[ http://jira.jboss.com/jira/browse/JBMESSAGING-1345?page=all ] Rich Daly updated JBMESSAGING-1345: ----------------------------------- Description: I have installed jboss-4.2.2.GA with jboss-messaging-1.4.0.SP3 on a test server and a qa server. On the Test server I call the run script like so: "run.sh -b test.server.com -c messaging -Djboss.bind.address=0.0.0.0". This test server is then able to accept requests from remote clients (from the 0.0.0.0 bind address option). And because of the -b option, any ConnectionFactory requests to 1099 will return a JbossConnectionFactory - ClientConnectionFactoryDelegate - serverLocatorURI like "http://test.server.com:4458//?callbackPollPeriod=102...". On the other hand, when I try to call the run script on my Qa server using "run.sh -b qa.server.com -c messaging -Djboss.bind.address=0.0.0.0", I get different behavior. The ports DO open up for remote clients but the serverLocatorURI comes back as "http://127.0.0.1:4458/?callbackPollPeriod=102...". Notice we have 127.0.0.1 instead of the name of the server. This does not help remote clients find the remote objects. I have spent days trying to manipulate -b, -D, and remoting*.xml files, but to no avail. I can usually only succeed one or the other: opening the ports for remote connections but getting 127.0.0.1 in serverLocatorURI OR getting qa.server.com in serverLocatorURI but blocking remote connections. was:I have installed jboss-4.2.2.GA with jboss-messaging-1.4.0.SP3 on a test server and a qa server. On the Test server I call the run script like so: "run.sh -b test.server.com -c messaging -Djboss.bind.address=0.0.0.0". This test server is then able to accept requests from remote clients (from the 0.0.0.0 bind address option). And because of the -b option, any ConnectionFactory requests to 1099 will return a JbossConnectionFactory - ClientConnectionFactoryDelegate - serverLocatorURI like "http://test.server.com:4458//?callbackPollPeriod=102...". On the other hand, when I try to call the run script on my Qa server using "run.sh -b qa.server.com -c messaging -Djboss.bind.address=0.0.0.0", I get different behavior. The ports DO open up for remote clients but the serverLocatorURI comes back as "http://127.0.0.1:4458/?callbackPollPeriod=102...". Notice we have 127.0.0.1 instead of the name of the server. This does not help remote clients find the remote objects. I have spent days trying to manipulate -b, -D, and remoting*.xml files, but to no avail. I can usually only succeed one or the other: opening the ports for remote connections but getting 127.0.0.1 in serverLocatorURI OR getting qa.server.com in serverLocatorURI but blocking remote connections. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1345?page=all ] Tim Fox updated JBMESSAGING-1345: --------------------------------- Fix Version/s: 1.4.0.SP3_CP03 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1345?page=all ] Tim Fox closed JBMESSAGING-1345. -------------------------------- Fix Version/s: Unscheduled (was: 1.4.0.SP3_CP03) Resolution: Rejected -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira