Hello all,
I have a http BC provider setup to communicate with a third party soap
server.
I am having an issue when the third party soap server closes the connection.
On that server, the netstat indicates that each socket is in a FINISH_WAIT
state.
In servicemix (3.1), it looks like the session is still open. After a
while, the servicemix encounters the limits for http client communications
(32 is the default value) and servicemix basically stops processing both
http requests coming in and going out.
The third party soap server is rather limited in its capabilities and I
suspect that there is some option that is not being set properly during its
configuration.
Two questions:
1) Does anyone have any suggestions of what might be happening and what to
troubleshoot. My knowledge in this area is limited.
2) Is there anyway to send/configure specific http header options. I was
thinking about trying to close the connection after each request from the
servicemix side as a test ('connection close' header option).
Thanks,
James
--
View this message in context:
http://www.nabble.com/http-sessions-not-releasing-with-a-bc-provider-soap-request-tf3274875s12049.html#a9107215
Sent from the ServiceMix - User mailing list archive at Nabble.com.
