When we have multiple threads concurrently running, we have an issue with proxy objects. Meaning when a thread a trying to access a domain object, it is loading the proxy object that is attached to a different session. I do not see any reason why it loads the other session instead of loading the object into the same session. So I am not sure how i could eliminate this issue. Though I am creating a new session per thread, I do not see any issue when one thread is getting executed. This is a race condition and happens only when i have multiple requests simultaneously running.

Any hibernate gurus? Help is greatly appreciated. Thanks in advance.

I think the proxy is tied to the session that first created the proxy object, and since a session is not thread-safe it will of course be problematic to use the proxy in a way that causes it to be initialized from another thread. Simplest way to ensure that an object is tied to the correct session is to use Session.get(). Eg. something like:

see for below reply.

Hi nordborg,

Thanks a bunch for your reply.

Yes, we are using session.get only. Also, we will only an id available initially and so we will load an obj by id. So I can not have an if condition check here.

If the sessions are not thread-safe, then how I could i resolve the issue? And also we have a proxy object containing a list of many-to-one proxy children too.

Help is really appreciated.

What do you do with the object once you have loaded it with Session.get()? Are you passing it on to another thread? When does the race condition happen? Can you post some code examples to clarify?