This content has been marked as final.
Show 4 replies
-
1. Re: CMP2.0 Beans refresh problem (or feature?)
dsundstrom Dec 11, 2002 1:08 PM (in response to fmarchioni)What version of JBoss are you using?
What commit option are you using? If you are using commit option A (default in for ejb1.1 beans), modifing the database out of band (directly) is not allowed.
This error is caused by putting an already existing key into the entity cache. -
2. Re: CMP2.0 Beans refresh problem (or feature?)
fmarchioni Dec 11, 2002 4:56 PM (in response to fmarchioni)Hi thanks for your reply
I'm using JBoss 3.0.0. and EJB 2.0
Honestly I don't know what commit option I have set,
I simply didn't set anything concerned with it...
Francesco -
3. Re: CMP2.0 Beans refresh problem (or feature?)
dsundstrom Dec 24, 2002 5:49 PM (in response to fmarchioni)You need to upgrade to 3.0.4.
-
4. Re: CMP2.0 Beans refresh problem (or feature?)
lafr Dec 26, 2002 11:03 AM (in response to fmarchioni)I get this same behaviour on JBoss-4.0.0alpha but not on JBoss-3.0.4.
I use "Standard CMP 2.x Entity Beans" with commit-option B.
Does this mean the change which solved that problem in JBoss-3.0 has not been ported to JBoss-HEAD ?