Session Affinity WLS8.1

Question

Our setup includes .NET client communicating (via a .NET-to-J2EE bridge) with a session facade. Now, as long as the .NET client retains the client-side proxy (of the session facade), all requests are routed to the original node -- regardless of load.
For our purposes, this is desirable behavior. The problem is, I'm having a hard time explaining why this is so, especially in high load situations when one node is idle while the other is being hammered. Is it a config issue i.e. can it be turned off/on.
Also, were would I find tracing/logging information on the session cookies -- or whatever means is used to route the the request to the appropriate server.
Thanks...and pardon the lenghty post.

Answer 1

          try to use url-rewriting
          and check if you enabled cookies with your browser.
          fear
          Mark Swanson <[email protected]> wrote:
          >Hello,
          >
          >I have a Session used between several JSP pages and it works fine. However,
          >when I submit the results of a form to a servlet the Session becomes
          >null.
          >I've spent hours on this and haven't been able to find out why this is.
          >
          >JSP Code:
          >System.out.println("*** jsp sessionID:" + session.getId()); // works
          >
          >JSP calls servlet using this path:
          >(/webapp/servlet/ZZZServlet)
          >request.getContextPath() + "/servlet/ZZZServlet";
          >
          >Servlet calls this:
          >
          >HttpSession session = request.getSession(false);
          > if (session == null)
          > Logger.info(LID + "ZZZServlet HTTPSESSION FAILED")
          >
          >The session is always null. It's a 10-line JSP and a 20-line servlet.
          >
          >Does anyone see anything wrong? Any suggestions?
          >
          >Thanks.
          >