I am using jboss3.0.4 and java 1.3.1_04 on two machines separated by a firewall.
I have an mdb message listener on one machcine listening to a message queue on the other machine.
I have read the previous postings on this topic on the forum, and as far as I can see, followed all the recommendations, in particular using UIL instead of OIL.
If I configure the firewall to allow any traffic between the two machines, everything works fine.
If I restrict the traffic to JNP (1099) and UIL (8091), then when the jboss server hosting the client mdb starts up, it hangs for about 20 minutes during the deployment of the mdb application, on the message:
[org.jboss.ejb.plugins.jms.DLQHandler] Creating
After about 20 mins, the deployment fails with the message:
[org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed
java.lang.NullPointerException at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:125)
During this time, the firewall log shows repeated attempts by the client machine to access the queue server machine on a port which varies from one occasion to another, e.g. 39319 or 54513. This port number changes if the jboss server hosting the queue is restarted, and therefore I cannot put a rule in the firewall to allow it.
Interestingly if I allow all ports through the firewall so that the jms connection is made, and then restrict them to the two mentioned above, messages continue to be received OK. So this port seems to be needed only for the initial set up of the connection. However this obviously does not help to solve the problem.
Is it possible to configure the port number used, so that I can set up a rule to allow it in the firewall?
Or is there some other solution?
Thanks
Chris
