Calling a CAF program via web service generates QName cannot be null error, but only for 1/5 of the same call in a parallel for loop.

[Former Member]

I'm calling 5 identical web service calls using a parallel for loop in BPM. Obviously the data in each slightly differs. Why would this call suspend the process and give the following errors:

handleCommunicationError( ErrorContextData, Throwable, TransitionTicket 😞 A technical error occurred. Interface namespace = myNamespace Interface name = myService Operation name = myOperation Connectivity type = WS Application name = myAppName Reference name = 8bd95deb-8cf1-453d-94e5-0576bb385149 Message Id = null WS style = DOC Start time of WS call = 2014-02-26 17:51:23.297 Return time of WS call = 2014-02-26 17:51:23.412 Principal name = SAP_BPM_Service Root error message = local part cannot be "null" when creating a QName Error message = Could not invoke service reference name 8bd95deb-8cf1-453d-94e5-0576bb385149, component name myComp application name myappname com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name 8bd95deb-8cf1-453d-94e5-0576bb385149, component name myCompname at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:341) 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.java:163) at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58) at com.sap.glx.core.resource.impl.j2ee.J2EEResourceImpl$Sessionizer.run(J2EEResourceImpl.java:261) at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:152) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:337) at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:149) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302) Caused by: java.lang.IllegalArgumentException: Could not process message for operation myOperation in web service plugin module. at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:228) at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:314) ... 19 more Caused by: java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName at javax.xml.namespace.QName.<init>(QName.java:246) at javax.xml.namespace.QName.<init>(QName.java:190) at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceImpl.getInterfaceInvoker(DInterfaceImpl.java:126) at com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASImpl.<init>(WSDASImpl.java:43) at com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASFactoryImpl.createWSDAS(WSDASFactoryImpl.java:39) at com.sap.engine.services.sca.plugins.ws.tools.wsdas.WsdasFactoryWrapper.createWsdas(WsdasFactoryWrapper.java:30) at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.initWsdas(WebServiceImplementationInstance.java:256) at com.sap.

Surely if it was the service group unassign then reassign issue then none of the calls would have worked?

[Former Member]

Hi David,

Is it randomly 1 of 5 that fail, the same one that fails always, or always the first or last?

Nick

[Former Member]

It is random. We've done several tests, it only failed this one time, so far. Obviously if we cant repeat it any more it could still be an issue in production.

I think we are going to open an OSS message for this...

Cheers

David

[Former Member]

Hi David,

While a random error is still an error it will be difficult for support to find a problem for an error which is not reproducible. It is always a faster resolution if you can determine how to provoke the error and provide those details. If we can reproduce an error on internal systems then we can fix the problem quickly and without having to access your system.

regards, Nick

[junwu]

are you able to call the ws in ws navigator?

[Former Member]

Yes. It also worked for the 4 other calls out of 5.