Hi,
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 someone know why the terminate sequence is pending and consums all my
client ressources pleased ?
Jérôme
Jerome Camilleri wrote:
Hi,
I used TCPMon (or SOAPMonitor) to monitor my WebServices with
Axis2-1.2 and sandesha2 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 notice that the terminateSequence request don't have any SOAP-response.
I used IN-OUT MEP synchrone.
Is it just a TCPMon effect ? or is a TCP connexion keep alive after
eatch Terminate sequence ?
How resolved it (if necessary ?)
Regards
Jérôme
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
