[
https://issues.apache.org/jira/browse/WINK-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101064#comment-13101064
]
Bruce Ke commented on WINK-252:
-------------------------------
Nick, can you help to response Dave's question, or let us know the latest
status of this, or future plan? We need this information to make decision how
to handle HATS related defect. Thanks.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
