Timer Boundary Even - How does it work?

[ergates]

We have a Receive Task that waits for a signal.  There is a listener that triggers when a JMS message arrives and signals the Receive Task.

This works fine.

However we would like to add a timer to the Receive Task in case the JMS listener never triggers.

So we added a Timer Boundary Even on the Receive Task.  The timer waits for 10 seconds and then triggers.
This works as well.

Now to the problem.  When the timer is active on the task, if the task receives the signal, in other words the expected behavior, the timer seems to not be stopped.  So when the process continues the timer activates and interrupts the flow.  This seems counterproductive.

Is this the expected behavior?  If so, how are we expected to model the behavior we need?

We are on version 5.13 using Oracle for our database.

[jbarrez]

No this is most certainly not expected behaviour. The timer is removed once it goes past the receive task.

So one thing I could think is that somehow the signal and timer fire at the same time, but stll then the transactionality should solve it for you. Do you have a simple unit test that I could try that has that piece of business process xml in it?

[ergates]

Not exactly sure what happened here, but the problem resolved itself.   Thanks for answering.