kevan wrote: > > It sounded like you can also avoid using asyncDispatch=false. If you have > slow consumers, this might be a problem for you... > yes, I set asyncDispatch=false with vm:// protocol, and the NPE happens less possible,,,but still happens. Now I change to use tcp:// protocol and run test, till now the problem did not happen yet. Is that only "VM"Transport problem?
kevan wrote: > > Would you be able to build a patched version of ActiveMQ? Would also like > to know if that fixes your problem... > I would like to, but actually I am using IBM WASCE (based on Geronimo) and modifying server side code is almost not allowed (not technically). I would only try to find a workaround. btw. i created a ticket here https://issues.apache.org/activemq/browse/AMQ-2679 really thanks for your help :) -- View this message in context: http://n3.nabble.com/sudden-NullPointerException-from-ActiveMQSessionExecutor-wakeup-tp676485p683549.html Sent from the Users mailing list archive at Nabble.com.
