You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Lila Aravopoulos (JIRA)" <ji...@apache.org> on 2011/01/19 15:06:44 UTC

[jira] Commented: (WINK-252) Wink doesn't support session affinity option on WebSphere Application Server with Cluster configuration

    [ https://issues.apache.org/jira/browse/WINK-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983716#action_12983716 ] 

Lila Aravopoulos commented on WINK-252:
---------------------------------------

Hi Nick, do you have any update in reply to Dave's comment? I manage our external defects for HATS and following up on this one. Thank you. Lila

> Wink doesn't support session affinity option on WebSphere Application Server with Cluster configuration
> -------------------------------------------------------------------------------------------------------
>
>                 Key: WINK-252
>                 URL: https://issues.apache.org/jira/browse/WINK-252
>             Project: Wink
>          Issue Type: Improvement
>          Components: Server
>         Environment: Websphere Application Server V7
>            Reporter: Lori Ruffing
>            Priority: Minor
>
> In WebSphere Application Server with Cluster configuration, Wink doesn't support session affinity option (which means Wink didn't initialize an HTTP session object when it received an HTTP request from Client).  Therefore, the request will be dispatched to one server and then the other server alternately. For RESTful service with session enabled, this may be a problem. Wink team may consider to provide to enable session affinity as a possible option.
> What is session affinity?  http://publib.boulder.ibm.com/infocenter/wasinfo/v4r0/index.jsp?topic=/com.ibm.websphere.v4.doc/wasa_content/040401010702.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.