[
https://issues.apache.org/jira/browse/AXIS2-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved TRANSPORTS-54 to AXIS2-5571:
--------------------------------------------------
Component/s: (was: JMS)
JMS
Affects Version/s: (was: 1.0.0)
1.0.0
Key: AXIS2-5571 (was: TRANSPORTS-54)
Project: Axis2 (was: Axis2 Transports)
> Support ClientIDs for JMS Connections
> -------------------------------------
>
> Key: AXIS2-5571
> URL: https://issues.apache.org/jira/browse/AXIS2-5571
> Project: Axis2
> Issue Type: Improvement
> Components: JMS transport
> Affects Versions: Transports 1.0.0
> Reporter: Rene Preissel
> Priority: Minor
>
> Currently the JMS transport doesn't support the specification of a client ID
> for connections.
> It does support a durable subscriber name. But even for non durable
> subscriber, a client ID is helpful to monitor the connections,
> Proposal:
> Introduce a new configuration parameter: "transport.jms.ClientID".
> Set the clientID in ServiceTaskManager.createConnection(), if the parameter
> is present.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
