Marvin, Thank you. I do typically perform the operation in three steps:
$ service tomcat6 stop $ cp cas.war <target directory> $ service tomcat6 start This time I forgot to stop the service and instead did the following: $ cp cas.war <target directory> $ service tomcat6 restart It seems to me that it should stop the service fully and then start it, but apparently not. Thanks Linda Linda Toth University of Alaska - Office of Information Technology (OIT) - Identity and Access Management 910 Yukon Drive, Suite 103 Fairbanks, Alaska 99775 Tel: 907-450-8320 Fax: 907-450-8381 [email protected] | www.alaska.edu/oit/ On Wed, Mar 5, 2014 at 10:21 AM, Marvin Addison <[email protected]>wrote: > > SEVERE: A web application registered the JBDC driver > > [oracle.jdbc.driver.OracleDriver] but failed to unregister it when the > web > > application was stopped. To prevent a memory leak, the JDBC Driver has > been > > forcibly unregistered. > > Oracle components are known to produce that error and it's not related > to CAS other than you're using that driver in a storage component used > by CAS. I'm not aware of a workaround that would prevent the error > altogether. I believe many if not most deployers are in the habit of > starting and stopping the container on application restarts, which > makes the error innocuous and it can be safely ignored. If, on the > other hand, you deploy CAS with other applications in the same > container you could run out of PermGen space if not for Tomcat > unloading the class by force. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
