How can I take advanatge of the fact that a container will instantiate multiple instances of a MDB to process JMS messages concurrently, without destroying the order in which messages should be processed ? For example, suppose I define a MDB which processes messages published on a single topic, where the messages communicate state transitions to be applied to Entity Beans. While it is acceptable to process messages concurrently for different Entity Beans, it is _not_ acceptable to process messages concurrently (and therefore potentially out of order) for the same Entity Bean, as this might put the Entity Bean in an inconsistent state. One possibility would be to restrict the container to at most one instance of the MDB, thus ensuring serialization, but this may cause a bottle-neck and eliminate all potential concurrent message processing. Another possibility would be to have different MDBs for different messages "types", and serialize message processing for each type, however I can't see how this could be defined. Does anyone have any experience of trying to solve this problem, or have any suggestions ? Regards William Ferreira _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
