You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2015/10/16 17:29:05 UTC

[jira] [Commented] (OPENEJB-2119) Incorrect binary tree - IvmContext

    [ https://issues.apache.org/jira/browse/OPENEJB-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960881#comment-14960881 ] 

Romain Manni-Bucau commented on OPENEJB-2119:
---------------------------------------------

Hi Milos,

can you precise the use case you encounter (was it during startup for a resource binding, during runtime etc...) please?

> Incorrect binary tree - IvmContext
> ----------------------------------
>
>                 Key: OPENEJB-2119
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2119
>             Project: OpenEJB
>          Issue Type: Bug
>            Reporter: Milos Volauf
>            Priority: Critical
>         Attachments: Testing.java
>
>
> I get many javax.naming.NameAlreadyBoundException exceptions so I digged into org.apache.openejb.core.ivm.naming.IvmContext and org.apache.openejb.core.ivm.naming.NameNode.
> I was strange that NameAlreadyBoundException was fired from IvmContext.rebind, which does unbind and then bind.
> The debugging showed me that binary tree (implemented by NameNode) gets sometimes into incorrect state and consequently unbind does not find the node.
> The problem is that IvmContext has a reference to NameNode and calls bind() but the binary tree is correct only if bind() starts at the tree root. There is one big tree and several contexts have their nodes in it (IvmContext.mynode) and bind new nodes starting in mynode.
> I prepared a small test case which shows how the tree can enter into incorrect state.
> I used openejb-core-4.7.1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)