It's absolutely affecting the way the cache operates -- your session isn't being replicated properly.
To answer your questions: 1) The only way to get rid of this logging is to set logging for JBossCacheService to FATAL. You'll lose a lot of other error messages that way, though. 2) You would need to ask this on the Tomcat lists. 3) No, we wouldn't adopt such a change; it would have to come through the Tomcat code base. Why are you storing the request in the session anyway? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952480#3952480 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952480 All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
