Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.0 CR2
    • Fix Version/s: 4.0
    • Component/s: None
    • Labels:
      None

      Description

      The JMS exception handling needs to be tidied up.

      The current code does not appear to release all connections resulting in 'too many open files' being raised on subsequent creation.

      It can also fail with a NameNotFoundException being raised from JNDI:-

      org.jboss.soa.esb.ConfigurationException: javax.naming.NameNotFoundException: ConnectionFactory not bound
      at org.jboss.internal.soa.esb.couriers.JmsCourier.createMessageConsumer(JmsCourier.java:486)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.jmsConnectRetry(JmsCourier.java:221)
      at org.jboss.internal.soa.esb.couriers.JmsCourier.access$000(JmsCourier.java:60)
      at org.jboss.internal.soa.esb.couriers.JmsCourier$1.onException(JmsCourier.java:503)
      at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1348)
      at java.lang.Thread.run(Thread.java:595)

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                kconner Kevin Conner
                Reporter:
                kconner Kevin Conner
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: