Discussion:
Deploying a WAR gives javax.servlet.UnavailableException: Parsing error processing resource path
(too old to reply)
Ryan Hoegg
2003-10-22 07:03:26 UTC
Permalink
Hello,

I am trying to deploy a WAR using struts 1.1 with tiles. This WAR is
in an EAR with a single EJB. It deploys fine on WebSphere AEs 4.0.6
on Windows 2000 Professional, but will not deploy on WebSphere AE
4.0.5 or WebSphere AE 4.0.6 on our AIX 4.3 machine. This machine is
behind a firewall and can not access the web.

When I try to deploy the EnterpriseApp, the following exception
occurs. I have searched the newsgroups to no avail. I have tried
multiple locations of the DTD for struts-config.xml and
tiles-defs.xml, using both a PUBLIC identifier and a SYSTEM
identifier. On the windows system, I was able to get this error when
using the SYSTEM identifier with an incorrect path. Can someone shed
some light on this?

[10/19/03 23:43:04:296 EDT] 75bede43 WebGroup X Servlet
Error-[action]: Failed to load servlet:
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:1014)
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:258)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletManager.java:802)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(StrictLifecycleServlet.java:141)
at com.ibm.servlet.engine.webapp.PreInitializedServletState.init(StrictLifecycleServlet.java:254)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(StrictLifecycleServlet.java(Inlined
Compiled Code))
at com.ibm.servlet.engine.webapp.ServletInstance.init(ServletManager.java(Compiled
Code))
at javax.servlet.GenericServlet.init(GenericServlet.java(Inlined
Compiled Code))
at com.ibm.servlet.engine.webapp.ServletManager.addServlet(ServletManager.java(Compiled
Code))
at com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java(Compiled
Code))
at com.ibm.servlet.engine.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java(Compiled
Code))
at com.ibm.servlet.engine.webapp.WebApp.loadServletManager(WebApp.java:1217)
at com.ibm.servlet.engine.webapp.WebApp.init(WebApp.java:145)
at com.ibm.servlet.engine.srt.WebGroup.loadWebApp(WebGroup.java:259)
at com.ibm.servlet.engine.srt.WebGroup.init(WebGroup.java:168)
at com.ibm.servlet.engine.ServletEngine.addWebApplication(ServletEngine.java:856)
at com.ibm.ws.runtime.WebContainer.install(WebContainer.java:36)
at com.ibm.ws.runtime.Server.startModule(Server.java:617)
at com.ibm.ejs.sm.active.ActiveModule.startModule(ActiveModule.java:511)
at com.ibm.ejs.sm.active.ActiveModule.startAction(ActiveModule.java:355)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:722)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:131)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled
Code))
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java(Compiled
Code))
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled
Code))
at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java:62)
at com.ibm.ejs.sm.agent._AdminAgentImpl_Tie._invoke(_AdminAgentImpl_Tie.java:73)
at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.java:532)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:2395)
at com.ibm.CORBA.iiop.OrbWorker.run(OrbWorker.java:186)
at com.ibm.ejs.oa.pool.ThreadPool$PooledWorker.run(ThreadPool.java:104)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:138)
Ryan Hoegg
2003-10-23 23:20:16 UTC
Permalink
Solved my problem. I was using J2EEApplicationVisibility on my AIX
server and the default visibility (Module?) on my Windows machine. I
moved the struts.jar to the root of the EAR and used a manifest
Class-Path entry on my WAR. The application deploys with no errors
now.
Post by Ryan Hoegg
Hello,
I am trying to deploy a WAR using struts 1.1 with tiles. This WAR is
in an EAR with a single EJB. It deploys fine on WebSphere AEs 4.0.6
on Windows 2000 Professional, but will not deploy on WebSphere AE
4.0.5 or WebSphere AE 4.0.6 on our AIX 4.3 machine. This machine is
behind a firewall and can not access the web.
<snip/>

Loading...