[
https://issues.apache.org/activemq/browse/SM-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved SM-963.
--------------------------------
Resolution: Fixed
Fix Version/s: 3.2
3.1.2
Assignee: Guillaume Nodet
URL: http://svn.apache.org/viewvc?view=rev&rev=551899
URL: http://svn.apache.org/viewvc?view=rev&rev=551900
> NullPointerExceptions during JMS component initialization
> ---------------------------------------------------------
>
> Key: SM-963
> URL: https://issues.apache.org/activemq/browse/SM-963
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jms
> Affects Versions: 3.2, incubation
> Environment: Windows XP, JDK 1.5.0_11
> Reporter: Piotr Bzdyl
> Assignee: Guillaume Nodet
> Fix For: 3.1.2, 3.2
>
> Attachments: MultiplexingConsumerProcessor.java.patch
>
>
> Currently org.apache.servicemix.jms.AbstractJmsProcessor.start() starts JMS
> connection (and thus starts fetching messages on all already registered and
> all new registered listeners) before
> org.apache.servicemix.jms.multiplexing.MultiplexingConsumerProcessor
> initializes its pendingMessages map in doStart() method.
> It can be resolved by:
> 1) moving initialization of MultiplexingConsumerProcessor.pendingMessages
> before consumer.setMessageListener(this); Also initializing
> MultiplexingConsumerProcessor.channel field should be done before any message
> arrives via listener's onMessage method.
> OR
> 2) starting JMS connection in
> org.apache.servicemix.jms.AbstractJmsProcessor.start() after whole
> initialization in subclasses is done (after doStart())
> I am attaching patch for the first solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
