[ 
https://wso2.org/jira/browse/ESBJAVA-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612#action_15612
 ] 

Asankha Perera commented on ESBJAVA-426:
----------------------------------------

Eric

This will mainly apply to proxy services that use the VFS file transport etc. 
Sometimes people want to run the same configuration (e.g. checked into an SVN) 
from different nodes.  The http/s and other proxy services will not have any 
problem with this, but what if instance A polls your FTP server for a CSV file, 
and while it is being processed, your instance B kicks in? 

This concept is supported by some of the other leading JEE app servers as well..

>By the way, how to define which instances are part of a cluster deployment? 
You can start the ESB instances with - right now it depends on which 
synapse.xml (or registry) the instance points to.. each of these are started 
independently. Currently the mediators for throttling and caching use the 
clustering support based on the Apache Axis2 (which runs underneath) clustering 
that uses tribes, to replicate and share state within a cluster. Thus which 
nodes are part of a cluster is done with tribes configuration via the axis2.xml

>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?
Again, you may have a task that does not require pinning, or there could be 
tasks that does..

asankha

> 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

Reply via email to