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 "Anuj Bhatia (JIRA)" <ji...@apache.org> on 2009/12/18 10:35:18 UTC
[jira] Issue Comment Edited: (AXIS2-4586) JiBX Client Stub not
cleaning up HTTP connections after each operation
[ https://issues.apache.org/jira/browse/AXIS2-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792411#action_12792411 ]
Anuj Bhatia edited comment on AXIS2-4586 at 12/18/09 9:34 AM:
--------------------------------------------------------------
I propose the attached patch (template.patch) as a fix to this issue
was (Author: anbhatia):
I propose the attached patch as a fix to this issue
> JiBX Client Stub not cleaning up HTTP connections after each operation
> ----------------------------------------------------------------------
>
> Key: AXIS2-4586
> URL: https://issues.apache.org/jira/browse/AXIS2-4586
> Project: Axis2
> Issue Type: Bug
> Components: databinding
> Affects Versions: 1.5
> Environment: Windows XP, Java 5
> Reporter: Anuj Bhatia
> Attachments: template.patch
>
>
> It seems that java/modules/jibx/src/org/apache/axis2/jibx/template/JibXDatabindingTemplate.xsl has a bug. The Stub classes generated for a service using JiBX data binding do not make a call to the method _messageContext.getTransportOut().getSender().cleanup(_messageContext); after each operation. This method is being called in the client stubs generated for services using ADB binding.
> Not calling this method results in the HTTP connection not getting released if the MultiThreadedHttpConnectionManager is being used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.