Topic
  • 1 reply
  • Latest Post - ‏2014-10-10T18:00:38Z by rickchen@ca.ibm.com
AnkiaP
AnkiaP
4 Posts

Pinned topic HTTP Session Management

‏2013-11-04T08:26:45Z |

Hello

Please can you clarify the use of the following two parameter on the splicer.properties:

i) listenerMode - infocentre documentation states that if the property is set to false, the web container will not be used to generate session, but it does not specify where the sessions will alternatively be generated from.

ii) sessionCreatedOnFailover - infocentre documentation states that this property only applies when listenerMode is set to false. Please can you specify under which conditions this property should be set to true and why?

We have multiple application servers in a cluster, with remote WXS session management enabled and we need to ensure that the separate web containers do not create duplicate session IDs as this will result in one session on the remote WXS data grid being overwritten by the second session creating havoc during failover when the particular session has to be recovered from the remote WXS data grid.

I specified a unique HttpSessionCloneId on each server , but noticed that it does not get appended to the session ID key on the remote WXS data grid.

Hoping that the 2 parameters above is the answer to ensure no duplication of session IDs.

Working with WXS client 8.5.0.3 on WAS 8.5.5.0

Thanks

  • rickchen@ca.ibm.com
    rickchen@ca.ibm.com
    3 Posts

    Re: HTTP Session Management

    ‏2014-10-10T18:00:38Z  

    i) when listenerMode=false, WXS will create the session and generate the sessionId, not the webcontainer

    ii) when listenerMode=false, and a session is reconstituted, e.g. retrieved from the grid after it was pushed out of the in-memory cache or in a failover situation, WXS will by default not invoke session listeners with a sessionCreated event (because this reconstituted session is not considered a 'new' session). if your application or listeners want to be informed of this event, then set sessionCreatedOnFailover=true

    we would recommend that you set reuseSessionId=true. in a failover scenario, the original session id is maintained. having said that, the chances of generating a duplicate session id is very minimal. the default length of the session id 23 alphanumeric characters long (by default).

    cloneId is not used by WXS. it is used by the webcontainer to identify servers which have serviced a request. for WXS, this information is not required.