Yeah, it's definitely not working for me when it comes to JDBC connection
pooling. For whatever reason, my servlet that instantiates the connection
pool can't reconnect to my database after an auto-reload -- even though the
tomcat logs show the servlet being destroyed and re-initialized.
I'm using the DbConnectionBroker from javaexchange.com and would be
interested in hearing if anyone else has the same problem. I'm not planning
on using auto-reloading in production, but it makes development a pain
having to restart Tomcat and Apache all the time.
Thanks,
--jeff
----- Original Message -----
From: "Boris Niyazov" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 29, 2001 8:59 PM
Subject: Re: Reloading Servlets
> Do not reboot. Just shutdown and restart tomcat. In 3.2.1 release notes
it's
> said that reloading classes is experimental feature and is not garanteed
to work
> 100%. I have similar problems with reloading my beans. Nobody answered my
> question so far, so I tend to beleive the doc is right: reloading does not
work
> all the time.
>
> *********************************************************************
> * Boris Niyazov Ph: 212-854-4094 Fax: 212-854-1749 *
> * Systems Manager Email: [EMAIL PROTECTED] *
> * Columbia Law School URL: http://www.law.columbia.edu *
> *********************************************************************
>
>
> >
> >
> >Hi,
> >
> > I've been writing servlets, testing them as I go with my
> >Tomcat-Apache Server and Netscape... I've run into the problem
> >that sometimes, not all the time, when I refresh a servlet to see
> >changes, it's not changed? I closed Netscape, deleted my
> >web cache, and closed Kawa. But still the next time I run it, it's
> >still there unchanged... Usually I have to re-boot... is Tomcat
> >or Apache Caching my servlets? Any Ideas on how to fix this?
> >
> > Thanks in Advance,
> >
> > Colin Morris.
> > [EMAIL PROTECTED]
> >
> >
>
