I'm currently confronted with loads of updates for entity beans (cmp) that will never been updated after their initial creation. I tried the container configuration attribute "call-ejb-store-on-clean"; set it to false. At no prevail. I'm still having these updates filling my logs. Even setting the default entity bean configuration does not change a thing. (I'm using commit-option D by the way.)
As an experiment I set the entity bean to read-only; to make sure I can see whether something makes them dirty. Suddenly everything works MUCH faster and all data comes in just fine. But of course I'm not able to create new instances any more due to the read-only attribute.
I don't know what's going on. The beans are not dirty, but still the ejbStore method is called when call-ejb-store-on-clean is set to false. Is there something else I need to set to avoid ejbStore call ?
Any clue to solve this mistery is welcome ! Thanks !
java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-b05, mixed mode)