this is from an earlier message which might be relevent.
You might want to check your commit-options. Jboss comes with them set to A which is cached sole access. You can try C if you have something else besides JBoss accessing the database. It will slow down the Entity beans some since there will be more database calls, but you should see the data in the database.
Occaisionally I need to directly/externally update database values for admin purposes.
Rather than change the setting in the previous post to say that JBoss is not the sole user of the database, is there anyway through some admin function where I can force an update/refresh of cached entity beans so that they will pick up the new/changed values from the db?
I'd rather do this if it is possible, rather than take the performance hit by saying JBoss is not the sole db user?