[jira] Resolved: (AXIS2-4586) JiBX Client Stub not cleaning up HTTP connections after each operation

["Andreas Veithen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen resolved AXIS2-4586.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6

Applied the patch to the trunk (r1050819) and to the 1.5 branch (r1050833).

> 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
>             Fix For: 1.6, 1.5.4
>
>         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.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org