The messaging server and the client (with its three threads) are running on two different machines. I am passing these two parameters through the 'build.properties' file on the client side. ====== jms.test.java.naming.provider.url = jnp://bhatp-desktop:1099 jms.test.java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory ===== And I am invoking my test program(client) from a machine *different* from 'bhatp-desktop'.
I was not aware of the 'java:' part in the jndi reference. But the client was able to connect to the messaging server (and the hang happens in the middle of the execution). Even so, I have changed the jndi reference to '/XAConnectionFactory'. And the behavior remains the same. To reiterate - I have only one instance of messaging server in the whole setup running on 'bhatp-desktop' (killing this server results in 'connection refused' etc exception). I guess I am running the setup in a standalone configuration. I invoke the messaging server by running 'run.sh -c messaging' in the jboss-4.0.4.GA/bin directory. And the client is invoked on a different machine with jboss-messaging-client-scoped.jar in its classpath. I wish to report one more behavioral observation with respect to the given code. Even if I introduce a 'sleep(1000)' in the producer (main) thread's send loop to basically reduce its send rate, the program hangs after 10-12 iterations - the relayer and the consumer hang in 'receive' calls while the sender makes progress doing sends till 10000 iterations. Thanks Raghu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951636#3951636 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951636 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
