JBoss's JMS Resource Adapter already implements the ExecptionListener
for you.
But it does not work in some versions, because some developers
didn't understand how it interacts with the pool and broke the code.
There is now a comment in the code, to stop people breaking it:
| // If we are destroying, check the connection is not in the pool
| if (kill)
| {
| // Adrian Brock: A resource adapter can asynchronously notify
us that
| // a connection error occurred.
| // This could happen while the connection is not checked out.
| // e.g. JMS can do this via an ExceptionListener on the
connection.
| // I have twice had to reinstate this line of code, PLEASE DO
NOT REMOVE IT!
| cls.remove(cl);
| }
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869820#3869820
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869820
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
