This has been reported on SailFin under
This is however a GlassFish issue.
during investigation whether deployments goes successful or not for just one
module, we see our whole systems JNDI tree. This complicates troubleshooting
and is annoying!
Reproduction: Please follow the following procedure:
choose a module that exposes JNDI when deployed (and enabled). An ear for example
check the JNDI tree. make sure the JNDI is not there
deploy the module containing the JNDI
check the JNDI tree. make sure the JNDI is there
undeploy the module containing the JNDI
check the JNDI tree. make sure the JNDI is not there (this fails)
push the Refresh button. See if it dissapears (this fails)
restart the server where the JNDI still shows, even though its removed
check the JNDI tree. make sure the JNDI is not there (this goes well)
There is a Refresh button when looking at the JNDI tree! Why doesn't the JNDI
dissapear when refreshing? I dont think that the idea is that restarting the
server should be the answer.
Unfortunately we cant share the used ear. However, it should work with any ear
(or even module) where a JNDI is exposed.