You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by brunp <pa...@gmail.com> on 2009/07/29 17:00:33 UTC
Session variables are getting wiped out
Since moving to Jetspeed 2.1.3, it appears that some Session Variables that
are stored within the session are being deleted and access to these
variables appear to invalidate access to some functionality? Are there any
changes from 2.0 to 2.1.3 that would explain this?
--
View this message in context: http://www.nabble.com/Session-variables-are-getting-wiped-out-tp24721155p24721155.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Session variables are getting wiped out
Posted by brunp <pa...@gmail.com>.
we figured it out, emptySessionPath was missing from the AJP definition and
one app was
killin' all session variables, hence, as a result, Jetspeed was invalidating
the session.
Paul
Ron McNulty wrote:
>
> Hi Paul
>
> You will need to supply a bit more detail. Are you setting and reading the
> session attribute in the same portlet? Or perhaps setting it in a servlet
> and reading in a portlet?
>
> If so, please read the JSR168 spec - it is not too turgid. It specifies a
> "portlet session scope" and an "application session scope". I never used
> Jetspeed 2.0, but it is possible that 2.1.3 aligned closer to the JSR168
> spec and broke your code.
>
> To share session data between a servlet and a portlet, you probably need
> to
> add "emptySessionPath=true" to the <Connector element in server.xml. This
> writes the JSESSIONID cookie without a path, allowing sharing across all
> contexts.
>
> Also, is there a reason that you can't use request.getUserPrincipal() to
> get
> the user?
>
> Regards
>
> Ron
>
> ----- Original Message -----
> From: "brunp" <pa...@gmail.com>
> To: <je...@portals.apache.org>
> Sent: Thursday, July 30, 2009 4:21 AM
> Subject: Re: Session variables are getting wiped out
>
>
>>
>>
>>
>> brunp wrote:
>>>
>>> Since moving to Jetspeed 2.1.3, it appears that some Session Variables
>>> that are stored within the session are being deleted and access to these
>>> variables appear to invalidate access to some functionality? Are there
>>> any
>>> changes from 2.0 to 2.1.3 that would explain this?
>>>
>>
>> To further expand on this problem, we are setting a session variable via
>> the
>> following code:
>>
>> HttpSession session = request.getSession();
>> session.setAttribute("user", user);
>>
>>
>> and then later on, reading it in the following manner:
>>
>> User userInSession = (User) session.getAttribute("user");
>>
>>
>> This worked in our Jetspeed 2.0 implementation, so unless I missed a
>> configuration setting that prevents session variables from being stored
>> and/or retrieved, I am sort of at a loss as to why this is happening.
>>
>> Thanks
>> Paul
>> --
>> View this message in context:
>> http://www.nabble.com/Session-variables-are-getting-wiped-out-tp24721155p24722708.html
>> Sent from the Jetspeed - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Session-variables-are-getting-wiped-out-tp24721155p24755643.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Session variables are getting wiped out
Posted by Ron McNulty <rm...@xtra.co.nz>.
Hi Paul
You will need to supply a bit more detail. Are you setting and reading the
session attribute in the same portlet? Or perhaps setting it in a servlet
and reading in a portlet?
If so, please read the JSR168 spec - it is not too turgid. It specifies a
"portlet session scope" and an "application session scope". I never used
Jetspeed 2.0, but it is possible that 2.1.3 aligned closer to the JSR168
spec and broke your code.
To share session data between a servlet and a portlet, you probably need to
add "emptySessionPath=true" to the <Connector element in server.xml. This
writes the JSESSIONID cookie without a path, allowing sharing across all
contexts.
Also, is there a reason that you can't use request.getUserPrincipal() to get
the user?
Regards
Ron
----- Original Message -----
From: "brunp" <pa...@gmail.com>
To: <je...@portals.apache.org>
Sent: Thursday, July 30, 2009 4:21 AM
Subject: Re: Session variables are getting wiped out
>
>
>
> brunp wrote:
>>
>> Since moving to Jetspeed 2.1.3, it appears that some Session Variables
>> that are stored within the session are being deleted and access to these
>> variables appear to invalidate access to some functionality? Are there
>> any
>> changes from 2.0 to 2.1.3 that would explain this?
>>
>
> To further expand on this problem, we are setting a session variable via
> the
> following code:
>
> HttpSession session = request.getSession();
> session.setAttribute("user", user);
>
>
> and then later on, reading it in the following manner:
>
> User userInSession = (User) session.getAttribute("user");
>
>
> This worked in our Jetspeed 2.0 implementation, so unless I missed a
> configuration setting that prevents session variables from being stored
> and/or retrieved, I am sort of at a loss as to why this is happening.
>
> Thanks
> Paul
> --
> View this message in context:
> http://www.nabble.com/Session-variables-are-getting-wiped-out-tp24721155p24722708.html
> Sent from the Jetspeed - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Session variables are getting wiped out
Posted by brunp <pa...@gmail.com>.
brunp wrote:
>
> Since moving to Jetspeed 2.1.3, it appears that some Session Variables
> that are stored within the session are being deleted and access to these
> variables appear to invalidate access to some functionality? Are there any
> changes from 2.0 to 2.1.3 that would explain this?
>
To further expand on this problem, we are setting a session variable via the
following code:
HttpSession session = request.getSession();
session.setAttribute("user", user);
and then later on, reading it in the following manner:
User userInSession = (User) session.getAttribute("user");
This worked in our Jetspeed 2.0 implementation, so unless I missed a
configuration setting that prevents session variables from being stored
and/or retrieved, I am sort of at a loss as to why this is happening.
Thanks
Paul
--
View this message in context: http://www.nabble.com/Session-variables-are-getting-wiped-out-tp24721155p24722708.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org