You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2007/07/31 03:37:52 UTC
[jira] Resolved: (AXIS2-3018)
ServiceDescriptionImpl.updateEndpointDescription() re-creates
EndpointDescription objects when portQName is not specified
[ https://issues.apache.org/jira/browse/AXIS2-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved AXIS2-3018.
--------------------------------
Resolution: Fixed
Fix Version/s: nightly
1.3
Patch committed to 1_3 branch: Committed revision 561207.
> ServiceDescriptionImpl.updateEndpointDescription() re-creates EndpointDescription objects when portQName is not specified
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3018
> URL: https://issues.apache.org/jira/browse/AXIS2-3018
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 1.3, nightly
>
> Attachments: AXIS2-3018.patch
>
>
> ServiceDescriptionImpl.updateEndpointDescription() looks for existing EndpointDescription objects only when portQName is specified. When portQName is not specified, the updateEndpointDescription() function will create a new EndpointDescription each time it is called. This can lead to a memory leak when the client configuration context is reused because somehow the EndpointDescription objects remain retained (through AxisConfiguration). I can provide more info on that later.
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org