Debugging session creation on WebLogic

I'm debugging an issue where calls to our weblogic server often return with a new JSESSIONID value, replacin开发者_开发百科g the JSESSION that was originally sent.

The issue occurs frequently, but not consistently. (Ie., when it affects you, it affects ~90% of your traffic.)

We've shown that the issue appears to be unrelated to the actual server call being made, which makes it hard for me to debug any specific method.

Is there a way to hook into the JSESSION creation in WebLogic, to see what is causing the session to be created / destroyed / invalidated?

Attaching a remote debugger would be great, but I'd settle for some form of logging that might point me in the right direction?

---

This is a standard part of the servlet spec (not WebLogic specific). You want the HttpSessionListener interface.

Note that the Servlet session stuff is really bad - the kind of behavior you're seeing can happen when memory problems kick in, etc. For a deconstruction, check out the presentation at SeaJUG (Rethinking Users and User Session Management). Slides and video are posted.

---

Nodemanager/WLST is something that is also useful in debugging and monitoring servers with Weblogic Admin, Enterprise Fusion Middleware Control, or Cloud Control.