Can you confirm that all key, value and Fqn components are serializable?
First af all, thanks for your reply...
However, tha exception is thrown before my application is being deployed.
And to tell the true, I am not sure who I can test if Fqn is serializable.
I'm assuming this is a problem with Session replication, or are you using jbossCache on its own?
I believe Manik is just asking if the objects your putting into the cache (or your session object) implement the serializable interface, and if the key your using is also serializable. (Hopefully, a string or int?)
Not sure if this helps, but look and see what your adding to the cache and if it does implement Serializable.
Thank you so much for your remarks...
The exception is thrown, before I deploy my application, so I assume that this is not caused by the objects I put in cache...
I have a clustered enviroment of two JBoss 4.0.4 and I use JBossCache on them...The cache works fine when the IseReplQueue is false, but when I turn it to true, after the servers are started the exception is thrown to both of them... Maybe I need some more configurations...
Could you post more logging (trace level) that leads up to this exception?
Have you tried newer versions of JBoss Cache?
Thanks for this Brian - I've targeted this against 1.4.1.SP4, release date yet unknown.