2 Replies Latest reply on Oct 6, 2005 7:38 AM by Joe Watts

    MDB deployment failure with HAJMS and clustering

    Joe Watts Newbie

      I am having a spot of trouble while attempting to deploy a simple message driven bean which subscribes for a topic defined in HAJMS. I have two JBoss server's running on a single box both using the all configuration with one server instance using the ports-1 and the other with ports-2 configuration in the sample-bindings.xml file. I reconfigured JMS in each server to use a Sybase database. Both servers start perfectly, but when I deploy the MDB to the deploy directory of one server I see the following:

      14:49:52,802 ERROR [DLQHandler] Initialization failed DLQHandler
      14:49:52,802 ERROR [DLQHandler] Initialization failed DLQHandler
      javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
      at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302)

      .... long stack trace...

      14:49:52,943 WARN [JMSContainerInvoker] JMS provider failure detected:
      javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out
      at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302)


      After this initial failure the server on which I deployed the bean seems to be trying to reconnect the JMS provider only to fail with the same of similar exceptions as those listed above.

      What might be causing this? And if it is a case of RTFM, which manual?