- Use REPL_SYNC if you want immediate and guaranteed replication
- I don't understand your point about: "how do I configure the readers to not cache changes to the writer after they load new data from the database" - I thought the writer loads data from the DB and puts it into cache?
Sorry, should have been more clear. Basically, the writer is an application that process various feeds, creates hibernate objects and stores them in the database. JbossCache is used as a second level cache with hibernate. The reader applications, are responcible for reading the data and displaying to the user. I would like to make sure that when the reader application, after a restart, loads data that is not currently in cache not to send the newly loaded objects to the writer application potentially interfering with a feed load of the same data occuring at the same time.
The reason I'm worried, is due to error experienced when there are two instances of the writer using jboss cache, it seems that one can interfere with the other, corrupting the data. Using jboss cache 1.2