(This might help someone searching the archives)
When upgrading from 3.0.6 to 3.2.2 we had a problem running a JMX client on a
separate host. The client uses UIL2ConnectionFactory (in 3.0.6 we used OIL). In
3.2.2 the client could not get a working QueueConnection to the server anymore.
We used different combinations of Linux, Windows NT and Win2k machines and the
error messages changed, but all had something to do with networking stuff.
Exceptions seen: javax.naming.CommunicationException, java.net.ConnectException,
java.rmi.NoSuchObjectException.
The exception messages was "Connection refused","no such object in
table","Cannot authenticate user".
The reason seems to be that the JBoss server has the wrong idea on what external
IP address it should bind to. It tells the JMS client to use 127.0.0.1.
The solution was to set the address on the command line when starting JBoss:
run.sh -Djboss.bind.address=192.168.3.75 -Djava.rmi.server.hostname=192.168.3.75
This will be used in server/default/deploy/jms/uil2-service.xml where an
attribue is set:
<attribute name="BindAddress">${jboss.bind.address}</attribute>
Open the JMX Console and look at jbossmq, "service=InvocationLayer,type=UIL2".
The attribute "BindAddress" should be set to the IP number the clients should
connect to.
Now it's vorking perfectly.
Someone else could perhaps fill in the details?
/Markus
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
