Since you are moving from one server to another this coule be caused by the structure of your deployment.

Is the directory structure of your deployment identical on both servers? If you have multiple WEB-INF directories for different portions of your site then you will end up with different sessions, unless you have other pieces of technology simulating a consistent session for you. (Such as a front end server talking to tomcat through a connector, etc, that is maintaining the session id and passing it through).

As a test try making sure that everything is deployed to the same WEB-INF directory.

Another thought... do you have any code (in the trouble area) that is ending the session (due to a timeout, invalid authentication, etc)

----- Original Message ----- From: "Rafal Markut" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, February 23, 2006 11:36 AM
Subject: Losing a session


Hello,

I use Turbine 2.1 with Torque, Tomcat 5.x and postgresql.

When I navigate on my application then suddenly HttpSession has diffrend
ID and my session information (like e.g. TurbineUser) has been lost.
It happens always in this same part of my apps (when I navigate on other
part, everything is OK).
What's more ... this application was working correctly but we made
migration on different server. This happens only on the new server.
Old server and new one - have different tomcat versions but both are
5.x.

I checked and debugged my code very carefully and I don't see any error
- in Action class comes suddenly RunData object with different sessionID
(data.getSession.getId()). When I see cookies (JSESSIONID)... it has
also different ID.

Does somebody have any idea?


With best regards,
Rafal


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to