Affects Version/s: 5.5.1-fuse-01-06
Fix Version/s: 5.5.1-fuse-02-02
Similar Issues:Show 10 results
MB-729 NPE within MessageGroupDelayedTest MB-1120 NPE exception occurs when stopping broker MB-300 Sending persistent messages to a broker who has persistence disabled hangs the broker after a short period of time. MB-1062 NPE when upgrading from 5.5.1-fuse-00-08 to 551-fuse-01-20 MB-1199 NPE exception in kahadb after index issue MB-1035 NPE Exception when starting broker followed by immediate NPE when stopping MB-1058 NPE exception when querying a starting broker use JMX program MB-1242 kahaDB Commit Failed with NPE using XA Transactions MB-1096 Suspicious NPE in log when network bridge cannot be established and loggingBrokerPlugin configured MB-542 Brokers cannot reestablish forwarding bridge
External Issue URL:
In the attached test case, I have a broker with a topic configured to use a lastImageSubscriptionRecoveryPolicy. When the broker is first started and a consumer subscribes to the queue and ends without receiving any messages (there are none there), the following Warning shows up which is ok, however, the NullPointer exception isn't so great:
It takes about 30 seconds after the consumer ends for these messages to start appearing and they continue to appear every 30 seconds until some messages are sent. Then they stop.
To reproduce this, please download the attached zip file:
1. Start the broker (script here to make it easy startBroker1.sh )
2. run ant stomp-subscribe which is a variant of the demo we ship. It simply subscribes to the topic and exits.
3. Wait about 30 seconds. Messages start showing up in the log/console
4. Wait for a few of them to show up and then run stomp-send to drop a few messages out there. The messages subside.