[jboss-jira] [JBoss JIRA] Commented: (JBESB-396) JMS exception handling tidyup

[Tom Fennelly (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-396?page=comments#action_12351906 ] 
            
Tom Fennelly commented on JBESB-396:
------------------------------------

Is there anything in particular I can do to reproduce this issue Kev?

> JMS exception handling tidyup
> -----------------------------
>
>                 Key: JBESB-396
>                 URL: http://jira.jboss.com/jira/browse/JBESB-396
>             Project: JBoss ESB
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0 CR2
>            Reporter: Kevin Conner
>         Assigned To: Tom Fennelly
>
> 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)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira