Mohan Pawar (MohanP1794)
Aaseya IT Services Pvt. Ltd.

Aaseya IT Services Pvt. Ltd.
MohanP1794 Member since 2014 5 posts
Aaseya IT Services Pvt. Ltd.
Posted: June 19, 2017
Last activity: July 4, 2017
Posted: 19 Jun 2017 11:42 EDT
Last activity: 4 Jul 2017 4:57 EDT

Connect SOAP timeout exception in test environment

Hi All,

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?

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.