On this high christmas server load, the most rare problems seem to face at a higher rate... The worst one is that with our tapestry app (4.0), on rare occasions on concurrent requests (really concurrent, on the apache logs they show with <1s difference) from different users, the ASOs get swapped between requests from different users!!! In Tapestry 4.0 most internal services seem to be have singleton instances in the engine with very few threaded services. Could this affect concurrent requests being executed *at the same time*? Any chance this could come from Tomcat/JK? Anyone heard of such issue (tomcat 5.5.17)?
-- Henri Dupre Actualis Center
