2 Replies Latest reply on Dec 14, 2005 2:26 AM by Adrian Brock

    RemoteJMSProvider & DefaultJMSProvider Mixup

    Terry Paterson Newbie

      Hi There,

      I have my JBoss server setup to listen to a remote queue as per the wiki - and this works fine,

      however - today I noticed - that when the remote machine went down, my app was no longer able to send messages to local topics (although local queues worked fine),

      when attempting to send a message to a local topic - I got an exception telling me the client was not connected.

      when the remote server came back up -- the problem remained - but after restarting Jboss on the local server things went back to normal.

      apologies for lack of detail, exceptions, etc on this -- I will endevour to collect some more tomorrow -- just thought I'd do a quick check and see if anyone recognised this problem ?

        • 1. Re: RemoteJMSProvider & DefaultJMSProvider Mixup
          Terry Paterson Newbie

          update to previous notes.

          When my app tries to send a message to a local topic - I get the following exception :


          org.jboss.mq.SpyJMSException: Cannot send a message to the JMS server; - nested throwable: (java.io.IOException: Client is not connected) at org.jboss.mq.Connection.sendToServer(Connection.java:1028)
          at org.jboss.mq.SpySession.sendMessage(SpySession.java:1005)
          at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:265)
          at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:199)
          at org.jboss.mq.SpyTopicPublisher.publish(SpyTopicPublisher.java:58)
          at com.actual_systems.p2.server.session.remote.ejb.VehicleFindMDBean.summarizeAndSendVehicles(VehicleFindMDBean.java:350)
          at com.actual_systems.p2.server.session.remote.ejb.VehicleFindMDBean.startSearch(VehicleFindMDBean.java:231)
          at com.actual_systems.p2.server.session.remote.ejb.VehicleFindMDBean.onMessage(VehicleFindMDBean.java:164)


          The client is still connected -- and I can see the socket connections using netstat or lsof.


          When the remote JMS provider comes back up -- I start receiving messages from the remote queue, but sending messages to the local topic still fails -- the only way to make it start working again is to restart JBoss on the local machine.

          • 2. Re: RemoteJMSProvider & DefaultJMSProvider Mixup
            Adrian Brock Master

            http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
            FAQ

            And broken keep-alive configurations don't count, use the networking forum
            or better yet talk to your network admin.