We created a Open SCA service with wsdl interface and java implementation. When we create an import for the service on WID assembly diagram (SCA binding) and test it using the WID test environment the test works fine.
But when calling the same service using a long running business process, the calls never reach the service and the invoke activity remains in running status.
It looks like the service invocation from long running business process is being routed via SI Bus (async invocation) and the SI Bus does not finds a destination for the target service. Setting the interaction style to synchronous/asynchronous on the imported sca component did not have any effect.
The same Open SCA component exposed with EJB3 binding did not have the above problem.
This topic has been locked.
2 replies Latest Post - 2010-05-14T13:59:50Z by Rohit_R
Pinned topic Long running process unable to invoke Open SCA service over SCA binding
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2010-05-14T13:59:50Z at 2010-05-14T13:59:50Z by Rohit_R
Re: Long running process unable to invoke Open SCA service over SCA binding2010-05-13T22:34:12Z in response to Rohit_RConsole log shows the following error
CWSIK0015E: The destination sca/AppAuditServiceSpringScaComponent/exportlink/AppAuditService was not found on messaging engine qnode.server1-SCA.SYSTEM.qcell.Bus.
Re: Long running process unable to invoke Open SCA service over SCA binding2010-05-14T13:59:50Z in response to Rohit_RIn the WID assembly diagram, removing "reliability" from the QoS Qualifiers for the SCA reference fixed the problem as the messages are no longer routed via SI BUS.