You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Upul Godage (JIRA)" <ji...@apache.org> on 2007/12/06 08:39:43 UTC
[jira] Resolved: (SYNAPSE-177) Require ability to pin File
transport based services and Tasks within a cluster
[ https://issues.apache.org/jira/browse/SYNAPSE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Upul Godage resolved SYNAPSE-177.
---------------------------------
Resolution: Fixed
added pinnedServers attribute to proxy, task
<proxy name="string" [transports="(http |https |jms )+|all"] [pinnedServers="(serverName)+"]>
<task class="org.my.synapse.Task" name="string" [pinnedServers="(serverName)+"]>
You can give a list of synapse server names where this proxy / task should be started using pinnedServers attribute. It takes the server names separated by comma or space character. If there is no pinned server list then proxy / task will start in all server instances. If a pinned server names list is given it will only start in the given named Synapse server instances. The Synapse server name is taken as follows. First it looks for the system property SynapseServerName. If it is not found it will take the hostname of the machine. Otherwise it will default to name 'localhost'. You can give a name to the starting Synapse server instance using ./synapse.sh -DSynapseServerName=<ServerName>
> Require ability to pin File transport based services and Tasks within a cluster
> -------------------------------------------------------------------------------
>
> Key: SYNAPSE-177
> URL: https://issues.apache.org/jira/browse/SYNAPSE-177
> Project: Synapse
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1
> Reporter: Asankha C. Perera
> Assignee: Upul Godage
>
> File transport based proxies and/or scheduled tasks must not run concurrently within a cluster. Thus it should be possible to pin them to a specific node
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org