[
http://jira.jboss.com/jira/browse/JBWS-1833?page=all ]
Magesh Kumar B updated JBWS-1833:
---------------------------------
Security: Public (was: JBoss Internal)
ConfigObserver was causing a memory leak
----------------------------------------
Key: JBWS-1833
URL:
http://jira.jboss.com/jira/browse/JBWS-1833
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jbossws-1.2.1
Environment:
https://na1.salesforce.com/50030000003iZKa
Reporter: Heiko Braun
Assigned To: Heiko Braun
Priority: Critical
Fix For: jbossws-2.0.1.SP2
ConfigObserver becomes a possible memory leak:
I think the leak is created through the Observable pattern that's used between
EndpointMetaData(Subject) and CommonBindingProvider(Observer):
For each invocation we create a ServiceEndpointInvoker. Each invoker will be associated
with a BindingProvider. This links the CommonBindingProvider to EndpointMetaData through
the Observer pattern.
The EndpointMetaData is kept in the registry. IMO this is result in a memory leak.
I'll need to verify this assumption. But basically you could monitor a deployed
EndpointMetaData#configObservable.countObservers(). If the above statement is true is will
increase with every request that's being processed.
--
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