You can ignore the boot.log entry - it is debug. Ditto for the first entry you posted for the server.log.
But this error indicates to me that you have made some other change that you did not mention:
2009-04-09 21:29:30,425 ERROR [org.jboss.security.auth.spi.UsersRolesLoginModule] (main) Failed to l
oad users/passwords/role files
java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224812#4224812
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224812
The following sentence makes me believe the only consistent cache strategy is using a single database for all nodes in the cluster. It is in "Chapter 2. Core Concepts" of hibernate 3.3.1 guide:
Concurrent cache updates of the same entity anywhere in the cluster should not be possible, as Hibernate will acquire an exclusive lock on the database representation of the entity before attempting to update the cache.
Should I be using the same DB for all nodes?
Is there any solution you can think of to be using one DB per node and have the DBs in synch as the cache is ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224809#4224809
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224809