-
1. Re: Message ordering
adrian.brock Apr 18, 2003 5:15 AM (in response to seven)Can you restate the problem or provide an
example.
I'm not sure I understand what your problem is.
Regards,
Adrian -
2. Re: Message ordering
seven Apr 18, 2003 5:40 AM (in response to seven)Here is the layout:
Actors:
1. Client JVM
2. GatewayBean (SLSB) running in JBoss JVM
3. MessageBean (MDB) running in JBoss JVM
Configuration:
1. The MDB container has only one bean instance.
2. JBossMQ uses file PM.
3. GatewayBean uses java:/JmsXA queue factory.
Flow:
1.ClientJVM -> GatewayBean.sendMessage() -> puts a message in a JBoss persistent queue (queueA).
2. MessageBean consumes messages from queueA.
-----------------------------------------------------------------
The problem is that if the client sequentially (so giving a timebased order of the messages) invokes GatewayBean.sendMessage(), the MDB not always receives the messages in the same order.
In one word, the message ordering is not conserved in this "one producer"->"one consumer" scenario. Which is somehow frustrating.
Regards,
Horia -
3. Re: Message ordering - ups
seven Apr 18, 2003 7:18 AM (in response to seven)My mistake. I am using JBoss-3.2.0 and I saw too late that conf. files have changed (I was using <container-configuration> in order to overwrite the pool size of the MDB container).
Back to testing now with <invoker-bindings> conf. BTW, does 1 size bean pool guarantees really the message ordering? (I keep asking this 'cause I don't want to rely on probability). Should I even test this case?
Regards,
Horia
P.S.
1.Does <invoker-proxy-binding> support "extends"? (like <container-configuration> - so one would not have to define the whole conf. in jbossx.ml).
2. Any word about xdoclet support for those changes?