You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "wolfdown (JIRA)" <ji...@apache.org> on 2008/11/17 22:14:05 UTC

[jira] Created: (SM-1693) NullPointerException in org.apache.servicemix.jms.multiplexing.MultiplexingConsumerProcessor.doShutdown()

NullPointerException in org.apache.servicemix.jms.multiplexing.MultiplexingConsumerProcessor.doShutdown()
---------------------------------------------------------------------------------------------------------

                 Key: SM-1693
                 URL: https://issues.apache.org/activemq/browse/SM-1693
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-jms
    Affects Versions: 3.3
         Environment: Any
            Reporter: wolfdown
            Priority: Minor


ServiceMix JMS component exception handler incorrectly assumes that the JMS provider was initialized successfully. The exception handler routine is failing in the following condiiton:

* AbstractJmsProcessor.java:init() (parent class of MultiplexingConsumerProcessor) is run, and all exceptions are caught and handled by shutdown()
* On succesfull run, doInit will be called and "pendingMessages" will be initialized as "new ConcurrentHashMap()"
* When exception is caught in init(), "doInit()" is not run and "pendingMessages" is left uninitalized"
* Eception handler "shutdown" calls "doShutdown()"
* --> doShutdown() in MultiplexingConsumerProcessor does not test if "pendingMessages" object is initialized before accessing it and causes a NullPointerException.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.