[ 
https://issues.apache.org/jira/browse/AXIS2-5800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371333#comment-15371333
 ] 

Andreas Veithen commented on AXIS2-5800:
----------------------------------------

Can you provide a test case that reproduces the problem with a supported 
version of Axis2?

> Memory leak in soap service client when remote service url is invalid.
> ----------------------------------------------------------------------
>
>                 Key: AXIS2-5800
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5800
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.6.3
>            Reporter: Jayachandra naidu K
>            Priority: Minor
>              Labels: easyfix, features
>   Original Estimate: 4m
>  Remaining Estimate: 4m
>
> Version: Axis2 1.6.3 kernel.
> Scenario: 
> Configure only IP address in remote service url and send SOAP message using 
> soap service client.
> Example: 127.0.0.1
> In the above scenario instance in this map are increasing. 
> org.apache.axis2.context.ConfigurationContext.operationContextMap
> Rootcause:
> As configured url is invalid, Below api throws AxisFault exception.
> org.apache.axis2.description.ClientUtils.inferOutTransport(AxisConfiguration, 
> EndpointReference, MessageContext)
> org.apache.axis2.client.OperationClient.prepareMessageContext(ConfigurationContext,
>  MessageContext)
> In prepareMessageContext api AxisFault exception not handled and it is 
> directly throwing to user application.
> Fix:
> Catch the AxisFault exception in 
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(boolean) 
> and call 
> org.apache.axis2.context.ConfigurationContext.unregisterOperationContext(String)
>  api with message id.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to