[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1345) -b 0.0.0.0 is behaving one way on Test machine and another way on Qa machine

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1345?page=all ]

Tim Fox updated JBMESSAGING-1345:
---------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136484

> -b 0.0.0.0 is behaving one way on Test machine and another way on Qa machine
> ----------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1345
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1345
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.4.0.SP3
>         Environment: Red Hat Enterprise Linux WS release 3 (Taroon Update 9) on both servers.  Java version on both servers is:  
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pxi32dev-20050923b)
> IBM J9SE VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20050915a (JIT enabled)
> J9VM - 20050914_03248_lHdSMR
> JIT  - 20050914_1758_r8
> GC   - 20050907_AB)
> JCL  - 20050915
> jboss-4.2.2.GA with jboss-messaging-1.4.0.SP3
>            Reporter: Rich Daly
>         Assigned To: Tim Fox
>
> 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