So.. I'm struggling a bit here to see where this thread is going.
Let me try and piece it together.
The way the messaging ordering is currently implemented in JBM is messages are ordered
when they hit the server. This is the way it works/will work in JBM 2.0.
Ordering messages by adding a time stamp on the *client* is not something I have heard of
before, and I do not know of any other messaging systems that implement it that way.
Using a timestamp from the client would have issues with clock synchronization on the
client. The differences between timings on clients would probably far outweigh the time
taken to send a message from client to server, thus rendering it pointless. For that
reason, that option does not seem worth pursuing.
There seems to be another issue on this thread regarding how this functionality is
configured - whether the queue is configured as "ordered", or whether this is
done on the connection factory.
This second issue seems unrelated to whether we use timestamp from the client or order on
the server.
As I mentioned in my previous post I would prefer to configure on the connection factory
since this is more consistent with JBM 2.0 and also does not restrict the entire queue to
be "strictly" ordered only.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206213#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...