[ https://issues.jboss.org/browse/AS7-3070?page=com.atlassian.jira.plugin.s... ] David White updated AS7-3070: ----------------------------- Fix Version/s: (was: 7.1.0.Final) Workaround Description: Add the following lines to the jboss startup script after the wait for startup: /opt/jboss/bin/jboss-admin.sh -c << EOF /subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory:remove /subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory:add(connector={"in-vm"=>undefined},entries=["java:/ConnectionFactory"],client-id=my-client-id) quit EOF n.b. :write-attribute does not work - it appears to work if issued twice, and the client-id appears to be set according to :read-resource, but running code does not have the client-id Description: 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 was: The following snippet is from standalone.xml. Client-id is silently ignored and deleted from the configuration file. It is not possible to create durable topic subscription with this factory (the sevrer complaints about missing client-id). {code:xml} <pooled-connection-factory name="DURABLE_SUB_CONNECTION_FACTORY"> <transaction mode="xa"/> <connectors> <connector-ref connector-name="netty"/> </connectors> <entries> <entry name="jms/DURABLE_SUB_CONNECTION_FACTORY"/> </entries> <client-id>cts3</client-id> </pooled-connection-factory> {code} Steps to Reproduce: as described -- 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

[ 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). -- 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

[ https://issues.jboss.org/browse/AS7-3070?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-3070: ----------------------------------- Can you try this against the recently released AS 7.1.0.CR1b and see if this is still an issue? -- 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

[ https://issues.jboss.org/browse/AS7-3070?page=com.atlassian.jira.plugin.s... ] David White edited comment on AS7-3070 at 1/4/12 5:57 AM: ---------------------------------------------------------- Jaikiran Bug is still present in 7.1.0.CR1b, as is the weird :write-attribute behaviour, which is exactly the same as when reported. was (Author: davidw53): Bug is still present in 7.1.0.CR1b, as is the weird :write-attribute behaviour, which is exactly the same as when reported. -- 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

[ https://issues.jboss.org/browse/AS7-3070?page=com.atlassian.jira.plugin.s... ] David White commented on AS7-3070: ---------------------------------- Jaikiran Same as before, client-id is not saved. Seriously though, I can live with this. Much more important for me by far is to know how to set up JMS security, which i've reported as a bug https://issues.jboss.org/browse/AS7-3150 -- 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