on 07-09-2014 5:02 PM
I`m experiencing wierd thing.
I have simple scenario using BPM
[ async iFlow1 ] -> [ BPM ] -> [ async iFlow2 ]
All SI are asynchronous, including one which I call from BPM through Automated Activity. But if I look in the message log of that outgoing message (from BPM to iFlow2), I see there this log entry
Application attempting to send an XI message synchronously using connection JPR
How can message be send synchronously through async SI/operation.
I doublechecked, that everything is set to async - even in automated activity in BPM process - when I try to set outbound mapping - it tells me, that it cannot be done.
I have a real problem with it, because I want to split that outgoing message and send it to two receivers. This cannot be done with sync messages, of course.
Do you experience same problem?
Hi Vladimir,
i cannot provide a solution, but we had a similiar issue. Scenario was the same as yours. The outgoing message from BPM ran into error and was not restartable, the log said "message expired", just like a sync message can expire due to timeout. But the configuration clearly was asynchronous.
(Suggestion from SAP was: increase parameter com.sap.aii.proxy.xiruntime.connection.timeoutInMSec in jpf.properties).
So i can somehow confirm that outgoing messages from BPM seem to be treated as synchronous in a weird way, even if it's configured as asynchronous.
Regards,
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
All right, thanks vladimir.. Please give notice as soon as you or your customer have found a solutuion. I slowly become desparate on this topic. I thought it might be caused by a too low patch level of the adapter framework or the messaging SC, so i updated all dependent SCs, but without success ...
Vladimir may I know how your customer imported his Service Interfaces?
I did import them from file to avoid ws-rm so that i can start the process from SOAP UI. When I send a request and look for the message content in the Message Monitor, i see the following tags:
<sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging>
So somehow SAP does RM anyway, and with that the synchronous messaging... Is there a possibility to disable wsrm on system side? When i look in the single service administration wsrm is disabled at least for the inbound event..
I just imported the service interfaces from ESR and started the process from wsnavigator and now it worked:
Application attempting to send an XI message asynchronously using connection JPR
Regards,
Maurice
How do you start your process flow? Via SOAP UI or the SAP wsnavigator?
I now imported every interface from ESR and deleted for the inbound interfaces every tags starting with "<wsp" or with "<ifw" from the WSDL in NWDS. Afterwards i could start my process via SOAP UI and the outbound services did send calls asynchronously
Hope this can help you,
Maurice
Regarding the example from first post:
I start iFlow1 by soapui
iFlow1 start BPM (no problem in that)
and then BPM calls iFlow2 by XI protocol - that call should be async (called SI is async) but it performs as sync.
So for your question - I start iflow by soapui but not directly - call of iFlow2 is done regardless of how I call iFlow1.
Is the question not clear? I can give an example.
Or nobody found such a behaviour?
Is this normal, that async message from BPM to iFlow through JPR is processed as sync? It looks really strange to me and I cannot find any reference to such a behavior on discussions or help.sap
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.