[jboss-jira] [JBoss JIRA] Assigned: (JBAS-3233) Web services debug logging is causing the classloader to be switched

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3233?page=all ]

Dimitris Andreadis reassigned JBAS-3233:
----------------------------------------

    Assignee: Darran Lofthouse  (was: Scott M Stark)

Darran, is this still happening, after jboss 4.0.x is updated to use jbossws 1.0.1 (which has the fix)? The offending class is not even part of the 4.0.x source tree now, I think.

I'm assigning this to you, if you can handle it.

> Web services debug logging is causing the classloader to be switched
> --------------------------------------------------------------------
>
>                 Key: JBAS-3233
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3233
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ClassLoading
>    Affects Versions: JBossAS-4.0.4.GA
>            Reporter: Darran Lofthouse
>         Assigned To: Darran Lofthouse
>             Fix For: JBossAS-4.0.5.CR1
>
>         Attachments: ComplexReturnEJB_DocLit.ear
>
>
> Web services debug logging is causing the classloader to be switched.
> Currently the web services stack does not correctly set the classloader for web services deployments when deployed as part of an ear with an issolated classloader (see JBWS-941).  However debug logging in the web services code is incorectly causing the deployment to work!
> In the class 'org.jboss.ws.server.ServiceEndpoint' there is a method called 'postProcessResponse', this method contains some logging wrapped with a 'log.isDebugEnabled': -
>          // debug the outgoing message
>          if(log.isDebugEnabled())
>          {
>             resMessage.saveChanges();
>             SOAPEnvelope soapEnv = resMessage.getSOAPPart().getEnvelope();
>             String envStr = DOMWriter.printNode(soapEnv, true);
>             log.debug("Outgoing SOAPMessage\n" + envStr);
>          }
> If this logging is remove the ClassNotFoundException is thrown regardless of the log4j configuration.
> The ClassNotFoundException is good and shows that the classloader has not been switched.
> I will attach a deployment that can be used to reproduce this.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira