[ https://jira.jboss.org/jira/browse/JBTM-394?page=com.atlassian.jira.plugi... ] Jonathan Halliday updated JBTM-394: ----------------------------------- Fix Version/s: 4.4.0.GA JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=140667 Affects Version/s: 4.4.CR2 Assignee: Jonathan Halliday -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBTM-394?page=com.atlassian.jira.plugi... ] Jonathan Halliday commented on JBTM-394: ---------------------------------------- Added getters and setter for addresses / ports to the jta and jts service mbean interfaces and implementations. Revised assorted jta/jts/core internals to remove knowledge of AS from things that don't need it - the TransactionManagerService puts the values from ServiceBindingManager (or SERVER_BIND_ADDRESS as a fallback) in to the arjuna config objects, so app server integration is transparent to the rest of the JBossTS codebase. Revised XTS AS integration to read same service bindings the AS webserver uses, making it more POJO and less JMX style integration. Whilst checking port bindings, discoved and fixed inconsistencies in various places where 4711 was stated as recovery manager port, rather than the correct 4712. Used 4713 for transaction status manager and 4714 for socketProcessId in the app server. Note that when running standalone these still use random ports - do we want to hardcode these defaults in the standalone version also? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira