We are using JBoss 4.2.0-CR1 with JBoss-Messaging 1.2.0.sp1
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074103#4074103
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4074103
___
We fixed our problem by modifying the reverse DNS tables on our server machine.
Here is our theory:
It appears that the JBoss machine does a reverse lookup back to the client
machine. We connect to the JMS from the client using an ip address and port
number, but the Microsoft TCP/IP stack tri
Here is some additional information. We can ping the JBoss machine from the
other machine, running on the different class C network. We can even bring up
the JBoss web-console from the machine of the different class C network. So,
we know the problem is not in the network hardware, a firewall
With the old JBossMQ, we could have clients connect to the JMS topics from a
different Class C network (the first set of numbers in the IP address differed
from the one that JBoss was running on). With the new JBoss-Messaging we are
having troubles. The JBossMessaging will accept JMS connectio
