I see this warning in my sever.log
2014-05-02 00:00:08,310 WARNING [javax.jms] (pool-4-thread-2) [I500]: Caught JVM Exception: java.lang.NullPointerException
I am using wildfly. My bridge definition looks like this:
<jms-bridge name="myBridge" module="org.glassfish">
<source>
<connection-factory name="jms/ConnectionFactory"/>
<destination name="jms/TestQueue"/>
<context>
<property key="java.naming.factory.initial" value="com.sun.enterprise.naming.SerialInitContextFactory"/>
</context>
</source>
<target>
<connection-factory name="java:/jmsConnectionFactory"/>
<destination name="jms/TestQueue"/>
<context>
<property key="java.naming.factory.initial" value="org.jboss.as.naming.InitialContextFactory"/>
</context>
</target>
<quality-of-service>AT_MOST_ONCE</quality-of-service>
<failure-retry-interval>500</failure-retry-interval>
<max-retries>10</max-retries>
<max-batch-size>500</max-batch-size>
<max-batch-time>500</max-batch-time>
<add-messageID-in-header>true</add-messageID-in-header>
</jms-bridge>
It seems this warning happen when the bridge receives a message. Does anyone know why this happens?
I don't recognize that WARN message, and I can't find anything like it in the HornetQ codebase (which contains the bridge). Perhaps it's coming from the Glassfish code?