-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Channel destinations are not always executing in order for synchronized channels #900
Comments
Check if this has been resolved in 1.8. Imported Comment. Original Details: |
This doesn't seem to be fixed. Below are the results of my tests: Channel A:
Channel B:
Test # 1:
Test # 2:
Order of destination execution seems random when "Wait for Channel Response" is set to NO. Imported Comment. Original Details: |
Set the synchronous property on messages to the receiver channel's synchronous property rather than the sender's. For VMRouter.routeMessage() when useQueue = false and synchronized = true the router has the same behavior as wait for response. Any other combination does not wait for response. Recommended usage is only using routeMessage(String channelName, String message, boolean useQueue), with useQueue assuming the same behavior as !waitForResponse. Imported Comment. Original Details: |
Channel A contains a channel writer, which writes to channel B. Both Channel A and Channel B are syncrhonized. Both channels have two or more destinations. Channel B has a soap sender destination and a javascript destination. Expected result is destinations in both channels should run in order.
What I found is that if Channel A sends a message to Channel B the destinations in Channel B are only guaranteed to execute in order if Channel A's Channel Writer destination is set to Wait for Channel Response. If Channel A's Channel Writer destination is not set to Wait for Channel Response then even if Channel B is synchronized it's destinations are not guaranteed to execute in order.
I think this is a bug, a channels destinations should execute in order if the channel is set to synchronized, regardless if the sending channel is waiting for a response.
Imported Issue. Original Details:
Jira Issue Key: MIRTH-895
Reporter: jerchap
Created: 2008-08-06T11:56:27.000-0700
The text was updated successfully, but these errors were encountered: