[
https://issues.jboss.org/browse/AS7-3070?page=com.atlassian.jira.plugin.s...
]
David White commented on AS7-3070:
----------------------------------
The described workaround does not work if a connecting class is loaded on server startup (
a common use case), because the workaround script may not yet have executed.
Therefore the connection client id must be set in code, which the API does not recommend
(for reasons not at all clear to me).
Connection factory client-id does not survive server restart
------------------------------------------------------------
Key: AS7-3070
URL:
https://issues.jboss.org/browse/AS7-3070
Project: Application Server 7
Issue Type: Bug
Components: JMS, Server
Affects Versions: 7.1.0.Beta1
Reporter: David White
Assignee: Clebert Suconic
You can add a client-id in standalone.xml e.g.
<connection-factory name="InVmConnectionFactory">
<client-id>my-client-id</client-id>
<connectors>
<connector-ref connector-name="in-vm"/>
</connectors>
<entries>
<entry name="java:/ConnectionFactory"/>
</entries>
</connection-factory>
But after a re-start, the client-id is missing
standalone.xml has been silently re-written without the client-id
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira