[fermataintl]

I have a simple struts based application that I can deploy inside myeclipse to tomcat 5 and everything works as expected. In order to deploy this application to a remote server running tomcat 5, can I just drop that same war file into the webapps directory, or must I completely construct a new war for the remote server? The reason I ask is that I have already tried it as I just stated, and it does not work. I get the following in the tomcat log on the remote server:

2005-12-07 06:05:40 ApplicationDispatcher[/banfordsports]: Servlet action is currently unavailable

Any suggestions?

Thanks.
Dean

[Riyad Kalla]

In order to deploy this application to a remote server running tomcat 5, can I just drop that same war file into the webapps directory, or must I completely construct a new war for the remote server?

Nope, just drop the WAR file in.

I get the following in the tomcat log on the remote server:

2005-12-07 06:05:40 ApplicationDispatcher[/banfordsports]: Servlet action is currently unavailable

Check the startup log, make sure the app or the server aren’t throwing exceptions when starting up. I have a feeling you may be developing with Tomcat 5 and deploying to Tomcat 4 or something like that. Tomcat 5 supports the web 2.4 spec and Tomcat 4 only supports the web 2.3 spec, so a problem there would be your web.xml file.

[fermataintl]

I tried it again, this is what was in the log:

2005-12-08 10:51:43 StandardContext[/banfordsports]Marking servlet action as unavailable
2005-12-08 10:51:43 StandardContext[/banfordsports]Servlet /banfordsports threw load() exception
javax.servlet.ServletException: Error instantiating servlet class org.apache.struts.action.ActionServlet
at org.apache.catalina.core.StandardWrapper.loadServlet (StandardWrapper.java:1010)
at org.apache.catalina.core.StandardWrapper.load (StandardWrapper.java:876)
at org.apache.catalina.core.StandardContext.loadOnStartup (StandardContext.java:4017)
at org.apache.catalina.core.StandardContext.start (StandardContext.java:4337)
at org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.access$0 (ContainerBase.java:121)
at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run (ContainerBase.java:143)
at java.security.AccessController.doPrivileged (AccessController.java:96)
at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:805)
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.startup.HostConfig.deployWARs (HostConfig.java:625)
at org.apache.catalina.startup.HostConfig.deployApps (HostConfig.java:431)
at org.apache.catalina.startup.HostConfig.check (HostConfig.java:1083)
at org.apache.catalina.startup.HostConfig.lifecycleEvent (HostConfig.java:327)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSupport.java:119)
at org.apache.catalina.core.StandardHost.backgroundProcess (StandardHost.java:800)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren (ContainerBase.java:1619)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren (ContainerBase.java:1628)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run (ContainerBase.java:1608)
at java.lang.Thread.run (Thread.java:674)
at java.lang.VMThread.run (VMThread.java:123)
—– Root Cause —–
java.lang.SecurityException: Sealing violation loading org.apache.commons.collections.FastHashMap : Package org.apache.commons.collections is sealed.
at java.lang.reflect.Method.invoke0 (Method.java)
at java.lang.reflect.Method.invoke (Method.java:255)
at java.lang.reflect.Constructor.newInstance (Constructor.java:90)
at java.lang.Class.newInstance (Class.java:1143)
at org.apache.catalina.core.StandardWrapper.loadServlet (StandardWrapper.java:1001)
at org.apache.catalina.core.StandardWrapper.load (StandardWrapper.java:876)
at org.apache.catalina.core.StandardContext.loadOnStartup (StandardContext.java:4017)
at org.apache.catalina.core.StandardContext.start (StandardContext.java:4337)
at org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.access$0 (ContainerBase.java:121)
at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run (ContainerBase.java:143)
at java.security.AccessController.doPrivileged (AccessController.java:96)
at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:805)
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.startup.HostConfig.deployWARs (HostConfig.java:625)
at org.apache.catalina.startup.HostConfig.deployApps (HostConfig.java:431)
at org.apache.catalina.startup.HostConfig.check (HostConfig.java:1083)
at org.apache.catalina.startup.HostConfig.lifecycleEvent (HostConfig.java:327)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSupport.java:119)
at org.apache.catalina.core.StandardHost.backgroundProcess (StandardHost.java:800)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren (ContainerBase.java:1619)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren (ContainerBase.java:1628)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run (ContainerBase.java:1608)
at java.lang.Thread.run (Thread.java:674)
at java.lang.VMThread.run (VMThread.java:123)

what do you think that means?

[Riyad Kalla]

Never seen that before, but according to some of these links:
http://www.google.com/search?hl=en&q=sealing+violation&btnG=Google+Search

a sealing violation occurs when you have a JAR that is sealed (commons-collections in this case) and there is another JAR in your classpath that has the same Class in it. So check your /common/lib dir under Tomcat and see if commons-collection is in there.

[Author]

Posts