[
https://issues.apache.org/jira/browse/AXIS2-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-939.
-------------------------------------
Resolution: Fixed
issue fixed in the current SVN code base
> Client API does not remove OperationContext instances from configuration
> context after MEP completes
> ----------------------------------------------------------------------------------------------------
>
> Key: AXIS2-939
> URL: https://issues.apache.org/jira/browse/AXIS2-939
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.0
> Reporter: Thomas Eckoldt
> Assigned To: Deepal Jayasinghe
>
> I'm using the ServiceClient class to make SOAP calls to a web service
> provider. The used MEP is OUT-IN, transport is HTTP. In case of a synchronous
> single transport operation, AxisOperation.registerOperationContext() is
> called twice, once for the outgoing message (request) and once for the
> incoming message (response). Each message will have a unique message id
> assigned. AxisOperation.registerOperationContext() calls
> ConfigurationContext.registerOperationContext() with the message id as
> argument. This means the OperationContext is stored in the operation context
> map with the message id as key and it means, if this method is called twice,
> you will end with two entries in the map. Only one (the last) will be removed
> from the map by OperationContext.cleanup().
> Another case is for asynchronous dual transport operations using WS-A. For
> the outgoing message everything is fine, the OperationContext is registered
> in the map and contains the MessageContext for the outgoing message. But when
> the response is received, the AddressingBasedDispatcher class does not
> register the message context in the operation context (in method invoke()).
> This means the operation context contains only the OUT-MessageContext, not
> the IN-MessageContext and will never be removed from the context operation
> map.
--
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]
