On Dec 18, 2009, at 3:51 PM, Mahesh Venkat wrote:
> Hi Paul,
>
> I am using JBoss 4.2.3 GA with Tomcat 5..5.
> The hang occurs when I make the first call after recycling the JBoss
> server.
> Apparently this does not occur all the time nor in all the machines.
I think this may be a JBoss bug when recycling (but it perhaps may be
alleviated if Jersey closes the InitialContext instances when finished).
> It looks like this hang is influenced by the order in which some
> classes or jars are loaded perhaps?
>
From the thread dump it looks more like an issue with the JBoss JNDI
implementation.
I suspect you can probably reproduce this by writing a simple servlet
that instantiates InitialConext and looks up something that is known
not to exist.
> I was sarching for InjectionManager context. Is this defined
> somewhere?
>
> Object injectionMgr = new InitialContext().
>
> lookup
> ("com.sun.enterprise.container.common.spi.util.InjectionManager");
>
The name above will only be bound to an object for GlassFish v3
deployments. On JBoss the lookup should throw an NamingException.
Paul.