Hi Filip or anyone, I got lost in this?: "but your stack trace show TransactionSession, and it could be that your TransactionSession is holding a reference to the Tomcat session, but the reference it is actually holding is a facade object, and the facade loses it connection to the delegate, hence the facade method.
Make sure you always get your reference to the session using the servlet API, and do NOT store a reference to it, as it is not the real session, just a facade object. " Transactionsession holds a reference to the tomcat session. This transactionsession object is part of a bean that is set in the response object. Can the tomcatsession be lost somewhere? -- View this message in context: http://www.nabble.com/Servlet-session-becoming-null-tf2028584.html#a5582709 Sent from the Tomcat - User forum at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
