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

["Nick Gallardo (JIRA)" <ji...@apache.org>]

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

Nick Gallardo commented on WINK-252:
------------------------------------

Hi Lori,

I see what you're saying and understand your expectation here.  My concern with this scenario is that it's asking Wink to create a session for every request regardless of whether or not the client or service choose to participate in such.

There is a way to handle this today.  Within the endpoint implementation, if you call: 

HttpSession.getSession() from within the endpoint impl, then that will give you the functionality you're looking for.  The session is accessible from the HttpServletRequest that can  be injected as a parameter on the resource method.

Here's a link to the javadoc for the servlet that describes the behavior.

http://java.sun.com/javaee/5/docs/api/javax/servlet/http/HttpServletRequest.html#getSession%28%29

Are you able to change your application to use this API for enabling session affinity?

Best,

-Nick

> 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.