We are using several JBoss instances concurrently. The instances use identical topic names and share the same Sybase database. Non-persistent messages are "paged" into this database, when slow subscribers are not able to keep up with the high message generation rate.
It seems to us, that there is no isolation between the server instances. When we started a second instance while the already running first one had messages persisted to the database, message management of the first instance was disturbed. We suppose this happened due to the second instance trying to clean up the JMS_MESSAGE and JMS_MESSAGE_REF tables during startup. What would be an appropriate way to isolate the instances against each other: 1) Use separate databases (actually, we would like to avoid this)? 2) Use unique JMS table names per instance? 3) Use differing topic names in the instances? 4) Augment all JMS tables by an additional column "INSTANCE_ID"? Any comments and suggestions appreciated. Actually, we even would prefer a more lightweight solution for message buffering than using a fullblown database for performance reasons (also see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=104420 ). In another thread ( http://www.jboss.org/index.html?module=bb&op=viewtopic&t=95035 ) of this forum someone suggested using Apache Derby as a replacement for file persistence. If this were used as in-process implementation, this should also easily solve our multi-instance problem mentioned above. Anybody got experience with this product or something similar? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031388#4031388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031388 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
