Wallace - Thanks for your thoughts. It would seem though that timeouts are allowed since many of the flow steps (like BRANCH, LOOP, INVOKE, MAP, etc.) have “timeout” as an optional property.
What’s happening in our scenario is that we are intentionally sending bad SQL to Oracle (to test Exception handling in a transaction). Instead of returning a SQLException, Oracle seems to be locking the table I want to update and never returning control back to my wM service. When this happens, I want my wM service to time out and raise an Exception after a configurable amount of time. This is not happening.
I’m guessing that someone in wmUsers has run into this scenario and may be able to shed some light. Thanks in advance.