Re: Tomcat error
Just thought i'd add that this error might be something completey different and not necessarily the reason why Tomcat is throwing LifeCycle exceptions.. just i saw the error and put 2 and 2 together.. - Original Message - From: "Claire Wall" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Monday, February 02, 2004 6:04 PM Subject: Tomcat error I know this is the Struts mailing list but replies are nice and quick here that i'm gonna post my query to you guys (and gals) Tomcat keeps on throwing LifeCycle exception errors and produces this error in the log file: 2004-02-02 17:54:57 StandardManager[/ApplicationName] IOException while loading persisted sessions: java.io.EOFException java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.ja va:2423) at java.io.ObjectInputStream.skipCustomData(ObjectInputStream.java:1783) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1509) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1425) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1616) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322) at org.apache.catalina.session.StandardSession.readObject(StandardSession.java: 1369) at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.j ava:864) at org.apache.catalina.session.StandardManager.load(StandardManager.java:440) at org.apache.catalina.session.StandardManager.start(StandardManager.java:655) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2572) at org.apache.catalina.servlets.ManagerServlet.reload(ManagerServlet.java:802) at org.apache.catalina.servlets.HTMLManagerServlet.reload(HTMLManagerServlet.ja va:501) at org.apache.catalina.servlets.HTMLManagerServlet.doGet(HTMLManagerServlet.jav a:151) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:551) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) at java.lang.Thread.run(Thread.java:536) I'm guessing that this is because there are some non-serialized objects tr
Tomcat error
I know this is the Struts mailing list but replies are nice and quick here that i'm gonna post my query to you guys (and gals) Tomcat keeps on throwing LifeCycle exception errors and produces this error in the log file: 2004-02-02 17:54:57 StandardManager[/ApplicationName] IOException while loading persisted sessions: java.io.EOFException java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2423) at java.io.ObjectInputStream.skipCustomData(ObjectInputStream.java:1783) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1509) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1425) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1616) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322) at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1369) at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:864) at org.apache.catalina.session.StandardManager.load(StandardManager.java:440) at org.apache.catalina.session.StandardManager.start(StandardManager.java:655) at org.apache.catalina.core.StandardContext.reload(StandardContext.java:2572) at org.apache.catalina.servlets.ManagerServlet.reload(ManagerServlet.java:802) at org.apache.catalina.servlets.HTMLManagerServlet.reload(HTMLManagerServlet.java:501) at org.apache.catalina.servlets.HTMLManagerServlet.doGet(HTMLManagerServlet.java:151) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:551) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:536) I'm guessing that this is because there are some non-serialized objects trying to be persisted in the session but its not allowing it because these objects are non serializable. Of course i could be completely wrong, which i probably am :-Þ Anybody have an idea what this error could be? It's causing problems because the exception tomcat is throwing is saying that there is a LifeCycle exception and that the path '/ApplicationName' has already been started, even though it clearly is not running. Any help would be
RE: Tomcat error with compiling JSPs
I have mine installed and working fine with a CATALINA_HOME of "D:\Program Files\Apache Group\Tomcat 4.1". I had trouble with the J2SDK and JASPER until I changed those environmental variables/paths to be the short names of the paths (i.e. without spaces). Those can be seen using the command "dir /x" from a command prompt window in Windows NT/ME/XP/etc. :) So, while my long path is: D:\Program Files\Apache Group\Tomcat 4.1 My short path for CATALONA_HOME is: d:\progra~1\apache~1\tomcat~1.1\ Regards, David -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 10:47 AM To: Struts Users Mailing List Subject: Re: Tomcat error with compiling JSPs I expect politicians to lie not engineers! *Glad that solved your problem* Martin - Original Message - From: "Claire Wall" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, January 15, 2004 8:56 AM Subject: Re: Tomcat error with compiling JSPs > sorry, i lied before - the JAVA_HOME variable is pointing to the bin folder > of the JDK. > > we have just reinstalled Tomcat (4.1.2) again to a path that has no spaces > and it now works. However, this doesnt solve the problem because as stated > before, we cannot dictate what path our client has their tomcat installed > in. > > > - Original Message - > From: "Martin Gainty" <[EMAIL PROTECTED]> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Sent: Thursday, January 15, 2004 1:43 PM > Subject: Re: Tomcat error with compiling JSPs > > > > I ran into this exact error when I installed IBM JDK with Websphere and > all > > of a sudden my JSP > > wouldnt compile on Tomcat > > What is your JAVA_HOME pointing to? > > Regards, > > -Martin > > - Original Message ----- > > From: "Claire Wall" <[EMAIL PROTECTED]> > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > Sent: Thursday, January 15, 2004 8:44 AM > > Subject: Re: Tomcat error with compiling JSPs > > > > > > > the classpath of the server only points to the bin folder of the JDK. > > > > > > It still doesn't explain why this application isnt working and all of > the > > > rest are, since all our applications are installed via a WAR file and I > do > > > not change or set a class path for each application - I only change the > > > paths that need to be changed in web.xml and struts-config.xml for the > > > application. We have been developing this application on Tomcat on > another > > > server and it works fine. > > > > > > What reasons are there for the java compiler to not be able to compile > JSP > > > files for a particular application as this appears to be the problem. > > > > > > > > > - Original Message - > > > From: "Max Cooper" <[EMAIL PROTECTED]> > > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > > Sent: Thursday, January 15, 2004 1:31 PM > > > Subject: Re: Tomcat error with compiling JSPs > > > > > > > > > > This seems telling: > > > > > > > > [javac] javac: invalid flag: C:\Program > > > > > > > > It seems like some kind of path with a space in it is being passed to > > the > > > > compiler, but it is not being quoted properly. > > > > > > > > javac -classpath C:\Program Files\somelib\lib.jar ... > > > > > > > > (should be: javac -classpath "C:\Program Files\somelib\lib.jar" ...) > > > > > > > > However, I would kind of expect the error to be "invalid flag: > > > > Files\somelib\lib.jar" in that case, since the C:\Program part is > before > > > the > > > > space. Could you have some kind of funky classpath like > "C:\dir\lib.jar; > > > > C:\Program Files\poop\stuff.jar" (note the space after the ';'). Are > you > > > > setting the classpath for the server process yourself, perhaps by > > starting > > > > Tomcat using your own script (rather than startup.bat)? Or do you have > > > some > > > > strange classpath in your environment before you start Tomcat? > > > > > > > > -Max > > > > > > > > - Original Message - > > > > From: "Claire Wall" <[EMAIL PROTECTED]> > > > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > > > Sent: Thur
Re: Tomcat error with compiling JSPs
I expect politicians to lie not engineers! *Glad that solved your problem* Martin - Original Message - From: "Claire Wall" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, January 15, 2004 8:56 AM Subject: Re: Tomcat error with compiling JSPs > sorry, i lied before - the JAVA_HOME variable is pointing to the bin folder > of the JDK. > > we have just reinstalled Tomcat (4.1.2) again to a path that has no spaces > and it now works. However, this doesnt solve the problem because as stated > before, we cannot dictate what path our client has their tomcat installed > in. > > > - Original Message - > From: "Martin Gainty" <[EMAIL PROTECTED]> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Sent: Thursday, January 15, 2004 1:43 PM > Subject: Re: Tomcat error with compiling JSPs > > > > I ran into this exact error when I installed IBM JDK with Websphere and > all > > of a sudden my JSP > > wouldnt compile on Tomcat > > What is your JAVA_HOME pointing to? > > Regards, > > -Martin > > - Original Message - > > From: "Claire Wall" <[EMAIL PROTECTED]> > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > Sent: Thursday, January 15, 2004 8:44 AM > > Subject: Re: Tomcat error with compiling JSPs > > > > > > > the classpath of the server only points to the bin folder of the JDK. > > > > > > It still doesn't explain why this application isnt working and all of > the > > > rest are, since all our applications are installed via a WAR file and I > do > > > not change or set a class path for each application - I only change the > > > paths that need to be changed in web.xml and struts-config.xml for the > > > application. We have been developing this application on Tomcat on > another > > > server and it works fine. > > > > > > What reasons are there for the java compiler to not be able to compile > JSP > > > files for a particular application as this appears to be the problem. > > > > > > > > > - Original Message - > > > From: "Max Cooper" <[EMAIL PROTECTED]> > > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > > Sent: Thursday, January 15, 2004 1:31 PM > > > Subject: Re: Tomcat error with compiling JSPs > > > > > > > > > > This seems telling: > > > > > > > > [javac] javac: invalid flag: C:\Program > > > > > > > > It seems like some kind of path with a space in it is being passed to > > the > > > > compiler, but it is not being quoted properly. > > > > > > > > javac -classpath C:\Program Files\somelib\lib.jar ... > > > > > > > > (should be: javac -classpath "C:\Program Files\somelib\lib.jar" ...) > > > > > > > > However, I would kind of expect the error to be "invalid flag: > > > > Files\somelib\lib.jar" in that case, since the C:\Program part is > before > > > the > > > > space. Could you have some kind of funky classpath like > "C:\dir\lib.jar; > > > > C:\Program Files\poop\stuff.jar" (note the space after the ';'). Are > you > > > > setting the classpath for the server process yourself, perhaps by > > starting > > > > Tomcat using your own script (rather than startup.bat)? Or do you have > > > some > > > > strange classpath in your environment before you start Tomcat? > > > > > > > > -Max > > > > > > > > - Original Message - > > > > From: "Claire Wall" <[EMAIL PROTECTED]> > > > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > > > Sent: Thursday, January 15, 2004 4:06 AM > > > > Subject: Tomcat error with compiling JSPs > > > > > > > > > > > > hi, > > > > > > > > I am trying to install my application on another server (Tomcat 4.1). > I > > > have > > > > built a WAR file from an ANT build file but when I install it on > Tomcat > > > and > > > > try to access it I get the following error: > > > > > > > > > > > > HTTP Status 500 - > > > > > > > > > > > -- > > > -- > > >
Re: Tomcat error with compiling JSPs
we are using 4.1.24 and are pretty certain that what you say is exactly what
is happening. The path that the app was installed in was quite long + then
there's the package names on top of that and they are pretty lengthy too -
up to 7 folders in depth.
Thanks for your help!
I'm going to try it out at home where I have 4.1.29 installed and see if
this solves the problem, but I'm fairly sure that you're spot on.
:)
- Original Message -
From: "Kevin A. Palfreyman" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, January 15, 2004 1:46 PM
Subject: RE: Tomcat error with compiling JSPs
This is a known problem in some versions of Tomcat, due to a known
problem in some versions of ANT, due to a known problem with
command-line length on windows.
It relates to the path length that is used by ANT when compiling your
JSP.
If the path is longer than the max, then the initial '"' is there but
the final one is chopped. So if you have spaces in the path it will fail
as you say. We hit this bug too.
My guess is you are using 4.1.24? (maybe 21/27 too, but it broke in 24
for me). Try 4.1.29 - that seems better (embeds a newer version of
ANT), although I think theoretically its not entirely fixed. (I think
they put quotes around each element, but that could still mean the path
is chopped. Not sure on this though.)
Your other apps worked because the their paths (e.g. package names) are
shorter, or they depend on fewer 3rd party JARs.
Hope this helps.
Kev
> -Original Message-
> From: Claire Wall [mailto:[EMAIL PROTECTED]
> Sent: 15 January 2004 12:53
> To: Struts Users Mailing List
> Subject: Re: Tomcat error with compiling JSPs
>
> i see what you're saying, but I've got about 6 applications
> running on Tomcat on this server and they all work fine with
> no problems. This is the first time that this has occured so
> I'd really like to understand what could be causing this to
> happen. I'm assuming that it can't be anything coded into my
> servlets/classes as these are already complied and shouldn't
> be compiled by Tomcat when it's run, should they? I am using
> the getRealPath() method in my servlets but this is also true
> of my other applications. i cannot change the path of Tomcat
> because this application may well need to be installed on a
> server where we can't dictate the install path of Tomcat so
> this is not a solution.
>
>
>
> - Original Message -
> From: "McCormack, Chris" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, January 15, 2004 12:11 PM
> Subject: RE: Tomcat error with compiling JSPs
>
>
> >[javac] javac: invalid flag: C:\Program
> >[javac] Usage: javac
> --
>
> Try putting your tomcat install to c:\tomcat
>
> -Original Message-
> From: Claire Wall [mailto:
> Sent: 15 January 2004 12:07
> To: Struts Users Mailing List
> Subject: Tomcat error with compiling JSPs
>
>
> hi,
>
> I am trying to install my application on another server
> (Tomcat 4.1). I have built a WAR file from an ANT build file
> but when I install it on Tomcat and try to access it I get
> the following error:
>
>
> HTTP Status 500 -
>
> --
> --
>
>
> type Exception report
>
> message
>
> description The server encountered an internal error () that
> prevented it from fulfilling this request.
>
> exception
>
> org.apache.jasper.JasperException: Unable to compile class for JSP
>
> An error occurred at line: -1 in the jsp file: null
>
> Generated servlet error:
> [javac] Since fork is true, ignoring compiler setting.
> [javac] Compiling 1 source file
> [javac] Since fork is true, ignoring compiler setting.
> [javac] javac: invalid flag: C:\Program
> [javac] Usage: javac
> [javac] where possible options include:
> [javac] -gGenerate all debugging info
> [javac] -g:none Generate no debugging info
> [javac] -g:{lines,vars,source}Generate only some
> debugging info
> [javac] -nowarn Generate no warnings
> [javac] -verbose Output messages about what the
> compiler is doing
> [javac] -deprecation Output source locations where
> deprecated APIs are used
> [javac] -classpath Specify where to find user
> class files
> [javac] -sourcepath Specify where to find input
> source files
> [javac] -bootclasspath Override location of
> bootstrap class files
> [javac] -extdirs
Re: Tomcat error with compiling JSPs
sorry, i lied before - the JAVA_HOME variable is pointing to the bin folder of the JDK. we have just reinstalled Tomcat (4.1.2) again to a path that has no spaces and it now works. However, this doesnt solve the problem because as stated before, we cannot dictate what path our client has their tomcat installed in. - Original Message - From: "Martin Gainty" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, January 15, 2004 1:43 PM Subject: Re: Tomcat error with compiling JSPs > I ran into this exact error when I installed IBM JDK with Websphere and all > of a sudden my JSP > wouldnt compile on Tomcat > What is your JAVA_HOME pointing to? > Regards, > -Martin > - Original Message - > From: "Claire Wall" <[EMAIL PROTECTED]> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > Sent: Thursday, January 15, 2004 8:44 AM > Subject: Re: Tomcat error with compiling JSPs > > > > the classpath of the server only points to the bin folder of the JDK. > > > > It still doesn't explain why this application isnt working and all of the > > rest are, since all our applications are installed via a WAR file and I do > > not change or set a class path for each application - I only change the > > paths that need to be changed in web.xml and struts-config.xml for the > > application. We have been developing this application on Tomcat on another > > server and it works fine. > > > > What reasons are there for the java compiler to not be able to compile JSP > > files for a particular application as this appears to be the problem. > > > > > > - Original Message - > > From: "Max Cooper" <[EMAIL PROTECTED]> > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > Sent: Thursday, January 15, 2004 1:31 PM > > Subject: Re: Tomcat error with compiling JSPs > > > > > > > This seems telling: > > > > > > [javac] javac: invalid flag: C:\Program > > > > > > It seems like some kind of path with a space in it is being passed to > the > > > compiler, but it is not being quoted properly. > > > > > > javac -classpath C:\Program Files\somelib\lib.jar ... > > > > > > (should be: javac -classpath "C:\Program Files\somelib\lib.jar" ...) > > > > > > However, I would kind of expect the error to be "invalid flag: > > > Files\somelib\lib.jar" in that case, since the C:\Program part is before > > the > > > space. Could you have some kind of funky classpath like "C:\dir\lib.jar; > > > C:\Program Files\poop\stuff.jar" (note the space after the ';'). Are you > > > setting the classpath for the server process yourself, perhaps by > starting > > > Tomcat using your own script (rather than startup.bat)? Or do you have > > some > > > strange classpath in your environment before you start Tomcat? > > > > > > -Max > > > > > > - Original Message - > > > From: "Claire Wall" <[EMAIL PROTECTED]> > > > To: "Struts Users Mailing List" <[EMAIL PROTECTED]> > > > Sent: Thursday, January 15, 2004 4:06 AM > > > Subject: Tomcat error with compiling JSPs > > > > > > > > > hi, > > > > > > I am trying to install my application on another server (Tomcat 4.1). I > > have > > > built a WAR file from an ANT build file but when I install it on Tomcat > > and > > > try to access it I get the following error: > > > > > > > > > HTTP Status 500 - > > > > > > > -- > > -- > > > > > > > > > type Exception report > > > > > > message > > > > > > description The server encountered an internal error () that prevented > it > > > from fulfilling this request. > > > > > > exception > > > > > > org.apache.jasper.JasperException: Unable to compile class for JSP > > > > > > An error occurred at line: -1 in the jsp file: null > > > > > > Generated servlet error: > > > [javac] Since fork is true, ignoring compiler setting. > > > [javac] Compiling 1 source file > > > [javac] Since fork is true, ignoring compiler setting. > > > [javac] javac: invalid flag: C:\Program > > > [javac] Usage: javac > > > [javac] where possible
Re: Tomcat error with compiling JSPs
I ran into this exact error when I installed IBM JDK with Websphere and all
of a sudden my JSP
wouldnt compile on Tomcat
What is your JAVA_HOME pointing to?
Regards,
-Martin
- Original Message -
From: "Claire Wall" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, January 15, 2004 8:44 AM
Subject: Re: Tomcat error with compiling JSPs
> the classpath of the server only points to the bin folder of the JDK.
>
> It still doesn't explain why this application isnt working and all of the
> rest are, since all our applications are installed via a WAR file and I do
> not change or set a class path for each application - I only change the
> paths that need to be changed in web.xml and struts-config.xml for the
> application. We have been developing this application on Tomcat on another
> server and it works fine.
>
> What reasons are there for the java compiler to not be able to compile JSP
> files for a particular application as this appears to be the problem.
>
>
> - Original Message -
> From: "Max Cooper" <[EMAIL PROTECTED]>
> To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> Sent: Thursday, January 15, 2004 1:31 PM
> Subject: Re: Tomcat error with compiling JSPs
>
>
> > This seems telling:
> >
> > [javac] javac: invalid flag: C:\Program
> >
> > It seems like some kind of path with a space in it is being passed to
the
> > compiler, but it is not being quoted properly.
> >
> > javac -classpath C:\Program Files\somelib\lib.jar ...
> >
> > (should be: javac -classpath "C:\Program Files\somelib\lib.jar" ...)
> >
> > However, I would kind of expect the error to be "invalid flag:
> > Files\somelib\lib.jar" in that case, since the C:\Program part is before
> the
> > space. Could you have some kind of funky classpath like "C:\dir\lib.jar;
> > C:\Program Files\poop\stuff.jar" (note the space after the ';'). Are you
> > setting the classpath for the server process yourself, perhaps by
starting
> > Tomcat using your own script (rather than startup.bat)? Or do you have
> some
> > strange classpath in your environment before you start Tomcat?
> >
> > -Max
> >
> > - Original Message -
> > From: "Claire Wall" <[EMAIL PROTECTED]>
> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> > Sent: Thursday, January 15, 2004 4:06 AM
> > Subject: Tomcat error with compiling JSPs
> >
> >
> > hi,
> >
> > I am trying to install my application on another server (Tomcat 4.1). I
> have
> > built a WAR file from an ANT build file but when I install it on Tomcat
> and
> > try to access it I get the following error:
> >
> >
> > HTTP Status 500 -
> >
>
> --
> --
> >
> >
> > type Exception report
> >
> > message
> >
> > description The server encountered an internal error () that prevented
it
> > from fulfilling this request.
> >
> > exception
> >
> > org.apache.jasper.JasperException: Unable to compile class for JSP
> >
> > An error occurred at line: -1 in the jsp file: null
> >
> > Generated servlet error:
> > [javac] Since fork is true, ignoring compiler setting.
> > [javac] Compiling 1 source file
> > [javac] Since fork is true, ignoring compiler setting.
> > [javac] javac: invalid flag: C:\Program
> > [javac] Usage: javac
> > [javac] where possible options include:
> > [javac] -gGenerate all debugging info
> > [javac] -g:none Generate no debugging info
> > [javac] -g:{lines,vars,source}Generate only some debugging
info
> > [javac] -nowarn Generate no warnings
> > [javac] -verbose Output messages about what the
> > compiler is doing
> > [javac] -deprecation Output source locations where
> > deprecated APIs are used
> > [javac] -classpath Specify where to find user class files
> > [javac] -sourcepath Specify where to find input source
files
> > [javac] -bootclasspath Override location of bootstrap class
> files
> > [javac] -extdirsOverride location of installed
> extensions
> > [javac] -d Specify where to place generated class
files
> > [javac] -encoding Specify character e
RE: Tomcat error with compiling JSPs
This is a known problem in some versions of Tomcat, due to a known
problem in some versions of ANT, due to a known problem with
command-line length on windows.
It relates to the path length that is used by ANT when compiling your
JSP.
If the path is longer than the max, then the initial '"' is there but
the final one is chopped. So if you have spaces in the path it will fail
as you say. We hit this bug too.
My guess is you are using 4.1.24? (maybe 21/27 too, but it broke in 24
for me). Try 4.1.29 - that seems better (embeds a newer version of
ANT), although I think theoretically its not entirely fixed. (I think
they put quotes around each element, but that could still mean the path
is chopped. Not sure on this though.)
Your other apps worked because the their paths (e.g. package names) are
shorter, or they depend on fewer 3rd party JARs.
Hope this helps.
Kev
> -Original Message-
> From: Claire Wall [mailto:[EMAIL PROTECTED]
> Sent: 15 January 2004 12:53
> To: Struts Users Mailing List
> Subject: Re: Tomcat error with compiling JSPs
>
> i see what you're saying, but I've got about 6 applications
> running on Tomcat on this server and they all work fine with
> no problems. This is the first time that this has occured so
> I'd really like to understand what could be causing this to
> happen. I'm assuming that it can't be anything coded into my
> servlets/classes as these are already complied and shouldn't
> be compiled by Tomcat when it's run, should they? I am using
> the getRealPath() method in my servlets but this is also true
> of my other applications. i cannot change the path of Tomcat
> because this application may well need to be installed on a
> server where we can't dictate the install path of Tomcat so
> this is not a solution.
>
>
>
> - Original Message -
> From: "McCormack, Chris" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, January 15, 2004 12:11 PM
> Subject: RE: Tomcat error with compiling JSPs
>
>
> >[javac] javac: invalid flag: C:\Program
> >[javac] Usage: javac
> --
>
> Try putting your tomcat install to c:\tomcat
>
> -Original Message-
> From: Claire Wall [mailto:
> Sent: 15 January 2004 12:07
> To: Struts Users Mailing List
> Subject: Tomcat error with compiling JSPs
>
>
> hi,
>
> I am trying to install my application on another server
> (Tomcat 4.1). I have built a WAR file from an ANT build file
> but when I install it on Tomcat and try to access it I get
> the following error:
>
>
> HTTP Status 500 -
>
> --
> --
>
>
> type Exception report
>
> message
>
> description The server encountered an internal error () that
> prevented it from fulfilling this request.
>
> exception
>
> org.apache.jasper.JasperException: Unable to compile class for JSP
>
> An error occurred at line: -1 in the jsp file: null
>
> Generated servlet error:
> [javac] Since fork is true, ignoring compiler setting.
> [javac] Compiling 1 source file
> [javac] Since fork is true, ignoring compiler setting.
> [javac] javac: invalid flag: C:\Program
> [javac] Usage: javac
> [javac] where possible options include:
> [javac] -gGenerate all debugging info
> [javac] -g:none Generate no debugging info
> [javac] -g:{lines,vars,source}Generate only some
> debugging info
> [javac] -nowarn Generate no warnings
> [javac] -verbose Output messages about what the
> compiler is doing
> [javac] -deprecation Output source locations where
> deprecated APIs are used
> [javac] -classpath Specify where to find user
> class files
> [javac] -sourcepath Specify where to find input
> source files
> [javac] -bootclasspath Override location of
> bootstrap class files
> [javac] -extdirsOverride location of
> installed extensions
> [javac] -d Specify where to place generated
> class files
> [javac] -encoding Specify character encoding used
> by source
> files
> [javac] -source Provide source compatibility
> with specified
> release
> [javac] -target Generate class files for
> specific VM version
> [javac] -help Print a synopsis of
> standard options
>
>
>
>
> at
> org.apache.jasper.compiler.DefaultErrorHandler.javacError(Defa
> ultErrorHandle
>
Re: Tomcat error with compiling JSPs
the classpath of the server only points to the bin folder of the JDK.
It still doesn't explain why this application isnt working and all of the
rest are, since all our applications are installed via a WAR file and I do
not change or set a class path for each application - I only change the
paths that need to be changed in web.xml and struts-config.xml for the
application. We have been developing this application on Tomcat on another
server and it works fine.
What reasons are there for the java compiler to not be able to compile JSP
files for a particular application as this appears to be the problem.
- Original Message -
From: "Max Cooper" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, January 15, 2004 1:31 PM
Subject: Re: Tomcat error with compiling JSPs
> This seems telling:
>
> [javac] javac: invalid flag: C:\Program
>
> It seems like some kind of path with a space in it is being passed to the
> compiler, but it is not being quoted properly.
>
> javac -classpath C:\Program Files\somelib\lib.jar ...
>
> (should be: javac -classpath "C:\Program Files\somelib\lib.jar" ...)
>
> However, I would kind of expect the error to be "invalid flag:
> Files\somelib\lib.jar" in that case, since the C:\Program part is before
the
> space. Could you have some kind of funky classpath like "C:\dir\lib.jar;
> C:\Program Files\poop\stuff.jar" (note the space after the ';'). Are you
> setting the classpath for the server process yourself, perhaps by starting
> Tomcat using your own script (rather than startup.bat)? Or do you have
some
> strange classpath in your environment before you start Tomcat?
>
> -Max
>
> - Original Message -
> From: "Claire Wall" <[EMAIL PROTECTED]>
> To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> Sent: Thursday, January 15, 2004 4:06 AM
> Subject: Tomcat error with compiling JSPs
>
>
> hi,
>
> I am trying to install my application on another server (Tomcat 4.1). I
have
> built a WAR file from an ANT build file but when I install it on Tomcat
and
> try to access it I get the following error:
>
>
> HTTP Status 500 -
>
> --
--
>
>
> type Exception report
>
> message
>
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
>
> exception
>
> org.apache.jasper.JasperException: Unable to compile class for JSP
>
> An error occurred at line: -1 in the jsp file: null
>
> Generated servlet error:
> [javac] Since fork is true, ignoring compiler setting.
> [javac] Compiling 1 source file
> [javac] Since fork is true, ignoring compiler setting.
> [javac] javac: invalid flag: C:\Program
> [javac] Usage: javac
> [javac] where possible options include:
> [javac] -gGenerate all debugging info
> [javac] -g:none Generate no debugging info
> [javac] -g:{lines,vars,source}Generate only some debugging info
> [javac] -nowarn Generate no warnings
> [javac] -verbose Output messages about what the
> compiler is doing
> [javac] -deprecation Output source locations where
> deprecated APIs are used
> [javac] -classpath Specify where to find user class files
> [javac] -sourcepath Specify where to find input source files
> [javac] -bootclasspath Override location of bootstrap class
files
> [javac] -extdirsOverride location of installed
extensions
> [javac] -d Specify where to place generated class files
> [javac] -encoding Specify character encoding used by source
> files
> [javac] -source Provide source compatibility with specified
> release
> [javac] -target Generate class files for specific VM
version
> [javac] -help Print a synopsis of standard
options
>
>
>
>
> at
>
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
> r.java:130)
> at
>
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
> 93)
> at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
> at
>
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:4
> 73)
> at
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:1
> 90)
> at
org.apache.jasper.servle
Re: Tomcat error with compiling JSPs
This seems telling:
[javac] javac: invalid flag: C:\Program
It seems like some kind of path with a space in it is being passed to the
compiler, but it is not being quoted properly.
javac -classpath C:\Program Files\somelib\lib.jar ...
(should be: javac -classpath "C:\Program Files\somelib\lib.jar" ...)
However, I would kind of expect the error to be "invalid flag:
Files\somelib\lib.jar" in that case, since the C:\Program part is before the
space. Could you have some kind of funky classpath like "C:\dir\lib.jar;
C:\Program Files\poop\stuff.jar" (note the space after the ';'). Are you
setting the classpath for the server process yourself, perhaps by starting
Tomcat using your own script (rather than startup.bat)? Or do you have some
strange classpath in your environment before you start Tomcat?
-Max
- Original Message -
From: "Claire Wall" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, January 15, 2004 4:06 AM
Subject: Tomcat error with compiling JSPs
hi,
I am trying to install my application on another server (Tomcat 4.1). I have
built a WAR file from an ANT build file but when I install it on Tomcat and
try to access it I get the following error:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it
from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Since fork is true, ignoring compiler setting.
[javac] Compiling 1 source file
[javac] Since fork is true, ignoring compiler setting.
[javac] javac: invalid flag: C:\Program
[javac] Usage: javac
[javac] where possible options include:
[javac] -gGenerate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source}Generate only some debugging info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the
compiler is doing
[javac] -deprecation Output source locations where
deprecated APIs are used
[javac] -classpath Specify where to find user class files
[javac] -sourcepath Specify where to find input source files
[javac] -bootclasspath Override location of bootstrap class files
[javac] -extdirsOverride location of installed extensions
[javac] -d Specify where to place generated class files
[javac] -encoding Specify character encoding used by source
files
[javac] -source Provide source compatibility with specified
release
[javac] -target Generate class files for specific VM version
[javac] -help Print a synopsis of standard options
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
r.java:130)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
93)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:4
73)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:1
90)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipel
Re: Tomcat error with compiling JSPs
i see what you're saying, but I've got about 6 applications running on
Tomcat on this server and they all work fine with no problems. This is the
first time that this has occured so I'd really like to understand what could
be causing this to happen. I'm assuming that it can't be anything coded into
my servlets/classes as these are already complied and shouldn't be compiled
by Tomcat when it's run, should they? I am using the getRealPath() method in
my servlets but this is also true of my other applications. i cannot change
the path of Tomcat because this application may well need to be installed on
a server where we can't dictate the install path of Tomcat so this is not a
solution.
- Original Message -
From: "McCormack, Chris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 15, 2004 12:11 PM
Subject: RE: Tomcat error with compiling JSPs
>[javac] javac: invalid flag: C:\Program
>[javac] Usage: javac
--
Try putting your tomcat install to c:\tomcat
-Original Message-
From: Claire Wall [mailto:
Sent: 15 January 2004 12:07
To: Struts Users Mailing List
Subject: Tomcat error with compiling JSPs
hi,
I am trying to install my application on another server (Tomcat 4.1). I have
built a WAR file from an ANT build file but when I install it on Tomcat and
try to access it I get the following error:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it
from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Since fork is true, ignoring compiler setting.
[javac] Compiling 1 source file
[javac] Since fork is true, ignoring compiler setting.
[javac] javac: invalid flag: C:\Program
[javac] Usage: javac
[javac] where possible options include:
[javac] -gGenerate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source}Generate only some debugging info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the
compiler is doing
[javac] -deprecation Output source locations where
deprecated APIs are used
[javac] -classpath Specify where to find user class files
[javac] -sourcepath Specify where to find input source files
[javac] -bootclasspath Override location of bootstrap class files
[javac] -extdirsOverride location of installed extensions
[javac] -d Specify where to place generated class files
[javac] -encoding Specify character encoding used by source
files
[javac] -source Provide source compatibility with specified
release
[javac] -target Generate class files for specific VM version
[javac] -help Print a synopsis of standard options
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandle
r.java:130)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
93)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:4
73)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:1
90)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at
org.apache.catalina.core.StandardHostValve.invoke(Standa
Tomcat error with compiling JSPs
hi,
I am trying to install my application on another server (Tomcat 4.1). I have built a
WAR file from an ANT build file but when I install it on Tomcat and try to access it I
get the following error:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from
fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Since fork is true, ignoring compiler setting.
[javac] Compiling 1 source file
[javac] Since fork is true, ignoring compiler setting.
[javac] javac: invalid flag: C:\Program
[javac] Usage: javac
[javac] where possible options include:
[javac] -gGenerate all debugging info
[javac] -g:none Generate no debugging info
[javac] -g:{lines,vars,source}Generate only some debugging info
[javac] -nowarn Generate no warnings
[javac] -verbose Output messages about what the compiler is
doing
[javac] -deprecation Output source locations where deprecated APIs
are used
[javac] -classpath Specify where to find user class files
[javac] -sourcepath Specify where to find input source files
[javac] -bootclasspath Override location of bootstrap class files
[javac] -extdirsOverride location of installed extensions
[javac] -d Specify where to place generated class files
[javac] -encoding Specify character encoding used by source files
[javac] -source Provide source compatibility with specified release
[javac] -target Generate class files for specific VM version
[javac] -help Print a synopsis of standard options
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at
org.apache.coyote.http11.
Re: Tomcat error log: Element "struts-config" does not allow "message-resource" here
Chuck Cavaness wrote: > It's . I think that yoy're missing the "s" > according to the error message. > > Chuck > > > At 12:16 PM 4/11/2002 +, you wrote: > >> Hi, >> >> Tomcat3.2.3+JBoss2.4.1 on JDK1.3.1_01 on SuSE7.2 (2.4.13) >> Struts1.0.2 >> >> >> I am getting the following error message on startup of my >> containers(only happens with 'tiles-doc.war' in tc/webapps): >> >> .. startup of JBoss . >> [Default] Starting tomcat. Check logs/tomcat.log for error messages >> [sax] startDocument() >> [sax] endDocument() >> [sax] startDocument() >> [Digester] Parse Error at line 219 column -1: Element "struts-config" >> does not allow "message-resource" here. >> org.xml.sax.SAXParseException: Element "struts-config" does not allow >> "message-resource" here. >>at org.apache.crimson.parser.Parser2.error(Parser2.java:3013) >>at >> >org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(ValidatingParser.java:349) > >> >>at >> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1303) >>at org.apache.crimson.parser.Parser2.content(Parser2.java:1700) >>at >> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468) >>at >> org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499) >>at org.apache.crimson.parser.Parser2.parse(Parser2.java:304) >>at >> org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433) >>at org.apache.commons.digester.Digester.parse(Digester.java:1299) >>at >> >org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:741) >> >>at >> org.apache.struts.action.ActionServlet.init(ActionServlet.java:408) >>at >> org.apache.struts.tiles.ActionComponentServlet.init(ActionComponentServlet.java:52) >> >>at javax.servlet.GenericServlet.init(GenericServlet.java:258) >>at >> org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) >>at org.apache.tomcat.core.Handler.init(Handler.java:215) >>at >> org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) >>at >> >org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnStartupInterceptor.java:130) > >> >>at >> org.apache.tomcat.core.ContextManager.initContext(ContextManager.java:491) >> >>at >> org.apache.tomcat.core.ContextManager.init(ContextManager.java:453) >>at org.jboss.tomcat.TomcatEntry.execute(TomcatEntry.java:337) >>at org.jboss.tomcat.TomcatEntry.(TomcatEntry.java:76) >>at >> >org.jboss.tomcat.EmbeddedTomcatServiceSX.startService(EmbeddedTomcatServiceSX.java:91) > >> >>at >> org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:107) >>at java.lang.reflect.Method.invoke(Native Method) >>at >> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) >>at >> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) >>at >> >org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:836) > >> >>at $Proxy0.start(Unknown Source) >>at org.jboss.util.ServiceControl.start(ServiceControl.java:81) >>at java.lang.reflect.Method.invoke(Native Method) >>at >> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) >>at >> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) >>at org.jboss.Main.(Main.java:210) >>at org.jboss.Main$1.run(Main.java:116) >>at java.security.AccessController.doPrivileged(Native Method) >>at org.jboss.Main.main(Main.java:112) >> [Digester] Parse Error at line 219 column -1: Element type >> "message-resource" is not declared. >> org.xml.sax.SAXParseException: Element type "message-resource" is not >> declared. >>at org.apache.crimson.parser.Parser2.error(Parser2.java:3013) >>at >> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1308) >>at org.apache.crimson.parser.Parser2.content(Parser2.java:1700) >>at >> org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468) >>at >> org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499) >>at org.apache.crimson.parser.Parser2.parse(Parser2.java:304) >>at >> org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433) >>at org.apache.commons.digester.Digester.parse(Digester.java:1299) >>at >> >org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:741) >> >>at >> org.apache.struts.action.ActionServlet.init(ActionServlet.java:408) >>at >> org.apache.struts.tiles.ActionComponentServlet.init(ActionComponentServlet.java:52) >> >>at javax.servlet.GenericServlet.init(GenericServlet.java:258) >>at >> org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) >>at or
Re: Tomcat error log: Element "struts-config" does not allow "message-resource" here
It's . I think that yoy're missing the "s" according to the error message. Chuck At 12:16 PM 4/11/2002 +, you wrote: >Hi, > >Tomcat3.2.3+JBoss2.4.1 on JDK1.3.1_01 on SuSE7.2 (2.4.13) >Struts1.0.2 > > >I am getting the following error message on startup of my containers(only >happens with 'tiles-doc.war' in tc/webapps): > >.. startup of JBoss . >[Default] Starting tomcat. Check logs/tomcat.log for error messages >[sax] startDocument() >[sax] endDocument() >[sax] startDocument() >[Digester] Parse Error at line 219 column -1: Element "struts-config" does >not allow "message-resource" here. >org.xml.sax.SAXParseException: Element "struts-config" does not allow >"message-resource" here. >at org.apache.crimson.parser.Parser2.error(Parser2.java:3013) >at > >org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(ValidatingParser.java:349) >at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1303) >at org.apache.crimson.parser.Parser2.content(Parser2.java:1700) >at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468) >at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499) >at org.apache.crimson.parser.Parser2.parse(Parser2.java:304) >at > org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433) >at org.apache.commons.digester.Digester.parse(Digester.java:1299) >at > org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:741) >at org.apache.struts.action.ActionServlet.init(ActionServlet.java:408) >at > org.apache.struts.tiles.ActionComponentServlet.init(ActionComponentServlet.java:52) >at javax.servlet.GenericServlet.init(GenericServlet.java:258) >at > org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) >at org.apache.tomcat.core.Handler.init(Handler.java:215) >at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) >at > >org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnStartupInterceptor.java:130) >at > org.apache.tomcat.core.ContextManager.initContext(ContextManager.java:491) >at org.apache.tomcat.core.ContextManager.init(ContextManager.java:453) >at org.jboss.tomcat.TomcatEntry.execute(TomcatEntry.java:337) >at org.jboss.tomcat.TomcatEntry.(TomcatEntry.java:76) >at > >org.jboss.tomcat.EmbeddedTomcatServiceSX.startService(EmbeddedTomcatServiceSX.java:91) >at > org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:107) >at java.lang.reflect.Method.invoke(Native Method) >at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) >at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) >at > >org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:836) >at $Proxy0.start(Unknown Source) >at org.jboss.util.ServiceControl.start(ServiceControl.java:81) >at java.lang.reflect.Method.invoke(Native Method) >at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) >at > com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) >at org.jboss.Main.(Main.java:210) >at org.jboss.Main$1.run(Main.java:116) >at java.security.AccessController.doPrivileged(Native Method) >at org.jboss.Main.main(Main.java:112) >[Digester] Parse Error at line 219 column -1: Element type >"message-resource" is not declared. >org.xml.sax.SAXParseException: Element type "message-resource" is not >declared. >at org.apache.crimson.parser.Parser2.error(Parser2.java:3013) >at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1308) >at org.apache.crimson.parser.Parser2.content(Parser2.java:1700) >at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468) >at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499) >at org.apache.crimson.parser.Parser2.parse(Parser2.java:304) >at > org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433) >at org.apache.commons.digester.Digester.parse(Digester.java:1299) >at > org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:741) >at org.apache.struts.action.ActionServlet.init(ActionServlet.java:408) >at > org.apache.struts.tiles.ActionComponentServlet.init(ActionComponentServlet.java:52) >at javax.servlet.GenericServlet.init(GenericServlet.java:258) >at > org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) >at org.apache.tomcat.core.Handler.init(Handler.java:215) >at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) >at > >org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnStartupInterce
Tomcat error log: Element "struts-config" does not allow "message-resource" here
Hi, Tomcat3.2.3+JBoss2.4.1 on JDK1.3.1_01 on SuSE7.2 (2.4.13) Struts1.0.2 I am getting the following error message on startup of my containers(only happens with 'tiles-doc.war' in tc/webapps): .. startup of JBoss . [Default] Starting tomcat. Check logs/tomcat.log for error messages [sax] startDocument() [sax] endDocument() [sax] startDocument() [Digester] Parse Error at line 219 column -1: Element "struts-config" does not allow "message-resource" here. org.xml.sax.SAXParseException: Element "struts-config" does not allow "message-resource" here. at org.apache.crimson.parser.Parser2.error(Parser2.java:3013) at org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(ValidatingParser.java:349) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1303) at org.apache.crimson.parser.Parser2.content(Parser2.java:1700) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499) at org.apache.crimson.parser.Parser2.parse(Parser2.java:304) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433) at org.apache.commons.digester.Digester.parse(Digester.java:1299) at org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:741) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:408) at org.apache.struts.tiles.ActionComponentServlet.init(ActionComponentServlet.java:52) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) at org.apache.tomcat.core.Handler.init(Handler.java:215) at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) at org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnStartupInterceptor.java:130) at org.apache.tomcat.core.ContextManager.initContext(ContextManager.java:491) at org.apache.tomcat.core.ContextManager.init(ContextManager.java:453) at org.jboss.tomcat.TomcatEntry.execute(TomcatEntry.java:337) at org.jboss.tomcat.TomcatEntry.(TomcatEntry.java:76) at org.jboss.tomcat.EmbeddedTomcatServiceSX.startService(EmbeddedTomcatServiceSX.java:91) at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:107) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:836) at $Proxy0.start(Unknown Source) at org.jboss.util.ServiceControl.start(ServiceControl.java:81) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.Main.(Main.java:210) at org.jboss.Main$1.run(Main.java:116) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.Main.main(Main.java:112) [Digester] Parse Error at line 219 column -1: Element type "message-resource" is not declared. org.xml.sax.SAXParseException: Element type "message-resource" is not declared. at org.apache.crimson.parser.Parser2.error(Parser2.java:3013) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1308) at org.apache.crimson.parser.Parser2.content(Parser2.java:1700) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1468) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:499) at org.apache.crimson.parser.Parser2.parse(Parser2.java:304) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433) at org.apache.commons.digester.Digester.parse(Digester.java:1299) at org.apache.struts.action.ActionServlet.initApplicationConfig(ActionServlet.java:741) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:408) at org.apache.struts.tiles.ActionComponentServlet.init(ActionComponentServlet.java:52) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) at org.apache.tomcat.core.Handler.init(Handler.java:215) at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) at org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit(LoadOnStartupInterceptor.java:130) at org.apache.tomcat.core.ContextManager.initContext(ContextManager.java:491) at org.apache.tomcat.core.ContextManager.init(ContextManager.java:453) at org.jboss.tomcat.TomcatEntry.execute(TomcatEntry.j
