users@glassfish.java.net

Re: Axis and Glassfish PWC1635,LDR5204

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Mon, 29 Oct 2007 09:49:52 -0400

Hi,

Łabno, Bernard wrote:
> The problem happens only when I'm using Axis. Unsetting context classloader
> does not help. My application does not set classloader. I can't use metro,
> since it implements JAX-WS which does not support "rpc/encoded" style.
> On axis-user mailing list nobody responses to my question. Now I'm lost, what
> shall I do ?

Can you produce a test case? I can experiment the JDK if you are able to
give me a simple test case that demonstrate the problem. But if the
problem is with Axis, then you will need to talk to them.

Thanks!

-- Jeanfrancois

>
> @Override
> public void destroy() {
> Thread.currentThread().setContextClassLoader(null);
> }
>
> Dnia piątek, 26 października 2007 20:51, Jeanfrancois Arcand napisał:
>> Hi,
>>
>> Łabno, Bernard wrote:
>>> Indeed your explanation was very useful, but what shall I do exactly now
>>> ?
>> If your app doesn't set the context classloader, then it is a GlassFish
>> or Axis (hopefully Axis :-)) issue. I'm not sure it will work but you
>> might make sure, when the Servlet.destroy() (if you use Servlet) unset
>> the Context Classloader, so when the application is undeployed, the
>> context is reset (but to be honest I really don't think it is viable
>> solution).
>>
>>> Shall i somewhere in constructor of ejb unset contextClassLoader ?
>> Could it be a bug in Axis? Is your application set the context
>> classloader or you get the exception because of Axis? Those bugs are not
>> simple to track (at leats for me :-)). Last time I've to instrument the
>> JDK's Thread classes to find who, inside GlassFish, was configuring the
>> context classloader (was the ORB, but that issue has been fixed now).
>>
>> Are you able to reproduce the problem without Axis?
>>
>> -- Jeanfrancois
>>
>>>> To add to this, we usually see that situation when an application invoke
>>>> the Thread.setContextClassLoader(WebAppClassloader) and forgot to unset
>>>> it when the WebApplication is stopped/undeployed. Next time the thread
>>>> is re-used the exception will show up.
>>>>
>>>> Hope that help.
>>>>
>>>> -- Jeanfrancois
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>