You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by bladu <eg...@hotmail.com> on 2009/03/31 19:45:07 UTC
Tomcat error: It is not available the ServletAction
Hi,
I am deploying an application using Ant from MyEclipse IDE.
When I deploy the application with the Ant, this say me that the application
has successfully deployed. I go to webaapps directory and I see into that
directory the applicacation deployed with its WAR.
But when I try to excute the application, Tomcat gives me the following
error:
Message: It is not available the Servlet Action
Description: The request resource (It doesn`t available the ServletAction)
is not available.
I
f I go to Apache Tomcat`s stdout log I can see two warnings:
WARN: No appends could be found for logger
(org.apache.commons.beanutils.Convertutils)
WARN: Please initialize the log4j system properly
But, If I go to the Java Build path of the application I can verify how I
have added the commons.beanutils.jar and log4j.jar .
I don`t know why it doesn´t run and I am stuck.
I would be very grateful somebody could help me tom solve this problem.
Regards
--
View this message in context: http://www.nabble.com/Tomcat-error%3A-It-is-not-available-the-ServletAction-tp22805251p22805251.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by bladu <eg...@hotmail.com>.
Christopher Schultz-2 wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Bladu,
>
> On 4/1/2009 4:00 AM, bladu wrote:
>> The Tomcat I have is in Spanish language. The log has lines written in
>> Spanish / English. Maybe you will have some problems to understand the
>> lines
>> written in Spanish, for that reason I put in the line below the
>> corresponding translation to English, (the translation that approachs
>> more
>> to English, Spanish is my mother tongue).
>
> Okay. You're right, Spanish would be a challenge, but there are some
> things that need no translation, like a stack trace (see below).
>
>> The log I provide you is the stdout.log (I don`t have the catalina.log
>> file,
>> or at least I am not able to find it).
>
> catalina.out is the standard stdout log, so if you have a stdout log,
> that should be fine.
>
>> 2009-03-31 17:51:28 StandardContext[/DSGCWeb]The Servlet /DSGCWeb threw
>> an
>> load() exception
>> javax.servlet.UnavailableException: Parsing error processing resource
>> path
>
>> at
>> org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1035)
>> at
>> org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1010)
>> at
>> org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
>> at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
>
> Struts is having a problem loading ifs configuration, which probably
> marking your application as unavailable.
>
> There's no indication in this log file why Struts is having trouble
> loading. If you have a Struts-specific configuration file, you might
> want to take a look at that. Typically, it's a syntax error in the
> struts-config.xml file. Check that file for recent changes to see what
> the problem might be.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAknTWJ0ACgkQ9CaO5/Lv0PAwfgCdGcf3pnfhpcNyfY6kK+JC5pCz
> EDgAn1Msm3hAF1E/JYvLsaIjC+SxuDzu
> =szyv
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Hi again
Thanks for trying to help me.
I have correct some bugs in the struts-config.xml (references to classes
that don`t exist), but the problem still remains. When I deploy the
application and execute it, Tomcat gives me the following error:
Message: It is not available the Servlet Action
Description: The request resource (It doesn`t available the ServletAction)
is not available.
The log stdout of Tomcat gives me the following information(like before, to
make easier your labour, I underline you the lines I consider that are more
important in order to solve the problem) :
2009-04-01 16:53:27 StandardContext[/manager]Manager: deploy: Deploying web
application at '/DSGCWeb'
2009-04-01 16:53:27 StandardContext[/manager]Manager: Uploading WAR file to
C:\Tomcat 5.0.28\webapps\DSGCWeb.war
2009-04-01 16:53:27 StandardContext[/manager]Manager: Extracting XML file to
C:\Tomcat 5.0.28\conf\Catalina\localhost\DSGCWeb.xml
2009-04-01 16:53:27 StandardContext[/manager]Manager: install: Installing
web application at '/DSGCWeb' from 'jar:file:/C:/Tomcat
5.0.28/webapps/DSGCWeb.war!/'
2009-04-01 16:53:30 StandardContext[/DSGCWeb]Marcando el servlet action como
no disponible
2009-04-01 16:53:30 StandardContext[/DSGCWeb] Marking the action servlet as
not available
2009-04-01 16:53:30 StandardContext[/DSGCWeb]El Servlet /DSGCWeb lanzó
excepción de load()
2009-04-01 16:53:30 StandardContext[/DSGCWeb] The Servlet /DSGCWeb threw an
load() exception
javax.servlet.UnavailableException: Parsing error processing resource path
at
org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1035)
at
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1010)
at
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4013)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4357)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
at
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:922)
at
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:652)
at
org.apache.catalina.manager.ManagerServlet.doPut(ManagerServlet.java:400)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:712)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)
Regards
--
View this message in context: http://www.nabble.com/Tomcat-error%3A-It-is-not-available-the-ServletAction-tp22805251p22829372.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bladu,
On 4/1/2009 4:00 AM, bladu wrote:
> The Tomcat I have is in Spanish language. The log has lines written in
> Spanish / English. Maybe you will have some problems to understand the lines
> written in Spanish, for that reason I put in the line below the
> corresponding translation to English, (the translation that approachs more
> to English, Spanish is my mother tongue).
Okay. You're right, Spanish would be a challenge, but there are some
things that need no translation, like a stack trace (see below).
> The log I provide you is the stdout.log (I don`t have the catalina.log file,
> or at least I am not able to find it).
catalina.out is the standard stdout log, so if you have a stdout log,
that should be fine.
> 2009-03-31 17:51:28 StandardContext[/DSGCWeb]The Servlet /DSGCWeb threw an
> load() exception
> javax.servlet.UnavailableException: Parsing error processing resource path
> at
> org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1035)
> at
> org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1010)
> at
> org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
> at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
Struts is having a problem loading ifs configuration, which probably
marking your application as unavailable.
There's no indication in this log file why Struts is having trouble
loading. If you have a Struts-specific configuration file, you might
want to take a look at that. Typically, it's a syntax error in the
struts-config.xml file. Check that file for recent changes to see what
the problem might be.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknTWJ0ACgkQ9CaO5/Lv0PAwfgCdGcf3pnfhpcNyfY6kK+JC5pCz
EDgAn1Msm3hAF1E/JYvLsaIjC+SxuDzu
=szyv
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by bladu <eg...@hotmail.com>.
Christopher Schultz-2 wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Bladu,
>
> On 3/31/2009 1:45 PM, bladu wrote:
>> But when I try to execute the application, Tomcat gives me the following
>> error:
>>
>> Message: It is not available the Servlet Action
>> Description: The request resource (It doesn`t available the
>> ServletAction)
>> is not available.
> <
> I suspect this is not the exact error message. Can you copy-and-paste
> the full error, including any stack trace that may appear in the browser
> window /or/ in your catalina.log file (or is that the stdout log that
> you mentioned)?
>
> The log files are likely to hold the key to this problem. If log4j
> appears to be broken, try running Tomcat with the standard logger just
> to test to see what's wrong.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAknSjQ8ACgkQ9CaO5/Lv0PCnLQCgpasQDZVKMBR2WyP9jXWbdxZu
> lkYAnRNMX1xr74RF7Xj0O7zwe8NHy0gm
> =SGgA
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Hi,
The Tomcat I have is in Spanish language. The log has lines written in
Spanish / English. Maybe you will have some problems to understand the lines
written in Spanish, for that reason I put in the line below the
corresponding translation to English, (the translation that approachs more
to English, Spanish is my mother tongue).
To make easier your labour, I underline you the lines I consider that are
more important in order to solve the problem.
The log I provide you is the stdout.log (I don`t have the catalina.log file,
or at least I am not able to find it).
2009-03-31 17:51:24 StandardContext[/manager]Manager: deploy: Deploying web
application at '/DSGCWeb'
2009-03-31 17:51:24 StandardContext[/manager]Manager: Uploading WAR file to
C:\Tomcat 5.0.28\webapps\DSGCWeb.war
2009-03-31 17:51:24 StandardContext[/manager]Manager: Extracting XML file to
C:\Tomcat 5.0.28\conf\Catalina\localhost\DSGCWeb.xml
2009-03-31 17:51:24 StandardContext[/manager]Manager: install: Installing
web application at '/DSGCWeb' from 'jar:file:/C:/Tomcat
5.0.28/webapps/DSGCWeb.war!/'
2009-03-31 17:51:28 StandardContext[/DSGCWeb]Marcando el servlet action como
no disponible
2009-03-31 17:51:28 StandardContext[/DSGCWeb] Marking the Action servlet as
not available
2009-03-31 17:51:28 StandardContext[/DSGCWeb]El Servlet /DSGCWeb lanzó
excepción de load()
javax.servlet.UnavailableException: Parsing error processing resource path
2009-03-31 17:51:28 StandardContext[/DSGCWeb]The Servlet /DSGCWeb threw an
load() exception
javax.servlet.UnavailableException: Parsing error processing resource path
at
org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1035)
at
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1010)
at
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4013)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4357)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
at
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:922)
at
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:652)
at
org.apache.catalina.manager.ManagerServlet.doPut(ManagerServlet.java:400)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:712)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)
2009-03-31 17:52:31 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:52:31 StandardWrapperValve[action]: The Servlet Action is not
available at this moment
2009-03-31 17:54:37 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:54:37 StandardWrapperValve[action]: The Servlet Action is not
available at this moment
2009-03-31 17:55:17 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:55:17 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 17:55:17 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:55:17 StandardWrapperValve[action]: The Servlet Action is not
available at this moment
2009-03-31 17:55:17 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:55:17 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 17:55:17 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:55:17 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 17:56:42 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:56:42 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 17:56:44 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:56:44 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 17:58:43 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:58:43 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 17:58:47 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:58:47 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 17:59:39 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 17:59:39 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
2009-03-31 18:01:06 StandardWrapperValve[action]: El Servlet action no está
disponible en este momento
2009-03-31 18:01:06 StandardWrapperValve[action]:The Servlet Action is not
available at this moment
Thank you for supporting me in this issue. It`s very important for me to
solve this.
Regards
--
View this message in context: http://www.nabble.com/Tomcat-error%3A-It-is-not-available-the-ServletAction-tp22805251p22821593.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bladu,
On 4/2/2009 2:42 AM, bladu wrote:
> Version of Java --->jdk1.5.0_17
Okay.
> Do you have xerces.jar in your webapp's lib directory? --->Yes, int he
> application deployed and also in the WAR I have xerces-1.2.3.jar
OMG that version is like 10 years old. They've been on Xerces 2.x for a
looong time. The current version is 2.9.1. This is likely to be the
problem. Does your application use XML parsing itself and rely on that
old version of Xerces? You may have a problem, then. If you don't do XML
parsing within your own application's code, consider upgrading to a
recent version of Xerces. I'm sure Struts will be a whole lot happier
with that.
> What version of Tomcat are you using? --->jakarta-tomcat-5.0.28
This version of Tomcat has been abandoned. You should upgrade to 5.5 or
(even better) 6.0 as soon as possible.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknUxL0ACgkQ9CaO5/Lv0PBBlwCfVfx+8Hj8fnwivOliGsT1pJ9J
tPcAoJe/OtlcPS4BNgue829gcri+SI57
=XQjR
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by bladu <eg...@hotmail.com>.
Christopher Schultz-2 wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Chuck,
>
> On 4/1/2009 11:45 AM, Caldarale, Charles R wrote:
>>> From: bladu [mailto:egoibe@hotmail.com]
>>> Subject: Re: Tomcat error: It is not available the ServletAction
>>>
>>> I have correct some bugs in the struts-config.xml (references to
>>> classes that don`t exist), but the problem still remains.
>>
>> The error message generated by struts shows a *parsing* error - meaning
>> you likely have something wrong with the syntax of your struts config
>> rather than the values of any fields. Try running that XML file through
>> a syntax checker to see if you can find it.
>
> Some Struts users have reported the following causes to this problem:
>
> 1. An actual XML parsing error
> 2. Java version mismatch
> 3. xerces.jar version mismatch or overlap
>
> What version of Java are you running?
> Do you have xerces.jar in your webapp's lib directory?
> What version of Tomcat are you using?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAknT0n4ACgkQ9CaO5/Lv0PB0PQCgsB4liiFvjm+FL7APhBAnxYAW
> k+wAn3EQluZ1WdeEDF3bnxr6+++9gEV4
> =k7yc
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Hi,
Version of Java --->jdk1.5.0_17
Do you have xerces.jar in your webapp's lib directory? --->Yes, int he
application deployed and also in the WAR I have xerces-1.2.3.jar
What version of Tomcat are you using? --->jakarta-tomcat-5.0.28
Regards
--
View this message in context: http://www.nabble.com/Tomcat-error%3A-It-is-not-available-the-ServletAction-tp22805251p22841851.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] Tomcat error: It is not available the ServletAction
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chuck,
On 4/2/2009 3:27 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Subject: Re: Tomcat error: It is not available the ServletAction
>>
>> I think the reason Xerces works within the application's
>> ClassLoader is because of the backward way that webapp ClassLoaders
>> work (load local before parent).
>
> If you don't mind pursuing this a bit more, I still have some
> concerns about how this can work reliably. Let's focus on the
> xml-apis.jar for now, which contains numerous classes that are also
> in the 1.5 and newer JREs. It would seem that if a webapp had its
> own copy of xml-apis.jar, it would load some javax.xml.* classes from
> there, while references in Tomcat's lib directory (including any
> shared jars used by multiple webapps) would resolve those classes
> from rt.jar. Constructs like instanceof would fail, since they have
> different classloaders.
>
> Does this just work by luck?
I dunno, but I suspect not ;)
If the application requests any class, presumably it will be loaded from
the xml-api.jar file in the webapp's lib directory. I can imagine that
those classes maintain their own referential integrity, so no classes
end up missing and having to be loaded from the parent ClassLoaders.
Similarly, if Tomcat needs a class, it never goes to the webapp
ClassLoader, so there's no confusion.
The only confusion would occur if you wanted to ask Tomcat to do
something for you and then use XML-related classes. For instance, if
Tomcat provided a service to give you a stream of SAX events, if your
application then tried to use those objects in certain ways, things
would break.
Fortunately, those cases don't crop-up too frequently.
It's possible that the "luck" experienced by webapps like cocoon is by
design: the xml-apis.jar file contains /everything/, including
javax.xml.* so any requests to "the JVM" for an XML parser (for example)
are intercepted by the local libraries and completely fulfilled, whether
those same (or similar) classes are available from the bootstrap
ClassLoader or any other one higher-up in the chain.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknWfaQACgkQ9CaO5/Lv0PBhtQCgpfrIOkbM5jyNFWXKE+sFmqKA
TQ8AoIGOC671EU8GYeQf1ehlFRjFnTGx
=I/Ib
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: [OT] Tomcat error: It is not available the ServletAction
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: Tomcat error: It is not available the ServletAction
>
> I think the reason Xerces works within the application's ClassLoader is
> because of the backward way that webapp ClassLoaders work (load local
> before parent).
If you don't mind pursuing this a bit more, I still have some concerns about how this can work reliably. Let's focus on the xml-apis.jar for now, which contains numerous classes that are also in the 1.5 and newer JREs. It would seem that if a webapp had its own copy of xml-apis.jar, it would load some javax.xml.* classes from there, while references in Tomcat's lib directory (including any shared jars used by multiple webapps) would resolve those classes from rt.jar. Constructs like instanceof would fail, since they have different classloaders.
Does this just work by luck?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Tomcat error: It is not available the ServletAction
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chuck,
On 4/2/2009 10:30 AM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Subject: Re: Tomcat error: It is not available the ServletAction
>>
>> Apache Cocoon, for instance, ships with xercesImpl-2.9.1.jar
>> (actual Xerces) along with xml-apis-1.3.04.jar (the org.w3c.*,
>> org.xml.* and javax.xml.* interfaces, etc.) provided as part
>> of the webapp's libraries.
>
> O.k., good to know. Have the class names changed since the version
> the OP is using was delivered? The various mailing lists are littered with
> stories of class conflict problems due to having multiple XML parser
> jars visible in a given classloader's path, especially on a 1.5 or newer
> JRE.
Xerces 1 implements somewhat older versions of the XML spec(s), while
Xerces 2 implements all the new stuff (which isn't all that different...
it's still XML 1.0). The implementation is completely different, but the
interfaces are largely the same names.
The XML APIs themselves have changed somewhat, and I think /that/ is
where the problems occur. It's not Xerces specific, of course, because
it's the org.w3c.*, org.xml.*, and javax.xml.* interfaces and classes
that have changed. IMO, Sun and the W3C really boned the XML API path.
I think the reason Xerces works within the application's ClassLoader is
because of the backward way that webapp ClassLoaders work (load local
before parent). When Xerces is/is not available to the boot classloader
as well as the main classloader, that's when problems occur (which is
why you need to bundle the parser with Tomcat 5.5 on a 1.4-level JVM).
> Note that the Tomcat 5.5 compatibility package for running with a
> 1.4 JRE consists primarily of the Xerces implementation and XML API
> definition jars, which are built-in to 1.5; leaving the
> compatibility package installed when switching from a 1.4 to a 1.5
> JRE definitely does cause problems.
Since this is at the top-level (i.e. not using a webapp-style
ClassLoader), confusion can occur when versions are not matched (and
they are almost always mismatched).
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknU1cUACgkQ9CaO5/Lv0PBefACfXYT1GHDzwoV1xgek0hXqZLIn
00wAn0bXFF4GysDxj+uo1/NiXqmV6WcG
=tNYW
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat error: It is not available the ServletAction
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: Tomcat error: It is not available the ServletAction
>
> Apache Cocoon, for instance, ships with xercesImpl-2.9.1.jar
> (actual Xerces) along with xml-apis-1.3.04.jar (the org.w3c.*,
> org.xml.* and javax.xml.* interfaces, etc.) provided as part
> of the webapp's libraries.
O.k., good to know. Have the class names changed since the version the OP is using was delivered? The various mailing lists are littered with stories of class conflict problems due to having multiple XML parser jars visible in a given classloader's path, especially on a 1.5 or newer JRE.
Note that the Tomcat 5.5 compatibility package for running with a 1.4 JRE consists primarily of the Xerces implementation and XML API definition jars, which are built-in to 1.5; leaving the compatibility package installed when switching from a 1.4 to a 1.5 JRE definitely does cause problems.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Tomcat error: It is not available the ServletAction
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chuck,
On 4/2/2009 9:08 AM, Caldarale, Charles R wrote:
>> From: bladu [mailto:egoibe@hotmail.com]
>> Subject: Re: Tomcat error: It is not available the ServletAction
>
> When you send the same message four times, you become extremely annoying - don't do that.
Agreed. I saw one of Bladu's "other" messages first and replied to it
instead of the one that was actually part of this thread, so it's
disconnected, now. I suspect a Xerces version mismatch. His version is
ooooooooold.
>> Do you have xerces.jar in your webapp's lib directory? --->Yes, int he
>> application deployed and also in the WAR I have xerces-1.2.3.jar
>
> Remove the xerces*.jar from wherever you have it - those classes are
> part of the 1.5 JRE/JDK. Having them in your webapp causes classloading
> confusion.
I disagree. We have applications that provide their own XML parsers and
everything works fine. Apache Cocoon, for instance, ships with
xercesImpl-2.9.1.jar (actual Xerces) along with xml-apis-1.3.04.jar (the
org.w3c.*, org.xml.* and javax.xml.* interfaces, etc.) provided as part
of the webapp's libraries. These work without conflict on Tomcat 5.5.26.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknUyGMACgkQ9CaO5/Lv0PDQlACgnQBxEedsljyuyUyGv51pt/yu
sQwAoMKYq/Go5An4r9PZHcscn+YJDkxY
=VHUF
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat error: It is not available the ServletAction
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: bladu [mailto:egoibe@hotmail.com]
> Subject: Re: Tomcat error: It is not available the ServletAction
When you send the same message four times, you become extremely annoying - don't do that.
> Do you have xerces.jar in your webapp's lib directory? --->Yes, int he
> application deployed and also in the WAR I have xerces-1.2.3.jar
Remove the xerces*.jar from wherever you have it - those classes are part of the 1.5 JRE/JDK. Having them in your webapp causes classloading confusion.
> What version of Tomcat are you using? --->jakarta-tomcat-5.0.28
Which has not been supported for quite some time. Please use a 5.5 or preferably a 6.0 version.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by bladu <eg...@hotmail.com>.
Christopher Schultz-2 wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Chuck,
>
> On 4/1/2009 11:45 AM, Caldarale, Charles R wrote:
>>> From: bladu [mailto:egoibe@hotmail.com]
>>> Subject: Re: Tomcat error: It is not available the ServletAction
>>>
>>> I have correct some bugs in the struts-config.xml (references to
>>> classes that don`t exist), but the problem still remains.
>>
>> The error message generated by struts shows a *parsing* error - meaning
>> you likely have something wrong with the syntax of your struts config
>> rather than the values of any fields. Try running that XML file through
>> a syntax checker to see if you can find it.
>
> Some Struts users have reported the following causes to this problem:
>
> 1. An actual XML parsing error
> 2. Java version mismatch
> 3. xerces.jar version mismatch or overlap
>
> What version of Java are you running?
> Do you have xerces.jar in your webapp's lib directory?
> What version of Tomcat are you using?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAknT0n4ACgkQ9CaO5/Lv0PB0PQCgsB4liiFvjm+FL7APhBAnxYAW
> k+wAn3EQluZ1WdeEDF3bnxr6+++9gEV4
> =k7yc
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Hi,
Version of Java --->jdk1.5.0_17
Do you have xerces.jar in your webapp's lib directory? --->Yes, int he
application deployed and also in the WAR I have xerces-1.2.3.jar
What version of Tomcat are you using? --->jakarta-tomcat-5.0.28
Regards
--
View this message in context: http://www.nabble.com/Tomcat-error%3A-It-is-not-available-the-ServletAction-tp22805251p22841693.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chuck,
On 4/1/2009 11:45 AM, Caldarale, Charles R wrote:
>> From: bladu [mailto:egoibe@hotmail.com]
>> Subject: Re: Tomcat error: It is not available the ServletAction
>>
>> I have correct some bugs in the struts-config.xml (references to
>> classes that don`t exist), but the problem still remains.
>
> The error message generated by struts shows a *parsing* error - meaning you likely have something wrong with the syntax of your struts config rather than the values of any fields. Try running that XML file through a syntax checker to see if you can find it.
Some Struts users have reported the following causes to this problem:
1. An actual XML parsing error
2. Java version mismatch
3. xerces.jar version mismatch or overlap
What version of Java are you running?
Do you have xerces.jar in your webapp's lib directory?
What version of Tomcat are you using?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknT0n4ACgkQ9CaO5/Lv0PB0PQCgsB4liiFvjm+FL7APhBAnxYAW
k+wAn3EQluZ1WdeEDF3bnxr6+++9gEV4
=k7yc
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat error: It is not available the ServletAction
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: bladu [mailto:egoibe@hotmail.com]
> Subject: Re: Tomcat error: It is not available the ServletAction
>
> I have correct some bugs in the struts-config.xml (references to
> classes that don`t exist), but the problem still remains.
The error message generated by struts shows a *parsing* error - meaning you likely have something wrong with the syntax of your struts config rather than the values of any fields. Try running that XML file through a syntax checker to see if you can find it.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Tomcat error: It is not available the ServletAction
Posted by bladu <eg...@hotmail.com>.
Christopher Schultz-2 wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Bladu,
>
> On 3/31/2009 1:45 PM, bladu wrote:
>> But when I try to execute the application, Tomcat gives me the following
>> error:
>>
>> Message: It is not available the Servlet Action
>> Description: The request resource (It doesn`t available the
>> ServletAction)
>> is not available.
>
> I suspect this is not the exact error message. Can you copy-and-paste
> the full error, including any stack trace that may appear in the browser
> window /or/ in your catalina.log file (or is that the stdout log that
> you mentioned)?
>
> The log files are likely to hold the key to this problem. If log4j
> appears to be broken, try running Tomcat with the standard logger just
> to test to see what's wrong.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAknSjQ8ACgkQ9CaO5/Lv0PCnLQCgpasQDZVKMBR2WyP9jXWbdxZu
> lkYAnRNMX1xr74RF7Xj0O7zwe8NHy0gm
> =SGgA
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Hi again
Thanks for trying to help me.
I have correct some bugs in the struts-config.xml (references to classes
that don`t exist), but the problem still remains. When I deploy the
application and execute it, Tomcat gives me the following error:
Message: It is not available the Servlet Action
Description: The request resource (It doesn`t available the ServletAction)
is not available.
The log stdout of Tomcat gives me the following information(like before, to
make easier your labour, I underline you the lines I consider that are more
important in order to solve the problem) :
2009-04-01 16:53:27 StandardContext[/manager]Manager: deploy: Deploying web
application at '/DSGCWeb'
2009-04-01 16:53:27 StandardContext[/manager]Manager: Uploading WAR file to
C:\Tomcat 5.0.28\webapps\DSGCWeb.war
2009-04-01 16:53:27 StandardContext[/manager]Manager: Extracting XML file to
C:\Tomcat 5.0.28\conf\Catalina\localhost\DSGCWeb.xml
2009-04-01 16:53:27 StandardContext[/manager]Manager: install: Installing
web application at '/DSGCWeb' from 'jar:file:/C:/Tomcat
5.0.28/webapps/DSGCWeb.war!/'
2009-04-01 16:53:30 StandardContext[/DSGCWeb]Marcando el servlet action como
no disponible
2009-04-01 16:53:30 StandardContext[/DSGCWeb] Marking the action servlet as
not available
2009-04-01 16:53:30 StandardContext[/DSGCWeb]El Servlet /DSGCWeb lanzó
excepción de load()
2009-04-01 16:53:30 StandardContext[/DSGCWeb] The Servlet /DSGCWeb threw an
load() exception
javax.servlet.UnavailableException: Parsing error processing resource path
at
org.apache.struts.action.ActionServlet.handleConfigException(ActionServlet.java:1035)
at
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1010)
at
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
at org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
at javax.servlet.GenericServlet.init(GenericServlet.java:211)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4013)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4357)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:832)
at
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:922)
at
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java:652)
at
org.apache.catalina.manager.ManagerServlet.doPut(ManagerServlet.java:400)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:712)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:540)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)
Regards
--
View this message in context: http://www.nabble.com/Tomcat-error%3A-It-is-not-available-the-ServletAction-tp22805251p22829289.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat error: It is not available the ServletAction
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bladu,
On 3/31/2009 1:45 PM, bladu wrote:
> But when I try to execute the application, Tomcat gives me the following
> error:
>
> Message: It is not available the Servlet Action
> Description: The request resource (It doesn`t available the ServletAction)
> is not available.
I suspect this is not the exact error message. Can you copy-and-paste
the full error, including any stack trace that may appear in the browser
window /or/ in your catalina.log file (or is that the stdout log that
you mentioned)?
The log files are likely to hold the key to this problem. If log4j
appears to be broken, try running Tomcat with the standard logger just
to test to see what's wrong.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAknSjQ8ACgkQ9CaO5/Lv0PCnLQCgpasQDZVKMBR2WyP9jXWbdxZu
lkYAnRNMX1xr74RF7Xj0O7zwe8NHy0gm
=SGgA
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org