Author: dboutindboutin
Date: Jan 5, 2007 02:55
> What's probably happening is that at the time the remove() is called,
> the row has already been deleted from the database.
> The reason your
> finder seems to work is that the finder first looks in the container's
> transaction-based cache before looking in the back-end database, whereas
> the remove always goes directly to the database, as required by the EJB
> specification. If the row is deleted in the database (by something
> else) sometime during the transaction where the EJB was first found and
> loaded, this is the behavior you'll see.
I've checked on the database and the row was never deleted so i don't understand why it is throwing me this error.
I'm the only user of this database and my application is only used by me and the process made is known and no drop of this column is made before the error.
Regards,
Denis.
|