We are using Connect-Soap method followed by Connect-Wait method where in currently, we are passing WaitSeconds param as '-1'. Both(Dev+Test) environments services are pointed to the same end point url. The service works fine all day in Dev environment where as Testing environment service works fine till 4-5pm IST daily, but it starts giving timeout exception after 5pm once onshore folks check's in.
We tried by deleting the requestor pools from the SMA and setting WaitSeconds param to some positive value(2-5 min's), but neither of them worked. When we traced with checking alerts in the tracer, it looks like service is taking more than 30 second's for response in the testing environment, while it gives response in couple of seconds when we test the same in SOAP UI and Dev environment.
As a workaround, we daily go for the server restart,which resolves the timeout issue. But is there any way to get a rid of this issue?
It was working in SOAP UI as well as in Dev environment too, only issue was with the test environment. We did verify by keeping alert in the tracer, which was showing timeout exception.
I believe the issue was with the Connect-Wait method, due to which the requestor pool was getting exhausted and was resulting into a timeout exception. It is working better than earlier now after removing the Connect-Wait method, but still we have to go for a restart once in a week which we earlier used to do daily.