Sure, on one hand it is overhead, but on the other hand you can scale better. - Your real front-end worker threads return quicker (the delay to write a small log entry to the jms queue is way lower than writing it to the db directly) - So the number of threads simultaneously used will be lower (and thus use less memory/threads) which can be used to process more requests - you can give the mdb's that process the logs from jms to the database their own thread pool - you do can limit the number of connections for the loging component to the database e.g. by giving them their own connection pool (which lowers the burden on the db).
Once you have it in place and use it (of course, make it a reusable component, dry) it is easy to do. But... don't forget to use the date/time from when you put it in JMS if you write a date to the db, Don't use the date/time from the moment it is actually written to the db... believe me... otherwise you can get confused when reading the logs View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208332#4208332 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208332 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
