Hey,

i work with Ejb3 (jboss + hibernate).
i get an excpetion when i tried to execute query because hibernate execute flush before the query and in the flush it complained that it try to persist deleted object. (i dont get any furher information)
I debug my code and i dont call to any persist during this sequence (there is also no case of changes that can cause to cascade).

I have JAD plugin in my eclipse and i put a breakpoint in the hibernate class , but it didnt stop.

Please help me to think on any idea to understand which object it try to persist.

ps. hibernate trace didnt help.
Thank you

avihaimar,

I can only suggest generalities without knowing the code in depth, but this migh help somehow:

- it makes sense that Hibernate perfoms a flush before a query, even if you didn't call it explicitly, because Hibernate promises to always return fresh data on a query.list();

- remember that Hibernate generates class proxies, therefore a breakpoint on a class won't necessarily be hit. Use logging instead. It is less gramorous, but more reliable.

- your code should not depend on a session to be flushed or not for Hibernate to "realize" an object has been deleted. Remember that, unless you flush and commit every step of the way (unlikely in a managed environment), Hibernate performs the database operations in a fixed sequence according to the type of SQL operation (see documentation 10.10: flushing the session)