Hello,

I'm having a random problem while deleting an object. Once in a while, it seems that the delete is being executed twice by hibernate, the second one resulting in an exception (cf. trace).

Have you ever seen such a behaviour ?
Thank's for your help

Jim


Hibernate version:3.0.3


/*** /
Ctlg catalog = DAOFactory.getCatalogDAO().getCtlg(cd, rav, secondLoc);
if (catalog != null) {
...
}
DAOFactory.getCatalogDAO().delete(catalog);



/*** /
public void delete(Ctlg catalog) {
Transaction tx = getSession().beginTransaction();
try {
getSession().delete(catalog);
tx.commit();
} catch (Throwable e) {
tx.rollback();
throw new DAOException( "Error deleting the catalog : " + catalog.toString(), e);
}
}


[2005-10-07 13:41:58.036] delete from CTLG where CD='XX' and RAV=' YYY' and SECOND_LOC='T1 '
[2005-10-07 13:41:58.036] delete from CTLG where CD='XX' and RAV=' YYY' and SECOND_LOC='T1 '
[2005-10-07 13:41:58.048] org.hibernate.event.def.AbstractFlushingEventListener addToBatch Could not synchronize database state with session org.hibernate.HibernateException: Unexpected row count: 0 expected: 1
at org.hibernate.jdbc.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:32)
at org.hibernate.persister.entity.BasicEntityPersister.delete(BasicEntityPersister.java:2059)
at org.hibernate.persister.entity.BasicEntityPersister.delete(BasicEntityPersister.java:2203)

It is weird but it seems to happen only with IE. With Mozilla, it seems that it never happens ???

I have more informations :
When it happens, there are 2 same requests being sent to websphere.

My session is being opened by the first query and all my sessions are closed at the end of that request's treatment.

So, it seems that the second delete is performed in another session, and that when it tries to find if it exists


So in that case i'm having in 2 different sessions the same object. And hibernate tries to delete it in the 2 sessions nearly at the same moment.

Should i use the get method to avoid that or what else can be done ?
Thank's

Jim

Hum, it seems my fellow, that created the frontend, created that bug.

I'm going to check that, but it seems he submits his form twice. And firefox is managing this whereas ie is not.

Jim