on ‎2014 Oct 17 3:02 AM
Hello Experts,
I have the following process:
In case where web service called through automated activity (AA) responds with normal response, proper response is sent back to synchronous web service call starting the process.
But in case, AA responds with a SOAP Fault, process does not return anything and it gets in status Error -> Suspended".
I can find the following information from the logs:
Please suggest if there is anything missing to be configured in the process.
Thanks & Regards,
Ankit Srivastava
*********************
com.sap.engine.services.sca.das.SCADASFactoryImpl Text: Error during SCA Processing
[EXCEPTION]
java.lang.reflect.InvocationTargetException: Could not process message for operation ******** in web service plugin module.
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:213)
at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:314)
at com.sap.glx.adapter.app.ucon.SCADASWrapperImpl.invoke(SCADASWrapperImpl.java:101)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject.invokeWebServiceOperation(UnifiedWebServiceCallObject.java:101)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallClass.invoke(UnifiedWebServiceCallClass.java:178)
at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:657)
at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:248)
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:798)
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:78)
at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:196)
at com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool
.
.
.
Caused by: com.sap.engine.services.webservices.espbase.client.dynamic.WebServiceException: ; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException:
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SDOUtil.deserializeException(SDOUtil.java:177)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SDOUtil.processFault(SDOUtil.java:138)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SDOUtil.deserializeResponse(SDOUtil.java:209)
*********
Request clarification before answering.
I think it is right behavior, you made it happen like that
Modeling Exceptions and Exceptions Handling - Modeling Processes with Process Composer - SAP Library
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can we see the details of the boundary event?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Siddhant,
Boundary events for each of the AA just raises the SOAP fault associated with individual services at each step.
At the boundary event, I am storing the fault in a context object. In case of fault, I can see that respective context object object is filled with proper values. It means that the fault is caught properly at boundary event.
Also, instead of diverting the flow at boundary event to error end for raising fault associated, if the flow is diverted to message end event... the process executes successfully even in case any of the AA return soap fault.
It indicates that "Error End" event is not able to return soap fault for some reason.
Please let me know if it provides more idea about the issue.
Thanks & Regards,
Ankit Srivastava
| User | Count |
|---|---|
| 9 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.