[
https://issues.apache.org/jira/browse/AXIS2-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875492#comment-17875492
]
David Steindorfer commented on AXIS2-6030:
------------------------------------------
Here is how it should look on repeat runs with the same service instance using
the same HTTP Client.
You can see how the connection is retuned to available in pool:
{code}
org.apache.http.impl.conn.PoolingHttpClientConnectionManager#leaseConnection
{code}
!screenshot-5.png!
Also [~robertlazarski] I tried yesterday to clone
https://github.com/apache/axis-axis2-java-core to contribute my fix and wanted
to test things locally using the JAXWS samples, but I could not get it running
(trying to use mvn install caused issues as things like axis2-kernel
1.8.3-SNAPSHOT not being found)
https://github.com/apache/axis-axis2-java-core/tree/master/modules/samples/jaxws-samples
Maybe you have a guide somewhere on how to contribute and test things properly
before doing changes and opening PRs.
> 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: jaxws
> Affects Versions: 1.8.0
> Reporter: David Steindorfer
> Assignee: Robert Lazarski
> Priority: Critical
> Fix For: 1.8.3
>
> Attachments: EchoTest.java, XMLSpineImpl_Fix.zip,
> closeInputStreamFn.png, echoTestInterruptionException.txt,
> inputStreamAssignment.png, jaxws-samples.png, screenshot-1.png,
> screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png,
> usageInCreateResponseFn.png
>
>
> 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.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
