Different session handling of weblogic on SP2 and SP3

Question

          I have set up 2 weblogic servers which are using the same cookie name, and having
          the same webapp name, on the same physical machine thus
          http://127.0.0.1:7220/test (Server A).
          http://127.0.0.1:9999/test (Server B).
          Using Weblogic 6.1 Service Pack 2
          1. Access Server A
          - Server A generate a new Session ID "123456...."
          2. Redirect Link from Server A to Server B
          3. Access Server B
          - Server B generate a new Session ID "987654..."
          4. Redirect Link from Server B to Server A
          5. Access Server A
          - Reused the same session ID "123456...."
          Using Weblogic 6.1 Service Pack 3
          1. Access Server A
          - Server A generate a new Session ID "123456...."
          2. Redirect Link from Server A to Server B
          3. Access Server B
          - Server B generate a new Session ID "987654..."
          4. Redirect Link from Server B to Server A
          5. Access Server A
          - Regenerate a new session ID "ABCDEFGHI...."
          Why weblogic server handle session differently in SP2 and SP3??
          

Answer 1

I think this was a bug in SP3. You could raise a support ([email protected]) call to
          confirm.
          Rick Bongpipat wrote:
          > "Rick Bongpipat" <[email protected]> wrote:
          > >
          > >I have set up 2 weblogic servers which are using the same cookie name,
          > >and having
          > >the same webapp name, on the same physical machine thus
          > >
          > >http://127.0.0.1:7220/test (Server A).
          > >http://127.0.0.1:9999/test (Server B).
          > >
          > >Using Weblogic 6.1 Service Pack 2
          > >
          > >1. Access Server A
          > >- Server A generate a new Session ID "123456...."
          > >2. Redirect Link from Server A to Server B
          > >3. Access Server B
          > >- Server B generate a new Session ID "987654..."
          > >4. Redirect Link from Server B to Server A
          > >5. Access Server A
          > >- Reused the same session ID "123456...."
          > >
          > >Using Weblogic 6.1 Service Pack 3
          > >
          > >1. Access Server A
          > >- Server A generate a new Session ID "123456...."
          > >2. Redirect Link from Server A to Server B
          > >3. Access Server B
          > >- Server B generate a new Session ID "987654..."
          > >4. Redirect Link from Server B to Server A
          > >5. Access Server A
          > >- Regenerate a new session ID "ABCDEFGHI...."
          > >
          > >Why weblogic server handle session differently in SP2 and SP3??
          >
          > In relation to previous question.
          >
          > I have 3 qns about session creation behaviour:
          >
          > 1. When a web container receives a session cookie (eg. JSESSIONID) whose session
          > id does not exists in this
          > server, should the server create a new session ?
          >
          > 2. If a session is to be created because there is a session cookie, then should
          > the new session id
          > be the one sent or should it be a newly generated session id ?
          >
          > 3. If a new session id is to be generated, then should the new session id be used
          > to overwrite that in the cookie
          > and send it back to the client ?
          Rajesh Mirchandani
          Developer Relations Engineer
          BEA Support