Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-2799

Improper Handling of Spring NullPointerException

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • jboss-fuse-6.3
    • jboss-fuse-6.2
    • Camel
    • None
    • % %
    • 6.3 Sprint 4 (Mar 28 - Apr 29), Sprint 7 - towards CR2

    Description

      Spring (3.2.9) throws an NPE (see below), which is not being properly handled. The end-result is that the attempts to refresh the JMS connections by the Camel route continue until, in this particular case, the Fuse container is stopped. This is reflected in the many ERROR statements, such as the one below, found in the container’s log files. 

      2015-01-22 08:40:02,117 | ERROR | Camel (CP_EPICadOTTR2_ip) thread #95 - JmsConsumer[vt.CP.ip.EPICad.in.CP_EPICadOTTR2_ip] | org.apache.camel.component.jms.DefaultJmsMessageListenerContainer} | 128 - org.apache.servicemix.bundles.spring-jms - 3.2.9.RELEASE_1 | Could not refresh JMS Connection for destination 'vt.CP.ip.EPICad.in.CP_EPICadOTTR2_ip?consumer.exclusive=true' - retrying in 5000 ms. Cause: null
java.lang.NullPointerException
        at org.springframework.jms.listener.AbstractJmsListeningContainer.refreshSharedConnection(AbstractJmsListeningContainer.java:392)[128:org.apache.servicemix.bundles.spring-jms:3.2.9.RELEASE_1]
        at org.springframework.jms.listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful(DefaultMessageListenerContainer.java:885)[128:org.apache.servicemix.bundles.spring-jms:3.2.9.RELEASE_1]
        at org.springframework.jms.listener.DefaultMessageListenerContainer.recoverAfterListenerSetupFailure(DefaultMessageListenerContainer.java:861)[128:org.apache.servicemix.bundles.spring-jms:3.2.9.RELEASE_1]
        at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1012)[128:org.apache.servicemix.bundles.spring-jms:3.2.9.RELEASE_1]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
        at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]

      This issue is related to an existing upstream issue: https://issues.apache.org/jira/browse/AMQ-5310. You’ll note in that upstream JIRA, the same combination of ERROR and NPE.

      Attachments

        1. trace.zip
          8.61 MB
        2. amq-request-reply.zip
          45 kB
        3. fuse.log
          1.43 MB
        4. camel-jms-2.15.1.redhat-621084.jar
          148 kB
        5. OSGI_LIST_Prod_Transform.txt
          11 kB
        6. Transform_logs.txt
          16 kB

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-7914 camel-jms retryInterval seems to have no effect

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link AMQ-5310

          Web Link CAMEL-7667

          Activity

            People

              janstey@redhat.com Jonathan Anstey
              Argo_Integration Travis North (Inactive)
              Viliam Kasala Viliam Kasala
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: