First Hit Session Data Replication

Question

We are using WLS 5.1 with sp3 in a cluster of three
          servers using in-memory-rep, JSP, and Apache as our proxy.
          Session data replication between a primary and secondary server
          seems to work fine except in the following case:
          1) Make first hit to the cluster. During the JSP processing of
          that hit set some HTTP session data via setAttribute().
          2) Kill-off the primary server (the one that handled the first hit).
          3)Make a second hit to the cluster, it is handled by another
          server (the secondary), the session is recognized as an ongoing
          session however the session data that was set during the first hit is not
          present in the second hit.
          If we make two hits to the first server and set data, then kill-off
          the primary server, the secondary has the data at the third hit. The
          only issue seems to be when the primary is killed after the first hit.
          Anyone have any ideas?
          Thanks,
          -darren
          

Answer 1

You can configure ClusterServlet in your web server farm (WLAS as web
          servers) to proxy JSP and servlet requests to the WLAS farm (WLAS processing
          your JSP and servlet).
          Set up in-memory replication in your WLAS farm. Session in JSP will be
          replicated.
          Cheers - Wei
          Yen Liu <[email protected]> wrote in message
          news:[email protected]...
          > Hello,
          >
          > I read breifly the section on BEA's online documentation talking about
          in-memory
          > replication and clustering.
          >
          > In it, it mentioned the ClusterServlet and configuring the
          weblogic.properties
          > file to assign servlets to the ClusterServlet so that sessions will be
          handled
          > correctly and all.
          >
          > My question is, "what about JSP" I am using a lot of JSP pages which sets
          > session parameters for the specific user into session objects.
          >
          > Any tips, recommendations will be most helpful.
          >
          > Thanks,
          >
          > Yen Liu
          > 510/870-1169
          >
          > Prasad Peddada wrote:
          >
          > > Darren,
          > >
          > > It shouldn't be the case. After your first hit, when you kill the
          primary
          > > server, when you make your next request you should find all the info in
          the
          > > session. I will post again, if we find the same problem on monday in our
          test
          > > environment.
          > >
          > > Thanks
          > >
          > > Prasad
          > >
          > > Darren Kessler wrote:
          > >
          > > > We are using WLS 5.1 with sp3 in a cluster of three
          > > > servers using in-memory-rep, JSP, and Apache as our proxy.
          > > > Session data replication between a primary and secondary server
          > > > seems to work fine except in the following case:
          > > >
          > > > 1) Make first hit to the cluster. During the JSP processing of
          > > > that hit set some HTTP session data via setAttribute().
          > > > 2) Kill-off the primary server (the one that handled the first hit).
          > > > 3)Make a second hit to the cluster, it is handled by another
          > > > server (the secondary), the session is recognized as an ongoing
          > > > session however the session data that was set during the first hit is
          not
          > > > present in the second hit.
          > > >
          > > > If we make two hits to the first server and set data, then kill-off
          > > > the primary server, the secondary has the data at the third hit. The
          > > > only issue seems to be when the primary is killed after the first hit.
          > > >
          > > > Anyone have any ideas?
          > > >
          > > > Thanks,
          > > >
          > > > -darren
          >