12:26 p.m.
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: Kevin Conner
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
1:18 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=all ]
Kevin Conner reassigned JBESB-396:
----------------------------------
Assignee: Tom Fennelly (was: Kevin Conner)
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
1:24 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-396) JMS exception handling tidyup
[ 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
1:44 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=comments#action_12351907 ]
Kevin Conner commented on JBESB-396:
------------------------------------
I have been seeing these issues when I have been going through the QSes.
My script does a combination of the following
- deploy standard sars
- deploy QS
- touch jboss-service.xml to force a redeploy
- run test
- remove jbossesb sars
rinse & repeat :-)
The second one happens reasonably frequently, the first not so often.
If this doesn't work let me know.
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
3:14 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=all ]
Mark Little updated JBESB-396:
------------------------------
Fix Version/s: 4.0
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
Fix For: 4.0
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
7:28 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=comments#action_12351932 ]
Tom Fennelly commented on JBESB-396:
------------------------------------
Ok, I've tried this a fair few times at this stage and I'm not reproducing it.
I'm obviously missing something here :-(
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
Fix For: 4.0
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
9:44 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=comments#action_12352023 ]
Kevin Conner commented on JBESB-396:
------------------------------------
I can still get the second one but have not seen the first since yesterday morning. I am
willing to take this back if you like.
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
Fix For: 4.0
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
9:49 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=comments#action_12352025 ]
Tom Fennelly commented on JBESB-396:
------------------------------------
Be my guest :-)
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
Fix For: 4.0
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
9:49 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=all ]
Tom Fennelly updated JBESB-396:
-------------------------------
Assignee: Kevin Conner (was: Tom Fennelly)
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: Kevin Conner
Fix For: 4.0
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
4:59 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=all ]
Kevin Conner closed JBESB-396.
------------------------------
Resolution: Done
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: Kevin Conner
Fix For: 4.0
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
4:59 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-396) JMS exception handling tidyup
[ http://jira.jboss.com/jira/browse/JBESB-396?page=comments#action_12352089 ]
Kevin Conner commented on JBESB-396:
------------------------------------
The Courier code has been tidied up in revision 9265.
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: Kevin Conner
Fix For: 4.0
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
6301
days inactive
6303
days old
10 comments
3 participants
participants (3)
-
Kevin Conner (JIRA) -
Mark Little (JIRA)
-
Tom Fennelly (JIRA)