I don't think that has changed, but I could be wrong. One thought is that
unless you have a lot of apps using the DB you could move the resource to
the context for the app. Then only the app would have to be restarted.
But that begs the question, if you are changing the global db resource what
are the apps doing? If you are making a change such as this why is
restarting Tomcat an issue?
Just trying to understand to better help.
Doug
- Original Message -
From: quentin.compson [EMAIL PROTECTED]
To: tomcat-user@jakarta.apache.org
Sent: Monday, April 11, 2005 11:08 PM
Subject: change to server.xml requires restart 5.5.4
tomcat 5.5.4 on win2k server, jvm 1.4.x
it seems that every time i make a change to the server.xml (db connection
pools), i have to restart tomcat. i assume thats normal, but i was hoping
maybe
not to have to do it. or maybe 5.5.9 supports something like this?
thx
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
