On 11/08/2011 11:58 AM, bvahdat wrote: > Hi, > > just a very tiny pointer: > > Looking at the source it seems that the > SedaEndpoint.getConsumerMulticastProcessor() method returns 'null' causing > the NPE, as the condition: > > multicastStarted == false || consumerMulticastProcessor == null > > is true.
Interesting. But, is it a bug or bad usage? A normal seda queue would not have problems with more than one consumer. Should I just stop the other route before starting this one? t > > Regards, Babak > > -- > View this message in context: > http://camel.465427.n5.nabble.com/NPE-when-using-SEDA-queue-tp4973626p4973923.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Regards / Med vennlig hilsen Tarjei Huse Mobil: 920 63 413
