[
https://issues.apache.org/jira/browse/SANDESHA2-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Illsley resolved SANDESHA2-105.
-------------------------------------
Resolution: Won't Fix
This appears to be the same TIME_WAIT problem you get with plain Axis2.
I don't believe there is anything Sandesha2 specific about this problem.
> Connexion pending with TerminateSequence
> ----------------------------------------
>
> Key: SANDESHA2-105
> URL: https://issues.apache.org/jira/browse/SANDESHA2-105
> Project: Sandesha2
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: Axis2 1.2
> Sandesha 1.2
> Debian
> Reporter: jerome camilleri
>
> I used TCPMon (or SOAPMonitor) to monitor my WebServices ( IN-OUT MEP
> synchrone) with Axis2-1.2 and sandesha2-1.2 module activate.
> All request is listed correctly and state for eatch begin to Active and
> become Completed.
> Some of them stay in Active state (all Terminate Sequence in fact).
>
> ---------------------------------------------------------------------------------------------------------------------------------------
> I work always on my client deamon which send MTOM file with WebService Axis2
> 1.2 and Sandesha 1.2 for reliability.
> My system work very well but after 2000 sequences send to the server my
> client is shutdown because of "Too many open file" exception.
> I had already factorize the ConfigurationContext to avoid multiple files lock
> but my problem still continuing and I think it's related to my previous
> observation about active connexion on TCPMon....
> The netstat --program return thousands of lines :
> tcp 1 0 bounty.dc.frec.bull.fr:8147 tahiti.dc.frec.bul:webcache
> CLOSE_WAIT 15062/java
> (the 15062 process is my deamon client)
> In fact, if I count the number of CLOSE-WAIT connexions it's the same than
> the number of sequence sending...
> So the Terminate sequence is pending and consums all my client ressources...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
