Hello Team,


In our project we have Axis1.2 been integrated with Tomcat5 and used for
the past few years.



We face CLOSE_WAIT(as in JIRA AXIS2-2883
<https://issues.apache.org/jira/browse/AXIS2-2883> )  issue and from the
release notes of Axis2 1.5.1,  it is inferred that the issue is resolved
in this release.




Excerpt from http://axis.apache.org/axis2/java/core/


October 23, 2009 - Apache Axis2/Java Version 1.5.1 Released!
 The 1.5.1 version fixes some bugs
<http://issues.apache.org/jira/browse/AXIS2> , including most notably a
connection starvation issue that would cause a large number of sockets
stuck in CLOSE_WAIT or TIME_WAIT.




So, we are planning to migrate from axis1.2 to axis2 1.5.1, only to
solve this CLOSE_WAIT issue in particular particular.



But I learnt that Axis1 to Axis2 is a major design change and could
involve more complexities.

This I can see comparing the *.jar files of both the releases.



Is it worthwhile to migrate solely fot this issue?



Is there is any path/workaround to solve this issue without complete
re-integration?



Expert feedback is needed on this.



Please support regarding this.





With Best Regards,

Senthil Kumar Sekar

________________________________________________________________________
________

Off: +91-44-39900038  |Mob: +91-9841378208 | VoIP: 8480038(Internal) |
Email: senthil.se...@wipro.com




Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com

Reply via email to