[jboss-jira] [JBoss JIRA] Resolved: (JBCLUSTER-183) Session ID lost over "secure" connector

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCLUSTER-183?page=all ]

Brian Stansberry resolved JBCLUSTER-183.
----------------------------------------

    Resolution: Rejected
      Assignee:     (was: Brian Stansberry)

Please re-open in the JBoss Application Server project (JBAS).  Sorry for the hassle; the JBCLUSTER project is really meant for high level planning issues, but there's no clean way to prevent people using it to raise bugs. Issues raised in JBAS can be assigned Fix Versions that correspond to real releases.

> Session ID lost over "secure" connector
> ---------------------------------------
>
>                 Key: JBCLUSTER-183
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-183
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web Tier
>    Affects Versions: Q4Y6
>            Reporter: Sergey Zhukov
>
> I'm using AJP or HTTP connector with secure="true" attribute in JBoss cluster environment.
> On every browser's request, my JSP code got new session id (session.getId()).
> Also it affects load balancing with sticky sessions, because every new request goes to another node.
> Try it, by simple index.jsp:
> <%= session.getId() %>
> Deploy it as farm application, open in browser and click refresh several times.
> You'll see new id every time.
> I've tried this with JBoss 4.0.5 with configuration: 'all'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira