Here is some more information on the problem. From a developer: "According to the document that the link below refers to, a single instance of Tomcat will have multiple JVMs, where each JVM represents a virtual host. The following link clearly states this virtual host concept as it applies to Tomcat. http://jakarta.apache.org/tomcat/tomcat-3.2-doc/uguide/tomcat_ug.html (please refer the virtual host section).}"
"As per the above document, each JVM corresponding to a virtual host contains a database connection pool object. Hence the connection pool that has been implemented seems to be in-line with the virtual host definition in the above document. "Also, we are also using the same concept of DBCP in our applications. The difference in our case is that we have chosen to use Oracle that also uses the same DataSource class." OK, it is my understanding that the problem of a new JVM for each virtual host was fixed in 4.X. True? I RT'ed some more FM on 4.2 and found that the Tomcat developers suggest that the connection code be placed in $CATALINA_HOME/common/lib. I passed that to the developers and: "As regards putting the flood.jar in $CATALINA_HOME/common/lib, we tried it and the behavior was no different." Is there anyone running tomcat with virtual hosts and do you also have this problem? It is a little hard to beleive this is so difficult to implement but hasn't come up before. (at least I couldn't find it in the archives) -- Stephen Carville UNIX and Network Administrator DPSI 310-342-3602 [EMAIL PROTECTED] -- Most people prefer believing their leaders are just and fair even in the face of contrary evidence. Perhaps this is because, once a man acknowledges that the government he lives under is corrupt and cares nothing for justice or fairness, that man also has to choose what he will do about it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
