[
https://issues.apache.org/jira/browse/GERONIMO-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jack Cai updated GERONIMO-4549:
-------------------------------
Attachment: Geronimo-4549_0307.patch
I've got some progress now.
1. For the original problem, it happens in such scenario: if there are two
names which share some common intermediate parts, e.g., "test/test1/GBean/R1"
and "test/test2/GBean/R2", then any attempts to remove any of them will fail.
This can be fixed by using passed-in removeNotEmptyContext instead of "false"
in
org.apache.xbean.naming.context.WritableContext$NestedWritableContext.removeBinding().
I've read through related code and feel it's a safe update.
2. There is another more serious problem exposed after the above problem is
fixed, i.e., the index entries in WritableContext will not be removed when the
corresponding object is removed. This will result in subsequent "lookup" for
that object continuing to succeed. I've also fixed this.
I wrote two testcases for future regression. The patched code passes all
previous unit tests in addition to the new ones. Also verified the JMS resource
issue in Admin Console is now resolved.
> 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
>
> Attachments: Geronimo-4549_0307.patch
>
>
> 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.
