java.lang.NullPointerException

MuleSoft JIRA | Angelo Bresci | 9 years ago
  1. 0

    I'm working with someone on case 1483 (https://na1.salesforce.com/50030000004hkw0). What's happening now is that they're testing 1.4.4, and seeing some strange behavior. I've reproduced both of the following behaviors: First, when Mule starts, it never succeeds in creating a connection upon the first attempt. We both see the following error: ERROR 2008-06-02 16:16:05,593 [UMOManager.3] org.mule.providers.SimpleRetryConnectionStrategy: Failed to connect/reconnect: WebsphereJmsConnector{this=15f1f9c, started=true, initialised=true, name='mqConnector', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=t rue, supportedProtocols=[jms], serviceOverrides={message.receiver=org.mule.providers.jms.MultiConsumerJmsMessageReceiver, transacted.message.receiver=org.mule.p roviders.jms.MultiConsumerJmsMessageReceiver}}. Root Exception was: null. Type: class java.lang.NullPointerException java.lang.NullPointerException at org.mule.providers.jms.MultiConsumerJmsMessageReceiver$SubReceiver.doStart(MultiConsumerJmsMessageReceiver.java:171) at org.mule.providers.jms.MultiConsumerJmsMessageReceiver.doStart(MultiConsumerJmsMessageReceiver.java:97) at org.mule.providers.AbstractMessageReceiver.start(AbstractMessageReceiver.java:466) at org.mule.providers.AbstractConnector.startConnector(AbstractConnector.java:379) at org.mule.providers.AbstractConnector.connect(AbstractConnector.java:1186) at org.mule.providers.SimpleRetryConnectionStrategy.doConnect(SimpleRetryConnectionStrategy.java:76) at org.mule.providers.AbstractConnectionStrategy$1.run(AbstractConnectionStrategy.java:57) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:619) INFO 2008-06-02 16:16:05,593 [UMOManager.6] org.mule.providers.SimpleRetryConnectionStrategy: Waiting for 5000ms before reconnecting. Failed attempt 1 of 12 Then, when we finally do connect (or at least when the console says we are connected), the messages on our queues are never consumed. I've attached the config files I've been using. If you have a VPN connection to the office, you should be able to connect to the same machine/queues referenced in my Spring file. Please let me know if you have any thoughts. Is this something we can fix with a config tweak?

    MuleSoft JIRA | 9 years ago | Angelo Bresci
    java.lang.NullPointerException
  2. 0

    I'm working with someone on case 1483 (https://na1.salesforce.com/50030000004hkw0). What's happening now is that they're testing 1.4.4, and seeing some strange behavior. I've reproduced both of the following behaviors: First, when Mule starts, it never succeeds in creating a connection upon the first attempt. We both see the following error: ERROR 2008-06-02 16:16:05,593 [UMOManager.3] org.mule.providers.SimpleRetryConnectionStrategy: Failed to connect/reconnect: WebsphereJmsConnector{this=15f1f9c, started=true, initialised=true, name='mqConnector', disposed=false, numberOfConcurrentTransactedReceivers=4, createMultipleTransactedReceivers=true, connected=t rue, supportedProtocols=[jms], serviceOverrides={message.receiver=org.mule.providers.jms.MultiConsumerJmsMessageReceiver, transacted.message.receiver=org.mule.p roviders.jms.MultiConsumerJmsMessageReceiver}}. Root Exception was: null. Type: class java.lang.NullPointerException java.lang.NullPointerException at org.mule.providers.jms.MultiConsumerJmsMessageReceiver$SubReceiver.doStart(MultiConsumerJmsMessageReceiver.java:171) at org.mule.providers.jms.MultiConsumerJmsMessageReceiver.doStart(MultiConsumerJmsMessageReceiver.java:97) at org.mule.providers.AbstractMessageReceiver.start(AbstractMessageReceiver.java:466) at org.mule.providers.AbstractConnector.startConnector(AbstractConnector.java:379) at org.mule.providers.AbstractConnector.connect(AbstractConnector.java:1186) at org.mule.providers.SimpleRetryConnectionStrategy.doConnect(SimpleRetryConnectionStrategy.java:76) at org.mule.providers.AbstractConnectionStrategy$1.run(AbstractConnectionStrategy.java:57) at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:619) INFO 2008-06-02 16:16:05,593 [UMOManager.6] org.mule.providers.SimpleRetryConnectionStrategy: Waiting for 5000ms before reconnecting. Failed attempt 1 of 12 Then, when we finally do connect (or at least when the console says we are connected), the messages on our queues are never consumed. I've attached the config files I've been using. If you have a VPN connection to the office, you should be able to connect to the same machine/queues referenced in my Spring file. Please let me know if you have any thoughts. Is this something we can fix with a config tweak?

    MuleSoft JIRA | 9 years ago | Angelo Bresci
    java.lang.NullPointerException
  3. 0

    Android: Saving Map State in Google map

    Stack Overflow | 11 months ago | Junie Negentien
    java.lang.RuntimeException: Unable to resume activity {com.ourThesis.junieNegentien2015/com.ourThesis.junieNegentien2015.MainActivity}: java.lang.NullPointerException
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.NullPointerException

      No message provided

      at org.mule.providers.jms.MultiConsumerJmsMessageReceiver$SubReceiver.doStart()
    2. org.mule.providers
      AbstractConnectionStrategy$1.run
      1. org.mule.providers.jms.MultiConsumerJmsMessageReceiver$SubReceiver.doStart(MultiConsumerJmsMessageReceiver.java:171)
      2. org.mule.providers.jms.MultiConsumerJmsMessageReceiver.doStart(MultiConsumerJmsMessageReceiver.java:97)
      3. org.mule.providers.AbstractMessageReceiver.start(AbstractMessageReceiver.java:466)
      4. org.mule.providers.AbstractConnector.startConnector(AbstractConnector.java:379)
      5. org.mule.providers.AbstractConnector.connect(AbstractConnector.java:1186)
      6. org.mule.providers.SimpleRetryConnectionStrategy.doConnect(SimpleRetryConnectionStrategy.java:76)
      7. org.mule.providers.AbstractConnectionStrategy$1.run(AbstractConnectionStrategy.java:57)
      7 frames
    3. org.mule.impl
      WorkerContext.run
      1. org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
      1 frame
    4. Backport of JSR 166
      ThreadPoolExecutor$Worker.run
      1. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
      2. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
      2 frames
    5. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:619)
      1 frame