My website uses a combination of Django + Java apps to function. For this particular problem, a record is deleted from the DB via a TastyPie resource DELETE operation. A Django signal post_delete handler is invoked, which submits an HTTP DELETE request to Jetty running in the Java app. The Java app then performs a query using Hibernate.

What appears to be happening is that Django thinks the record was deleted. I invoke this code in the post_delete signal handler:

DynamicVolume.objects.filter(user=instance.user).count()

Which returns ZERO.

However, the Java app thinks the record still exists unless I make it sleep for several seconds before asking Hibernate to query the DB.

I've tried forcing Hibernate to clear its cache with no success. Any suggestions appreciated.

Thanks

I believe Django might be at fault here.

That's how transaction isolation works.

Django uses its own database connection and so it can read its own writes. On the other hand, Hibernate uses a separate database connection, and if Django has not got the chance to commit, Hibernate is not going to see any change that Django has issued. This is the expected behavior for any isolation level that is greater or equal to READ COMMITTED).

The solution is simple. You just have to commit the transaction in Django. If the Hibernate Session has already cached the entity that you modify in Django, you'll have to use refresh.

Thanks. I think Django has performed the write, but it is inside a transaction so it hasn't been committed. The Java process can allow a 5s delay before reading the database again so I can do that for now. It's not a big deal and doesn't affect the functionality even though technically it's a "hack".

Thanks again.