jms message sent to another cluster picked before transactio

[navjeetc]

We have two separate JBoss clusters on the same machine. A stateless session bean method (transaction is enabled) on one cluster adds a domain object to the database and sends a message to the other cluster that indicates an event has occurred and the MDB (on the other cluster) goes to the database and reads the domain object just persisted. Looks like the MDB on the other machine is invoked before the session bean on the first machine commits the transaction, thereby reading the previously inserted data. We are using ClusteredXAConnectionFactory to send the message to the topic.

Is this expected behaviour or there is something wrong in the setup. I would expect the MDB on the other cluster not to execute onMessage() until the transaction on the sender side has committed.

We are using JBoss 4.2.1.GA and JBoss messaging 1.3.0.GA.

[clebert.suconic]

Can you try the same with 1.4.0.CR3? it's almost GA

[timfox]

"navjeetc" wrote:


Is this expected behaviour

Yes, this is expected behaviour.

This has been covered on a previous thread http://www.jboss.org/index.html?module=bb&op=viewtopic&t=112873

[navjeetc]

Tim,

In that case is there any point in trying with JBoss messaging 1.4.0 CR3 as suggested earlier or not?

"timfox" wrote:

"navjeetc" wrote:


Is this expected behaviour

Yes, this is expected behaviour.

This has been covered on a previous thread http://www.jboss.org/index.html?module=bb&op=viewtopic&t=112873

[clebert.suconic]

In that case is there any point in trying with JBoss messaging 1.4.0 CR3 as suggested earlier or not?

Well.. not for this issue...
I didn't understand your post before. (sorry about that!)

[timfox]

"navjeetc" wrote:
Tim,

In that case is there any point in trying with JBoss messaging 1.4.0 CR3 as suggested earlier or not?

No. This is just normal JTA behaviour, not a JBM bug.