Ping!
2013/1/11 Lukasz Lenart <lukaszlenart@apache.org>:
> Thanks a lot, can I add your note to the page regarding WebSphere in
> the docs [1] ?
>
> [1] http://struts.apache.org/2.x/docs/websphere.html
>
>
> Kind regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/1/10 Vineet Kanwal <vikanwal@in.ibm.com>:
>>
>> IBM WebSphere Application Server uses the JSESSIONID information to keep
>> track of the client session. If you have an application where the
>> application client must navigate across multiple WebSphere Application
>> Server nodes residing in same domain, then the JSESSIONID information may
>> be over-written on the client because multiple JSESSIONID cookies received
>> with the same name and path.
>>
>> When persistence is disabled and if the JSESSIONID in the incoming request
>> is not found in the current session manager, then the session manager will
>> generate a new sessionId and create a session object, instead of using the
>> sessionId in the incoming request.
>>
>> To resolve this issue, configure WebSphere Application Server to reuse the
>> sessionId present in the incoming request.
>> For All versions:
>> 1. Open the administrative console.
>> 2. Select Servers > Application Servers > Server_Name > Server
>> Infrastructure > Java and Process Management > Process Definition >
>> Java Virtual Machine > Custom Properties > New.
>> 3. Add a new Custom Property for the JVM to reuse the sessionId:
>> System Property Name: HttpSessionIdReuse
>> System Property Value: true
>> 4. Save your changes and restart the Application Server.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
>> For additional commands, e-mail: user-help@struts.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
|