Hello there, I wanted to share some of my trouble with the people on this list. maybe some of you knows a way out of it.
1) I am using Tomcat 3.2.4, IBM JDK 1.3, Apache 1.3.x and mod_jk. All of these are pretty much unchanged and come from YaST/SuSE 7.3 on an Intel system. 2) My Application is relying heavily on XSL (xalan 2.1.0), Dom (xerces 2.0.2), JDom and all those. They all came with Turbine 2.2 b3 and I am using that. Problem 1: when accessing the site through Apache and mod_jk, URL rewriting didn't work. That is, session tracking didn't work. URLs got rewritten, but tomcat didn't recognize the browser coming back and assigned a new session. Solution to 1: on one of my other servers I had a self-compiled mod_jk, that did the job. If you ever need a reason to not trust SuSE and their packages and distribution contact me, i'll give you plenty. Problem 2: my servers once in a while stop. Yes, they do, stop entirely. Can such a thing be blamed on a Java application? Lets say one without a memory leak? Are there known pitfalls in the interplay: JVM, Apache, Tomcat (also Xalan, Xerces, etc.) that can crash the entire operation system? This happened on a machine that had been running for monthS without any failure. The apache there was serving many applications, but this was the first Java app. No solution to that one so far and help greatly appreciated! Cheers, Alex -- _______________________________________ Questech GmbH Schwarzwaldstr. 19 79199 Kirchzarten Fon: +49 (0)7661 90 35-15 Fax: +49 (0)7661 90 35-20 www.questech.de _______________________________________ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
