[esb-issues] [JBoss JIRA] Commented: (JBESB-1821) JmsCourier holds JNDI contexts over calls to JmsConnectionPool

[Darrin Mison (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422496#action_12422496 ] 

Darrin Mison commented on JBESB-1821:
-------------------------------------

Proposed SOA 4.2 TP02 Release Note:
The period that JmsCourier will hold its JNDI contexts has been minimised to avoid potential deadlocks

> JmsCourier holds JNDI contexts over calls to JmsConnectionPool
> --------------------------------------------------------------
>
>                 Key: JBESB-1821
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1821
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2.1 CP3
>            Reporter: Kevin Conner
>            Assignee: Kevin Conner
>            Priority: Blocker
>             Fix For: 4.2.1 CP3
>
>
> The JmsCourier obtains a naming context from the pool but, before it has used it, makes a call to the JmsConnectionPool.
> The result of this is that there are now two naming contexts being obtained in the same thread.  This is a problem if you have already used up all the contexts, for example if you had 20 JmsCouriers with a context trying to obtain their JmsSession (no more contexts).  This will cause the first thread to deadlock for 30 seconds (the current timeout) and possibly others before the contexts have been released.
> The JmsCourier should not be holding the naming context for longer than is necessary, we need to reduce the scope.

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