[ 
https://issues.apache.org/jira/browse/AXIS-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536327
 ] 

Bjorn Townsend commented on AXIS-2696:
--------------------------------------

Hello Ravi,

Since Axis doesn't invoke RegistryDocumentBuilder objects directly (that's done 
by your app inside the servlet container) this is going to be tough to 
reproduce without source code or at least a WSDL that I can generate a service 
and client for and hook a debugger up to. My guess though is that this is 
happening inside org.apache.axis.utils.XMLUtils.ThreadLocalDocumentBuilder.  Is 
it possible that you could provide a small test application that  we can use to 
reproduce this problem, or at least a WSDL file?

I also have some further questions for you:

1) How many times are you deploying and redeploying applications before the 
problem occurs? Are the applications being used much between deployments or are 
they just being un- and re-deployed? How much time passes between deployments?
2) What version of axis are you using? The latest is 1.4.
3) I am a bit confused about how you can be getting OutOfMemoryErrors between 
deployments. Axis 1.x doesn't support hot deployment, that's one of the selling 
points of Axis2. My understanding is that you pretty much have to restart your 
app server when you redeploy an app.  I would expect the 
RegistryDocumentBuilder objects to be released at that point if nothing else. 
Can you describe your redeployment process for me?

I'm sorry to hear that BEA wasn't able to help you. I'm not an Axis committer 
but I'd like to help you out.

Thanks,
Bjorn

> Apache Axis tends to use ThreadLocal to store RegistryDocumentBuilder causing 
> MemoryLeak
> ----------------------------------------------------------------------------------------
>
>                 Key: AXIS-2696
>                 URL: https://issues.apache.org/jira/browse/AXIS-2696
>             Project: Axis
>          Issue Type: Bug
>          Components: Deployment / Registries
>         Environment: Sun Solaris, Windows, Weblogic9.2 Portal Server, 
> JDK1.5.11
>            Reporter: ravi gutta
>
> We are getting OutOfMemoryErrors in Weblogic Portal Server9.2 during our 
> application multiple deployments. BEA analyzed this issue and found that, 
> Apache Axis classes are using ThreadLocal to hold RegistryDocumentBuilder 
> objects and not releasing them upon application un-deployment. This is one of 
> the issue identified during profiling of the application.
> Please, let us know if you are aware of this issue and a potential fix that 
> you recommend for this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to