Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <301939822.1236293516614.JavaMail.jira@brutus>
Date: Thu, 5 Mar 2009 14:51:56 -0800 (PST)
From: "Joe Bohn (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-4549) JMS resource jndi entries are not
 removed after uninstalling the JMS connect adapter
In-Reply-To: <463937598.1235293982137.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679405#action_12679405 ] 

Joe Bohn commented on GERONIMO-4549:
------------------------------------

BTW, one other interesting tidbit.  Once you have at least one jndi resource entry that is not removed subsequent entries will likewise not be removed (even if you then deploy and uninstall a resource group with just a connector). 

For example, if you deploy and undeploy a resource group with just one connector and no destination the connector entry will be removed from the jndi global context.
If you deploy a resource group with both a connector and destination the global context entries will not be removed on uninstall.  
And, if you subsequently deploy and undeploy another resource group with just a connector (no destination) after the failure to cleanup mentioned above the new connector will also continue to exist in global context after the uninstall.


> JMS resource jndi entries are not removed after uninstalling the JMS connect adapter
> ------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4549
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4549
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>            Reporter: Forrest Xia
>            Assignee: Jack Cai
>            Priority: Minor
>             Fix For: 2.1.4, 2.2
>
>
> Steps to reproduce this problem:
> 1. login admin console
> 2. Create a ActiveMQ resource connector with the wizard
> 3. Deploy it and check it is in running state
> 4. Click J2EE connector to uninstall it
> 5. Check JNDI viewer, you will see the JNDI entry still there, even you've uninstalled it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.