I am encountering a problem where my updated record will be reverted back to previous copy of the record. Following is the senario:

1. I added about 10 records and the field "requestDate" in the 10 records has set to "null".
2. Recall any of the 10 records and set the "requestDate" to the current system date.
3. Verify in SQL 2000 database and the record updated correctly.
4. Recall another record out of the 10 without updating anything, I noticed the "requestDate" field in the record updated in Step 2 has been reverted back to "null". In fact all fields in that record has been reverted back as new inserted and not what I have updated in Step 2.

I realised from the JBoss log file that the Persistant Manager is trying to flush the old data of that record back to the database. Could this be a configuration problem in hibernate-service.xml as the following:

<attribute name="DatasourceName">java:jdbc/primdb</attribute>
<attribute name="SessionFactoryName">java:/hibernate/SessionFactory</attribute>
<attribute name="Dialect">org.hibernate.dialect.SQLServerDialect</attribute>
<attribute name="CacheProviderClass">org.hibernate.cache.HashtableCacheProvider</attribute>
<attribute name="Hbm2ddlAuto">update</attribute>
<attribute name="ShowSqlEnabled">true</attribute>
<attribute name="ReflectionOptimizationEnabled">false</attribute>
<attribute name="MaxFetchDepth">5</attribute>

Anyone can advise?

Thanks in advance

I'm having the same problem (I think). I have this code



When I run the application, it generates this in the logs.



It seems that, for some reason, it's refreshing the ID, but gets the rest of the object from session cache. Does anyone know why this is happening?

Thanks,
Connor

Missed two lines in the logs. Just in case you thought I wasn't using a read lock.

My problem has solved. It is due to a session object being opened in the Web tier not closed after using.