[
https://issues.apache.org/jira/browse/AXIS2-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682033#action_12682033
]
Dobri Kitipov commented on AXIS2-3670:
--------------------------------------
I think that this issue has a solution. You can solve it doing one of the
following:
- Call the "cleanupTransport" in service client (client.cleanupTransport());
- setting the option.setCallTransportCleanup(true);
- invoke messageContext.getTransportOut().getSender().cleanup(messageContext);
all this should release your http connection and return it into the pool for
reuse.
Additionally it is always a good practice to invoke:
client.cleanup();
Doing so you releases resources (and memory) assigned to the client and can
solve "java.lang.OutOfMemoryError: Java heap space" issues if any.
IMHO this JIRA should be closed. What do you think?
Regards,
Dobri
> Problem using REUSE_HTTP_CLIENT - Application stalls
> ----------------------------------------------------
>
> Key: AXIS2-3670
> URL: https://issues.apache.org/jira/browse/AXIS2-3670
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Alois Reitbauer
> Priority: Critical
> Attachments: Stalled call vs. executing call.jpg
>
>
> When using REUSE_HTTP_CLIENT on a service client to reuse a http client the
> client application hangs after 3 executions. The reason is that it obviously
> waits in MultithreadedHttpConnectionManager.getConnectionWithTimeout()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
