hi,
jboss seems to get into an infinite loop spitting out this error message
repeatedly. My application runs for a couple of hours, then this starts
happening and goes into an infinite loop of spitting out this message. I am
using JBOSS4.0.4CR2/EJB3.0 with tree cache clustering of 2 servers.
I get this error from jboss spitting out in an infinite loop. Investigating
this a bit, it's coming from the stateful session bean clustering eviction
StatefulEvicitonPolicy class. What is it trying to do? Is it trying to evict a
stateful session bean that no longer exists? How can I prevent
i'm using jboss 4.0.4CR2/ejb3 package. I think i am moving away from stateful
beans now. Even though I just have 1 stateful bean that is clustered, i'm
seeing the problem of it not clustering properly sometimes and this eviciton
error is very bad. It's a big headache.
View the original post :
i have 2 load balanced, clustered machines with 1 stateful session bean whose
clustering is turned on. Experimenting between the machines, about 1 out 7
times the stateful session bean will fail to cluster properly. It loses the
sateful session bean when i shutdown the jboss app server on one
I'm using IDENTITY generated Ids. This is for a serial (autoincrement) datatype
on the new Informix 10.0 server. I'm getting an error in which ejb cannot
return the incremented Id value as evidenced by the error below. Using a
previous version of Informix 9.4, it used to work. After it inserts
more specifically from the DEBUG. It looks like i'm losing the transaction.
Below is the problem for the bad database, and below that is the good database
(one that works).
2006-04-18 15:28:32,355 INFO [STDOUT] gettting id: null
2006-04-18 15:28:32,371 DEBUG
