[
http://jira.jboss.com/jira/browse/JBAS-4256?page=all ]
Adrian Brock closed JBAS-4256.
------------------------------
Resolution: Done
The issue has been resolved for the in memory JVMIL by a more generic fix
that always triggers the ExceptionListener on the client if the client did not itself
initiate the close request.
e.g. The server or the transport layer closes the connection
Add support for stopping ILs triggering the ExceptionListener -
JVMIL
---------------------------------------------------------------------
Key: JBAS-4256
URL:
http://jira.jboss.com/jira/browse/JBAS-4256
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.4RC1
Reporter: Adrian Brock
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1
As per the super task which is a fix to make sure client exception listeners
get triggered if somebody stops the server, this same behaviour should
occur if somebody just stops the IL.
This involves making each IL keep track of their respective connections.
--
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