RE: broken webapp after upgrading Tomcat

2008-01-28 Thread ashiers
had to go into it and rename them in uppercase. This issue at least is solved...now I have other issues...more on that later in another post. Alan -- View this message in context: http://www.nabble.com/broken-webapp-after-upgrading-Tomcat-tp15124373p15135210.html Sent from the Tomcat - User

Re: broken webapp after upgrading Tomcat

2008-01-27 Thread David Smith
My first thought when dealing with linux is to verify the file permissions and/or ownership are set so at minimum the user tomcat is running as has at least read permissions on all the files in your webapp. Otherwise your logs should hold more information regarding what's happening. --David

RE: broken webapp after upgrading Tomcat

2008-01-27 Thread Caldarale, Charles R
> From: Konstantin Kolinko [mailto:[EMAIL PROTECTED] > Subject: Re: broken webapp after upgrading Tomcat > > 1) Please check how WEB-INF, classes, mvcs directories and web.xml > file names are spelled on the Linux machine. > > 2) You may configure AccessLogValve in your ME

Re: broken webapp after upgrading Tomcat

2008-01-27 Thread Konstantin Kolinko
It is strange. Looks like it should be working. 1) Please check how WEB-INF, classes, mvcs directories and web.xml file names are spelled on the Linux machine. 2) You may configure AccessLogValve in your META-INF/context.xml to log all requests that are coming to your application. See http://tomc

broken webapp after upgrading Tomcat

2008-01-27 Thread ashiers
ny ideas as to what maybe going on? Maybe Tomcat 6.0 requires something different in the web.xml file? Maybe Tomcat 6.0 requires something more that I don't have in the webapp? Please advise, Alan -- View this message in context: http://www.nabble.com/broken-webapp-after-upgrading-Tomcat-tp15