[
https://wso2.org/jira/browse/ESBJAVA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15610#action_15610
]
Eric Hubert commented on ESBJAVA-426:
-------------------------------------
Asankha, could you please provide some additional comments on this! I don't
understand what you mean with "pinning" a proxy or task to an esb instance of a
cluster?
Do you mean a proxy service for a real service will be created only on one
instance of the cluster? Why shall someone want this? Isn't it much better to
create it on any instance and use loadbalancing with sticky session support
instead? Otherwise one could use a separate instance, which is not part of the
cluster. By the way, how to define which instances are part of a cluster
deployment?
Regarding tasks it should not matter on which instance a task will be
performed, but it has to be guaranteed, that it will only be executed on one of
the instances. Or am I wrong here?
> Allow Proxy services and Tasks to be "pinned" to a server instance on a
> cluster via the admin UI
> ------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-426
> URL: https://wso2.org/jira/browse/ESBJAVA-426
> Project: WSO2 ESB
> Issue Type: Bug
> Reporter: Asankha Perera
> Assignee: Upul Godage
> Fix For: 1.7
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
