np. ur welcome. JbossCache doesn't exclude the use of a database. The question is... the exact use of each. For example, database can be used only for persistence in case of a general power failure or system restart, but not for failover. Don't forget that if you use a non High Availability clustered database, then you still have a 1-point failure node. If your db server crashes, then so does all your system.
Let me search a little bit this weekend to refresh my memory and I ll send you whatever info i believe you ll find useful. In the meantime, check the url I posted previously and tell me what exactly is the purpose of your job scheduling app? To be accurate, to handle vast number of schedules, to be lossless? To execute many small jobs or fewer cpu-memory hungry jobs? You need clustering for High Availability or Load Balancing or both? I am asking these because I didn't find a do-it all in one solution :) For example if you use synchronized cache, and as every node added to the cluster brings a hell of a lot network traffic for cache synchronization, the bottleneck appears to be the network and not the Timer itself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159535#4159535 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4159535 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
