0

Context/Set-Up

We are using open-session-in-conversation-filter pattern in our application w/ Spring & Hibernate integration.

We are using Springs declarative transaction mgmt using the org.springframework.transaction.interceptor.TransactionProxyFactoryBean.

When the application gets a request we do multiple database activities (insert/updates) where update & inserts are individually flushed to database and transaction is committed.

Problem

Let's say for one of the insert/update there is a database exception thrown the hibernate session is closed as expected since the session is in an invalid state.

Even after this if I do not want to return the request back and want to continue with my request and complete the other activities I cant because the session is closed and any successive calls through this session fail and it's obvious why.

I need help in writing a solution where I can close the existing session and open a new one and attach the latest session to the thread using TransactionSynchronizationManager but not sure how to do that since there are many places where I might need to do this in the flow, is there a generic way to do this ? And is it even correct design?

And even if I achieve this what about the entities which are detached from the previous session how can I automatically attach to the new session so that proxies will work seamlessly?

Vlad Mihalcea
  • 142,745
  • 71
  • 566
  • 911
Mayur
  • 303
  • 1
  • 3
  • 14

1 Answers1

0

We are using open-session-in-conversation-filter pattern in our application w/ Spring & Hibernate integration.

The COnversation pattern just like the Extended Persistence Context in Java EE works just like you described here. If you get an Exception, you will have to discard everything and start from scratch.

Now, if you want more flexibility, you can just use detached entities and use a new Session in every request which will merge the detached entities.

However, what if an entity state will always cause the exception? How can you determine the entity and simply ignore it? What if it's linked to other entities.

Therefore, there is no simple solution to this issue. What you can do is:

  1. Capture the initial state using the initial entities your read from the DB and store it in the HttpSession, Redis, etc.
  2. Store the info submitted by the user, so if you get an exception, you can re-render the UI with the very same changes along with the error message.

This way, the users will not lose the changes they did and based on the error message they can retry after applying corrections.

Vlad Mihalcea
  • 142,745
  • 71
  • 566
  • 911
  • thank you Vlad for quick reply . i was referring to a different problem where i want to continue with the same request even if one of my updates failed and continue with the other activities ,but in order to do so i need to create a new session and attach all the entities to it.Does this need to be done manually because i may not have a track of all the entities to the older session ? and is there a common place/template class where i can create this session so that any of my transaction fails i should create a new session ? – Mayur Apr 17 '18 at 13:05
  • 1
    Yes, you'll have to do that manually. That's why you are better off doing what I suggested you instead. – Vlad Mihalcea Apr 17 '18 at 15:21