Thanks for this Brian - I've targeted this against 1.4.1.SP4, release date yet
unknown.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031082#4031082
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031082
Hi,
Could you post more logging (trace level) that leads up to this exception?
Have you tried newer versions of JBoss Cache?
Cheers,
Manik
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4030761#4030761
Reply to the post :
This could be related to http://jira.jboss.com/jira/browse/JBCACHE-1012.
Perhaps in earlier releases that led to an NPE?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4030813#4030813
Reply to the post :
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
Can you confirm that all key, value and Fqn components are serializable?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4029272#4029272
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4029272
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.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4029295#4029295
Reply to
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.
