Hi everyone,

I have a strange problem and I'm quite sure that it's easy to solve. I'm using spring + hibernate framework in our application and i think something is missing in the picture.

Here's an example.

When I log in to our application from my desk top (PC1) as myself and log in to another PC (PC2) with another log in name and play around in both PC's I can suddenly see the data which should be seen only in my login in the PC 1 and vice versa.

Man.... this drives me crazy. I know that I'm missing something or some configuration is not done properly.

Please if you have any idea what is a miss, let me know.

Thanks a ton!

MH

Well, I guess the obvious question now is:
By what mechanism(s) were you trying to cause that only certain users saw data corresponding to them?

Gonzalo,

Thank you for your response. I don't exactly understand what is your question.

The mechanisms I'm using is Spring Framework and Hibernate. The problem seems to be that somehow the alive session (which is started first) is visible to all users who log in the application instead that the user who log in would ONLY see it. Or USER1 logs in first and when USER2 logs in (after USER1) USER2 is some cases can see the data that only USER1 should see.

Me think that I have made a mistake in Spring Framework session listeners configurations.

If you or anyone has an idea what I'm missing I really appreciate help.

MH

How do you obtain the sessions, exactly?
Do you have OSIV configured, and get the current session from SessionFactory?

Gonzales,

I obtain the session in login as request.getSession(true) and request.getSession(false) until logout.

I think that this is the main problem. Do I need to use session from SessionFactory instead of request.getSession()?

Hmmm... that would make more sense alright.

MH

(My first name is Gonzalo, last name Díaz).

Yes!
The "session" you can get from the request is an http Session (javax.servlet.http.HTTPSession), nothing to do with a Hibernate session (org.hibernate.Session).

And you cannot reuse the same Hibernate session all across your application. On the contrary, you should obtain the current Hibernate Session via SessionFactory.getCurrentSession(false) in your Java UI code.

The creation/reuse of these Hibernate sessions that you obtain with this method, is something Hibernate itself doesn't manage, so that is why you need a "managed environment" (such as Spring) in order to "pool" those sessions adequately.

In an article of mine here:

http://hibernar.org/articulos_en/spring ... xample.php

I explain in detail a minimal Spring+Hibernate setup, that you can use as a guideline.