Dear all, Part of our application has the following pattern: during the day, messages are put in the a queue for specific client. The clientID is set in a JMS Message header (clientId = 'Something'). One or two times per day, the client synch from a remote location and pick up its messages. For this we start a QueueReceiver with the selector "clientId = 'TheClientId'"
How can we improve the situation / tune performence. Let's say message cache is not used, it means that JBossMQ will first read ALL messages in this queue and then read the Blob to see if the selector matches. Is it correct? We have a Bi-proc 2GB memory machine dedicated to JBoss (DB - Postgres runs on a separate machine, same hardware). What settings should be set for the message cache. I guess that if it's high enough, all messages are both in memory and in the DB right? Any precision, let me know. I hope I am not asking too weird questions. My last two questions remains without any answer :p We will be in the next Bootcamp in Paris. Hope to see some of you there! Cheers, Stephane ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
