Maybe I should describe what the MDB does. My messages have keys (messageKey). The Sender will put a 'notification message' on the queue for each new key in one transaction. These messages only have a property messageKey. The MDB is listening on these messages (message selector). Upon onMessage it locks the key to ensure that no other MDB is working on that key. After that it sets up a queue receiver to receive the 'data messages' for that key (queue_keystream_data is not null and messageKey=7) and processes them. (In my simple scenario it just sends the message to another queue) Ever message is its own transaction here.
If no more are to be received, it closes the consumer and unlocks the key. After that it opens a QueueBrowser with the same message selector to check whether any new messages arrived in the mean time. Here is my second problem. I sometimes loose messages (forget them on the input side) and it seems that happens because the queue browser somtimes does not have elements although there are some on the queue. This whole thing is to ensure that messages with the same key are processed in the right order. Refering to me last post; therefore I know the messages of messageKey 7 go to the OUT queue in the right order, but the retrieving client does not get it that way. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865532#3865532 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865532 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
