We have an ESB Process that has a Topic as it's entry point.
When the ESB Process starts it uses the message contents to do three calls to External Web Services using the Sonic Connect Client, then ends. The Web Service calls are sequential (not fanned out). The Process also has a logging feature, implemented by CXF Interceptors, that records and timestamps the SOAP Envelopes for each Web Service Exchange.
When a number of messages arrive at the topic I expected to see the messages all being processed in sequence, like:
- Message_1, WSCall_1, Out/In
- Message_1, WSCall_2, Out/In
- Message_1, WSCall_3, Out/In
- Message_2, WSCall_1, Out/In
- etc
Instead, we see, based on the timestamps, that the steps are being interleaved so we get:
- Message_1, WSCall_1, Out/In
- Message_1, WSCall_2, Out/In
- Message_2, WSCall_1, Out/In
- Message_3, WSCall_1, Out/In
- Message_4, WSCall_1, Out/In
- Message_5, WSCall_1, Out/In
- Message_1, WSCall_3, Out/In
- Message_2, WSCall_2, Out/In
- etc, with the WS Calls for the different messages interleaved, but ultimately in sequence.
Note that the Out/In pair for a WS Call are always together in the sequence. There are never any operations for other messages between them.
Can anyone suggest an explanation of what is happening here?
Why aren't they in sequence?
Thanks
Steve
Could it be that you have more than one listener for the process defined?
Or maybe more than one listener for a service step?
Are you using intra container messaging ?