I have the sitation that a SessionBean sends 3 messages to a queue in one
transaction.
15:24:49,157 INFO [JMS SessionPool Worker-6][JMSDestinationProxy] Proxy
Message: 6 Correl: 2
15:24:49,160 INFO [JMS SessionPool Worker-6][JMSDestinationProxy] Proxy
Message: 6 Correl: 3
15:24:49,162 INFO [JMS SessionPool Worker-6][JMSDestinationProxy] Proxy
Message: 6 Correl: 4
But when I look at the timestamps something very strange happens:
Timestamp CorrelationId
| 1107527163426 4
| 1107527164357 2
| 1107527164361 3
The message with Correl-Id 4 is sent at last, never the less it has a newer
timestamp than the others. Pls remember it is the same transaction.
Furthermore (and much more important) the Correl-Id 4 is delivered before the
others and I assume the timestamp is the reason for that.
I'm using 4.0.1 with the standard jms configuration.
Help would be very much appreciated
Mike
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865214#3865214
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865214
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
