[ https://issues.apache.org/jira/browse/AXIS2-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550740#comment-17550740 ]
Robert Lazarski commented on AXIS2-6030: ---------------------------------------- I tried the best I could with the time I had and couldn't reproduce the problem using the latest axis2 code in git. It is possible the problem got fixed during this release cycle. I really need to proceed with the 1.8.1 release at this point since we have several vulnerable dependencies with CVE's, and I need to send the Axis quarterly report to the Apache board of directors no later than tomorrow - which I'd like to say a release is in progress. I am attaching my client code which is very similar to what you posted, though I added a main() so it can be invoked easily and also 300 connections in a loop. The web service invoked was the echo service contained in the {color:#000000}jaxws-samples{color}.war that was installed on Tomcat 9. See the attached screenshot that shows how to invoke it via a browser, and the java client code that invokes the service as a Java client. I am marking the issue as a fix for 1.8.2 though you may find out 1.8.1 just works as expected. > 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 > Attachments: EchoTest.java, echoTestInterruptionException.txt, > jaxws-samples.png, screenshot-1.png, screenshot-2.png, screenshot-3.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.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org