I've run into a similar problem, which expressed itself in certain browsers.
In some browsers the url http://somehost and http://somehost:80 are treated
as different URLs. This means that the browser will not send a session
cookie created at http://somehost to http://somehost:80, and the servlet
invoked as http://somehost:80 will attempt to create a new session. We
solved this problem by always removing the port number if it was standard.
If you're not running into this problem, ensure you aren't accidentally
invalidating the session somehow.
Andre
-----Original Message-----
From: Juan Fuentes [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 1:15 AM
To: Orion-Interest
Subject: Different JSESSIONID
>
> Hi list,
>
> We're having a problem with http session. We call a servlet twice in a
> session, but the second one sends a different JSESSIONID. Although the
> original session is not expired, and the application continues working.
>
> As the second time that servlet is called it gets a different session,
> it cannot access to the attributes in the session.
>
> How is it possible, and how could I solve this problem??
>
> TIA
--
··················································
Juan Fuentes Nieto Essi Projects
[EMAIL PROTECTED] t +34 977 221 182
http://www.essiprojects.com f +34 977 230 170
··················································
