[
https://issues.apache.org/jira/browse/AXIS2-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711556#comment-17711556
]
Bryan Behling commented on AXIS2-6030:
--------------------------------------
We are having this same issue with our product after upgrading to Axis2 1.8.2
from 1.7.8. The thread dumps (after the problem starts to occur) show the exact
same stack as indicated in: https://github.com/dsteindo/Axis2Examples. After
review, we confirmed that it was happening after exactly 200 requests. This 200
connection count is defined in
"org.apache.axis2.transport.http.impl.httpclient4.HTTPSenderImpl", so I
recompiled that with 250 and confirmed it then allowed 250 requests before
"hanging". So, as noted, this confirms that connections are not getting
released. I also confirmed that the problem was introduced by the change made
in the mentioned commit:
https://github.com/apache/axis-axis2-java-core/commit/4d573434d35326cf3b37ee70db0fc9fc53fb0d81
However, I was not able to just replace that removed code, since some of the
classes used in that previous code no longer exist in Axiom. So, I settled on
the attached change (see attached: XMLSpineImpl_Fix.zip). The basic idea is to
call "detach()" on the Builder (which in turn iterates through next() until the
status is "complete"), which allows the connection to be released.
Not sure if this is the exact proper way to fix this issue, but it does resolve
the problem, and I thought I would update here in case it helps. Thanks.
> 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: Major
> Fix For: 1.8.3
>
> Attachments: EchoTest.java, echoTestInterruptionException.txt,
> jaxws-samples.png, screenshot-1.png, screenshot-2.png, screenshot-3.png,
> screenshot-4.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
