Support Article
Application stops working on invoking a SOAP service
SA-45683
Summary
Application stops working after invoking a remote SOAP service using a Connect-SOAP method.
Error Messages
[ WebContainer : 84] [ STANDARD] [ ] [ MyApp:01.01.01] ( internal.mgmt.Executable) ERROR Rule-Connect-SOAP.MyCo-FW-MyApp-Int-MyClass.myMethod - Exception
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.step15_circum0(ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.java:3797)
at com.pegarules.generated.activity.ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.perform(ra_action_invokeaxis2_58dbca272054d891f3559ad0fb53c832.java:309)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pegarules.generated.activity.ra_action_invoke_0cfba5258feb98ffba5cfba243966b7a.step8_circum0(ra_action_invoke_0cfba5258feb98ffba5cfba243966b7a.java:1025)
at com.pegarules.generated.activity.ra_action_invoke_0cfba5258feb98ffba5cfba243966b7a.perform(ra_action_invoke_0cfba5258feb98ffba5cfba243966b7a.java:190)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3553)
at com.pegarules.generated.activity.ra_action_invokesingleconnector_436d9e99e006184d29b3053573b8a8b2.step1_circum0(ra_action_invokesingleconnector_436d9e99e006184d29b3053573b8a8b2.java:547)
at com.pegarules.generated.activity.ra_action_invokesingleconnector_436d9e99e006184d29b3053573b8a8b2.perform(ra_action_invokesingleconnector_436d9e99e006184d29b3053573b8a8b2.java:71)
...
Caused by:
com.pega.apache.axis2.AxisFault: One or more functional errors have occurred.
000000c6 ThreadMonitor W WSVR0605W: Thread "WebContainer : 84" (00370b9f) has been active for 772220 milliseconds and may be hung. There is/are 120 thread(s) in total in the server that may be hung.
...
Caused by:
com.pega.apache.axis2.AxisFault: One or more functional errors have occurred.
000000c6 ThreadMonitor W WSVR0605W: Thread "WebContainer : 84" (00370b9f) has been active for 772220 milliseconds and may be hung. There is/are 120 thread(s) in total in the server that may be hung.
at java.lang.Thread.sleep(Native Method)
at java.lang.Thread.sleep(Thread.java:987)
at com.pega.pegarules.session.internal.mgmt.base.RequestorChildren.waitOnAllBatchActivities(RequestorChildren.java:653)
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.waitOnAllBatchActivities(PRRequestorImpl.java:1231)
at com.pegarules.generated.activity.ra_action_myactivity_6b1bcb50a963fa54c6a15824b1bde93b.step2_circum0(ra_action_myactivity_6b1bcb50a963fa54c6a15824b1bde93b.java:924)
[wasadmin@myhost] appsrv01> grep -i "SOAP service failed" SystemOut.log | wc -l
2640
Steps to Reproduce
- Invoke a remote SOAP service using a Connect-SOAP method with 'Run in Parallel Execution' mode
- Use the Connect-Wait method in the current or in a follow-on activity to access the results from the Connector with no value in WaitSeconds parameter
Root Cause
A software use or operation error. The Connect-Wait method when configured with an empty WaitSeconds parameter causes the current Requestor to wait indefinitely for child requestors to complete.
When the Connect-SOAP rule does not have a value for Response Timeout parameter, the child requestors created during the invocation takes a while before returning a value or failing due to a remote error.
Resolution
Perform the following local-change:- Assign a relevant value for Response Timeout parameter in the Connect-SOAP rule
- Set a value for WaitSeconds parameter in the Connect-Wait method when Connect rule is executes with 'Run in Parallel Execution' mode
Published March 3, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.