Sudden and unexpected exception at Tomcat startup

Hi. Does someone have an idea of what is going as per the logfile catalina.out below ? What is this IOException all about ? This is a Tomcat 5.0.x under Suse Enterprise Linux 10.1, which had been working fine until now and suddenly logs this at startup. This Tomcat runs under an IBM JVM

Re: Sudden and unexpected exception at Tomcat startup

Well, the exception looks like, as if somebody has tried to change the name of the user-realm from /srv/www/tomcat5/base/conf/tomcat-users.xml to /srv/www/tomcat5/base/conf/tomcat-users.xml.new . AFAIK Tomcat will never ever change configuration-files, except creating new context-definitions when

Re: Sudden and unexpected exception at Tomcat startup

Thanks for your answer and tips. Gregor Schneider wrote: Well, the exception looks like, as if somebody has tried to change the name of the user-realm from /srv/www/tomcat5/base/conf/tomcat-users.xml to /srv/www/tomcat5/base/conf/tomcat-users.xml.new . Do you have any idea where one would do

Re: org.apache.jasper.JasperException: java.lang.ClassCastException: org.apache.catalina.util.DefaultAnnotationProcessor cannot be cast to org.apache.AnnotationProcessor

I get the solution; the problem was in catalina.jar that was in my web application, i deleted it from my web application and let the one in tomcat/lib, every thing is ok -- View this message in context:

Re: Sudden and unexpected exception at Tomcat startup

André, it lookes as if Tomcat indeed tries to write to a file tomcat-users.xml.new as indicated in this thread: http://mail-archives.apache.org/mod_mbox/tomcat-users/200508.mbox/%3c4381.80.136.127.17.1122968130.squir...@mailserver.kippdata.de%3e That's really new to me, and I don't see any

Re: Sudden and unexpected exception at Tomcat startup

Hi Andre Tomcat DOES in fact rewrite the tomcat-users.xml file during startup. This has been mentioned on this list several times as being insecure but the general opinion is that you should not be using the MemoryUserDatabaseRealm in production. Actually, I found that not only does it

java.sql.SQLException: Already closed..strange!

Hello guys, I've a strange problem with my jsp application. I use Tomcat 6.0.18. I use connection pool with dbcp and this is context.xml of my application ?xml version=1.0 encoding=UTF-8? !-- Connessione al db sul server jsys-- Context path=/xxx docBase=xxx debug=5 reloadable=true

Re: java.sql.SQLException: Already closed..strange!

You're probably running into the fact that MYSQL closes connections which have been open too long. Probably if you make the request to the server again, you'll find that it works because the connection is reopened. One way to deal with this is to add the following to your context.xml

RE: Using precompiled JSPs

Thanks, its work. The jsp mapping wasn't set correctly. -- View this message in context: http://www.nabble.com/Using-precompiled-JSPs-tp21124710p21196649.html Sent from the Tomcat - User mailing list archive at Nabble.com. -

JPA/Hibernate persistence and MySQL connection timeout

Hi All, I'm using: Tomcat 6.0.18; Mysql 5.0.51a; Java 1.5; Hibernate 3.2; (no spring) MyApp utilizes five (5) distinct mysql catalogs (databases). Originally all 5 were accessed using JDBC/JNDI with Resources that all look like this (in webapps/MyApp/META-INF): Resource

RE: java.sql.SQLException: Already closed..strange!

DBCP documentation says you need to validateConnection(connection) before you close it e.g.http://wiki.apache.org/commons/DBCPMartin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official

Re: java.sql.SQLException: Already closed..strange!

Can you post relevant portions of your code? This smells like your code is accessing the underlying connection object DBCP wraps and closing that instead of the DBCP connection object. That'll subvert DBCP and give you problems. --David gbattine wrote: Hello guys, I've a strange problem with

Re: java.sql.SQLException: Already closed..strange!

DBCP documentation says you need to validateConnection(connection) before you close it No you don't. Just close the connection DBCP returned when you called DataSource.getConnection() --David Martin Gainty wrote: DBCP documentation says you need to validateConnection(connection) before

Deploy WAR on ROOT without losing Manager application

We need tp have our application accessed from the Root context /. So we usually delete the ROOT.war and rename our application to ROOT.war. This works well of course but we lose the benefit of using the Tomcat manager. What would be the best way to obtain that? I don't understand Virtual Host

Re: Deploy WAR on ROOT without losing Manager application

2008/12/29 nodje nodje...@gmail.com: We need tp have our application accessed from the Root context /. So we usually delete the ROOT.war and rename our application to ROOT.war. This works well of course but we lose the benefit of using the Tomcat manager. No, you are not loosing it. The