I discovered a very strange behavior with the use of "Jboss 3.0.4-Tomcat 4.1" with the JDK 1.3.1 (x86).
Even with commit option B or C JBoss seamed to cache entities (entities also weren't read-only in jboss.xml).
As I changed data in the database from other applications, jboss didn't recognize this change.
With the JDK 1.4 this problem didn't appear again.
Can anybody confirm this behaviour?
For some strange reason with Commit-option B JBoss does not update the cache from the DB with JDK1.4 as well.
Its only working with commit-option C.