[jira] [Commented] (AXIS2-6030) Axis2 connections are not returned to connection pool on 1.8.0 with JAXWS

["Robert Lazarski (Jira)" <ji...@apache.org>]

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

Robert Lazarski commented on AXIS2-6030:
----------------------------------------

Yes, {{getPoolEntryBlocking in the stack trace listed in your README of the github project you created indicates that connections are not being released somehow as the code is waiting for a connection. }}

My best guess is that you are not reading the entire response somehow and therefore the connection is not closing do to a lack of a proper consume of HttpEntity. 

RequestImpl.releaseConnection() can be called automatically by setting HTTPConstants.AUTO_RELEASE_CONNECTION=true.  

Furthermore, you can define your own HttpClient and manage the close cycle. See  "options.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient)" in the link below that has been updated for 1.8.1. 

[https://github.com/apache/axis-axis2-java-core/blob/master/src/site/xdoc/docs/http-transport.xml]

Let us know what you find out. 

{{}}

{{}}

> Axis2 connections are not returned to connection pool on 1.8.0 with JAXWS
> -------------------------------------------------------------------------
>
>                 Key: AXIS2-6030
>                 URL: https://issues.apache.org/jira/browse/AXIS2-6030
>             Project: Axis2
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.8.0
>            Reporter: David Steindorfer
>            Assignee: Robert Lazarski
>            Priority: Major
>
> Good Afternoon,
>  
> I have upgraded Axis2 from 1.7.9 to 1.8.0 on one of our projects.
> However with the upgrade the requests seem to get stuck. 
> On further analysis I figured out that the connection pool ran dry as the connections were not returned.
>  
> It took a while to reproduce the issue reliably and isolated from the other code of our project but under very similar circumstances.
> Thus I created a public git repo with the code I wrote to reproduce the issue:
> [https://github.com/dsteindo/Axis2Examples]
>  
> I think the affected component is the "axis2-transport-http" library.
> For now I reverted the project's libraries back to 1.7.9.
> But it would be awesome to use the latest libraries, considering that you did quite a lot of changes and improvements :) 
>  
> Please feel free to contact me if more information is needed, but I guess that everything should be documented with the git repository.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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