genman, Can you point to the lines of code which cause selectors with topics to not scale well?
Perhaps you are confused and are referring to selectors with queues, which are a really, really bad idea. rohit_mca2000, We got the idea to switch to Topics with Selectors after seeing that every other JMS implementation out there (ActiveMQ, WebSphere MQ, WLMQ) provide better slightly better performance with Topics and Selectors. Google for JMS Topics and Selectors and you'll find quite a few of them. We run about 20,000 messages per server during our peak 8 hours. We saw memory usage drop by 100M (out of 1024M) by switching from TemporaryQueues to Topics with selectors. We've also seen our full GC invocations drop by 40% and the average length of our Full GC go from 15 seconds to 12 seconds. My advice to you is this: it's not impossible to switch mechanisms (we coded it so we can do it with a properties file switch). Follow the recommended practices: Cache the connection Create a Session per thread View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3909562#3909562 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3909562 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
