It's strange, but the behaviour I described above is not reproducable. I checked in
the DB and found many rows where the correct value (119773) was written.
I identified six cases where this behaviour occured, and for all of them, there are other
rows in the DB where the value was written correctly.
Strangely, of the six cases I identified, 3 respectively 2 occured with the same ID.
Again, in other rows, those very same IDs were written correctly.
In all cases, the bit #16 changed from 1 to 0.
Does anybody have an idea what could be the cause for this strange behaviour?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005253#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...