You are running the 2.1-beta of Poolman. While I did not see the specific bug you refer to (StackOverflowException), I did see other bugs, including a random and occasional NullPointerException. Since 2.1-beta has been in beta since October, and since there have been no development since then, and since the primary author has apparantly decided not to continue developing it, I suggest you rollback to the last stable version 2.0.4.
Bryan On Fri, 2002-03-08 at 08:01, Satish Jeejula wrote: > Hi All, > > I am running a web application under apache1.3.22\Tomcat3.3 using > struts1.0\poolman2.1-b1 on Windows NT server. > > After running fine for 5-6 hrs, tomcat crashes with StackOverflowException. > Then for all the requests that come afterwards, an error is thrown with huge > stacktrace (I printed it out, which came out to be 18 pages!! in length) > onto the browser. The only way that I can bring tomcat in running mode is to > restart it. > > The stack trace points to > com.codestudio.sql.PoolManConnection.setAutoCommit(Unknown Source) method. > The stack trace is repetitive after first few lines. This error is also > thrown on to tomcat console window. > > Is this problem with Tomcat or struts or poolman or with my web > application?? > > I have increased the size of heap, changed my code so that it does not print > stacktraces etc etc but to no avail. > > Any help is appreciated. > > Thanks, > Satish > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
