[ https://issues.jboss.org/browse/AS7-4521?page=com.atlassian.jira.plugin.s... ] jaikiran pai updated AS7-4521: ------------------------------ Fix Version/s: 7.1.2.Final-redhat1 Affects Version/s: (was: 7.1.2.Final-redhat1) Environment: AS7 upstream (dated 16th April 2012) Description: While trying to test a fix for a remote ejb issue I have found a problem with pooled-connection-factory credentials. It appears JBoss 7.1.2 nightly snapshot (16th April 2012) has tightened up security somewhat such that credentials are now required for internal pooled connection factory. I have found that user credentials specified for the hornetq configuration are not persisted between server restarts. For example. In the following configuration my server starts correctly the first time. However the <user> and <password> elements are mysteriously deleted by the app server. <jms-connection-factories> <pooled-connection-factory name="hornetq-ra"> <transaction mode="xa"/> <connectors> <connector-ref connector-name="remote-jms"/> </connectors> <entries> <entry name="java:/remote-JmsXA"/> </entries> <user>jmsUser</user> <password>mypass</password> </pooled-connection-factory> </jms-connection-factories> was: While trying to test a fix for a remote ejb issue I have found a problem with pooled-connection-factory credentials. It appears JBoss 7.1.2 nightly snapshot (16th April 2012) has tightened up security somewhat such that credentials are now required for internal pooled connection factory. I have found that user credentials specified for the hornetq configuration are not persisted between server restarts. For example. In the following configuration my server starts correctly the first time. However the <user> and <password> elements are mysteriously deleted by the app server. <jms-connection-factories> <pooled-connection-factory name="hornetq-ra"> <transaction mode="xa"/> <connectors> <connector-ref connector-name="remote-jms"/> </connectors> <entries> <entry name="java:/remote-JmsXA"/> </entries> <user>jmsUser</user> <password>mypass</password> </pooled-connection-factory> </jms-connection-factories> Forum Reference: https://community.jboss.org/message/730234#730234 (was: https://community.jboss.org/message/730234#730234) -- 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-4521?page=com.atlassian.jira.plugin.s... ] Hans Steiner edited comment on AS7-4521 at 4/16/12 7:31 AM: ------------------------------------------------------------ Creating this entry with jboss-cli seems to be successful [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/pooled-connection-factory=hornetq-ra:write-attribute(name=user, value=guest) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } but also does not store the property permanently. The standalone.xml config file is unchanged and the username is lost afer reload or system restart. was (Author: hans-juergen.stemmer.vkb.de): Creating this entry with jboss-cli seems to be successful [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/pooled-connection-factory=hornetq-ra:write-attribute(name=user, value=guest) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } but also does not store the property permanently. The standalone.xml config file is unchanged and the username is lost afer reload oder system restart. -- 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-4521?page=com.atlassian.jira.plugin.s... ] SBS JIRA Integration updated AS7-4521: -------------------------------------- Forum Reference: https://community.jboss.org/message/730233#730233, https://community.jboss.org/message/729620#729620, https://community.jboss.org/message/730234#730234 (was: https://community.jboss.org/message/729620#729620, https://community.jboss.org/message/730234#730234) -- 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-4521?page=com.atlassian.jira.plugin.s... ] Theo Cleminson commented on AS7-4521: ------------------------------------- I have noticed that this also applies to non-pooled connection-factory configurations too, eg: <connection-factory name="remote-jms-factory"> <connectors> <connector-ref connector-name="remote-jms"/> </connectors> <entries> <entry name="java:/remote-jms-factory"/> </entries> <user>jmsUser</user> <password>somePass</password> </connection-factory> -- 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