The JBI container itself should be able to handle the load. I think performances mainly depend on what kind of processing the system will perform. For example, if you need to keep track of all messages, it will take some processing time ...
On this point, you can use the JdbcAuditor which is already configured in the default configuration (but disabled). You can also modify it to suit your needs or implement another one using the org.apache.servicemix.jbi.events package. On 2/14/07, Felipe Gaucho <[EMAIL PROTECTED]> wrote:
my system is being designed to support 72'000 messages per hour it means: 20 messages per second, availability 24x7 (99%) no problem for ServiceMix ? any experience >= that values ? other question: the above number refer to 12 096 000 (12 million messages per week) How to you archive such messages ? That means, I will keep the message data persisted in a database for other processes (audit processes and history log). From time to time, I supose I must dump the database or clear my log directory.. do you do that through ServieMix or delegate for thid-party processes ?? -- View this message in context: http://www.nabble.com/performance-question---72%E2%80%99000-messages-per-hour-tf3226134s12049.html#a8961467 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
