This content has been marked as final. Show 9 replies
Is all three are running the same version ?
Is this occuring regularly ?
This normally occurs, when the composite is waiting for response. But we should handle this by checking for the response data.
All the Oracle software is the same version. The composite calls the BPELs asynchronously. On two environments
all is always ok. On this one particular environment the other BPEL is always fine but this one always never receives the
1-way operation which is invoked by the mediator.
Is binding location of the BPEL reference is from the same environment where your mediator is deployed?
It once happened to me that my BPEL composite deployed on server1 by mistakenly was pointed to another BPEL process deployed on server2. So i was not able to view the flow trace in EM console. The status showed running in server1, and ended in server2.
Thanks. Not sure where to look for the binding location of the BPEL but I think it will be. The same code works ok in 2 other environments. Unit Test and DEV.
Check the composite.xml of your Mediator or Bpel.
If you are using dynamic URL then check in the assign activity.
In the flow trace the Mediator claims to invoke the 1-way operation 'operation1' ,say, on the target service but the receiveInput of the BPEL service does not show at all in the flow trace. We cannot see what is happening between the Mediator and the invoked BPEL - it's not exposed to us, as it all is in the composite or have I got that wrong?
My suggestion is to check if the Audit setting in the em is set properly.
Check at the following place
1. EM soainfra page
2. Composite Home page
3. Service Engine properties page
It is possible by default Audit may be off or set to Minimal in which u cannot see the flow
Thanks. Audit is on. ApplicationServer restarted. No luck.
Any lucky on this issue?