2 Replies Latest reply on Jun 14, 2011 9:37 AM by barrys

    jms bridge - NullPointerException

    barrys

      I have created a JMS bridge between OpenMQ and HornetQ.  The jms bridge configuration, based on the example jms-bridge, appears to successfully transfer messages from the OpenMQ queue into the HornetQ queue as expected.  However, I am also getting NullPointerExceptions in the HornetQ log:

       

      [main] 17:11:11,869 INFO [org.hornetq.core.server.impl.HornetQServerImpl]  HornetQ Server version 2.2.2.Final (super-hornetq-fighter, 122) [99ec237d-5ec6-11e0-953f-109add4c2c10] started

      [pool-3-thread-1] 17:11:39,146 WARNING [javax.jms]  [I500]: Caught JVM Exception: java.lang.NullPointerException

      [pool-3-thread-1] 17:12:13,488 WARNING [javax.jms]  [I500]: Caught JVM Exception: java.lang.NullPointerException

      [pool-3-thread-1] 17:12:45,049 WARNING [javax.jms]  [I500]: Caught JVM Exception: java.lang.NullPointerException

      ...

       

      Question: is there any way I can determine is causing these NullPointerExceptions or intercept them so they can be handled or surpressed?  I am using a stand-alone, nonclusted configuration for HornetQ.

       

      Any help would be appreciated.

        • 1. Re: jms bridge - NullPointerException
          clebert.suconic

          Honestly I have no idea... I would need some more information.

           

          can't you debug it somehow? Adding extra logs on the Bridge to catch where this is happening?

          • 2. Re: jms bridge - NullPointerException
            barrys

            Could you please provide an example of how to add extra logs on the Bridge?  Can it be done in a configuration file or would I need to get hold of the source code for the bridge and modify that to see where the exception is being thrown?

             

            You can assume that my hornetq-beans.xml is configured exactly like the jms-bridge example, except for the addresses to the specific servers in SourceJNDI and TargetJNDI. 

             

            Thanks for your reply.