I'm having a similar problem, using websphere 5.0 on NT, with
struts. I've turned on both of these diagnostic traces
com.ibm.ws.webcontainer.httpsession.SessionContext
com.ibm.ws.webcontainer.httpsession.SessionMgrComponentImpl
and they've given me diddley squat. I've tried cookie based and URL based session management, that hasn't done anything. For a while I suspected it was a multithreaded issue, so I set websphere to serialize
thread access. Nada.
Did you ever solve your problem? Does this ring any bells?
[ April 04, 2003: Message edited by: Chris Treglio ]