Log files? Sheesh, why didn't I .... Oh well. Here's the log from a shutdown of Tomcat--the startup is below. As you can see it shuts down several contexts just fine and then says /soap wasn't ever started--no surprise:
2003-02-19 11:51:48 StandardHost[localhost]: Removing web application at context path /admin
2003-02-19 11:51:48 StandardHost[localhost]: Removing web application at context path /webdav
2003-02-19 11:51:48 StandardHost[localhost]: Removing web application at context path /examples
2003-02-19 11:51:48 StandardHost[localhost]: Removing web application at context path /tomcat-docs
2003-02-19 11:51:48 StandardHost[localhost]: Removing web application at context path /soap
2003-02-19 11:51:48 StandardHost[localhost]: ContainerBase.removeChild: stop:
LifecycleException: Container StandardContext[/soap] has not been started
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1036)
at org.apache.catalina.core.StandardHostDeployer.remove(StandardHostDeployer.java:420)
at org.apache.catalina.core.StandardHost.remove(StandardHost.java:852)
at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:919)
...
Here's the startup w/ /soap failing and the /manager stuff being deployed properly. The message "Resources start failed:" looks like it might be intending to have something after that colon--a more specific explanation, perhaps?
2003-02-19 11:56:38 StandardContext[/soap]: Starting
2003-02-19 11:56:38 StandardContext[/soap]: Processing start(), current available=false
2003-02-19 11:56:38 StandardContext[/soap]: Configuring default Resources
2003-02-19 11:56:38 StandardContext[/soap]: Resources start failed:
2003-02-19 11:56:38 StandardContext[/soap]: Configuring non-privileged default Loader
2003-02-19 11:56:38 StandardContext[/soap]: Configuring default Manager
2003-02-19 11:56:38 StandardContext[/soap]: Processing standard container startup
2003-02-19 11:56:38 StandardContext[/soap]: Context startup failed due to previous errors
2003-02-19 11:56:38 StandardContext[/soap]: Exception during cleanup after start failed
LifecycleException: Container StandardContext[/soap] has not been started
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3643)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3621)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:738)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347)
at org.apache.catalina.core.StandardService.start(StandardService.java:497)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189)
at org.apache.catalina.startup.Catalina.start(Catalina.java:512)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
2003-02-19 11:56:38 HostConfig[localhost]: Deploying configuration descriptor admin.xml
2003-02-19 11:56:44 HostConfig[localhost]: Deploying configuration descriptor manager.xml
2003-02-19 11:56:44 WebappLoader[/manager]: Deploying class repositories to work directory /var/tomcat4/work/Standalone/localhost/manager
2003-02-19 11:56:44 ContextConfig[/manager]: Configured an authenticator for method BASIC
2003-02-19 11:56:44 StandardManager[/manager]: Seeding random number generator class java.security.SecureRandom
2003-02-19 11:56:44 StandardManager[/manager]: Seeding of random number generator has been completed
2003-02-19 11:56:44 StandardWrapper[/manager:default]: Loading container servlet default
2003-02-19 11:56:44 default: init
2003-02-19 11:56:44 StandardWrapper[/manager:invoker]: Loading container servlet invoker
2003-02-19 11:56:44 invoker: init
2003-02-19 11:56:44 jsp: init
[EMAIL PROTECTED] wrote:
John,
What do the Tomcat logs say? Find the section where it's trying to delpoy
the soap application. That may give you some clues.
I have a soap .war of around the same vintage. If I have time I'll dump it
into a Tomcat 4 installation and let you know if it works.
-Mark
-----Original Message-----
From: J M Craig/Alpha-G [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 19, 2003 12:13 PM
To: [EMAIL PROTECTED]
Subject: Re: Tomcat 4.1.18, JDK 1.4.1, & Soap--Tomcat's already happy
Mark,
Thanks for the suggestions--the one thing I forgot to mention is that I have other JSP apps working fine; the only one that's unhappy is Soap. That is, I already had Tomcat & Apache playing together (never mind how long that took :-|); what I'm trying to do is add Soap to a working set-up. I do have Tomcat listening on 8080 (I've always found that useful myself).
I was afraid that my set-up might be working incorrectly because of the fact that the Soap .war file was apparently built with a 1.3 version of the JDK--but I suppose that would have given me some exceptions rather than the bland message I got.
Thanks,
John
[EMAIL PROTECTED] wrote:
John,configs is to allow
One thing that greatly helps me debugging Tomcat/Apache
Tomcat to listen to its own HTTP port. If you can accessthe resource
(servlet, jsp, whatever) directly from Tomcat then theproblem is with the
Apache-Tomcat connection. Tomcat should listen to port 8080by default.
Once you have the configuration straight then comment outthe HTTP configs
in Tomcat's servlet.xml file or, if it's a development boxjust leave it for
later debugging.the ROOT context
Also, I usually put a silly "Hello World" jsp in my webapps directory
wherever I think I'm having a problem. First I put it in
to see if I can access it there. Then I'll move it arounduntil I get the
Resource Not Available error.I did this
Simplifying helps target the error and its scope.
Good luck,
-Mark
-----Original Message-----
From: J M Craig/Alpha-G [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 19, 2003 4:31 AM
To: [EMAIL PROTECTED]
Subject: Tomcat 4.1.18, JDK 1.4.1, & Soap
Hi Folks,
Does anyone have this working? I understand that 1.4 has rather different XML processing class organization (presumably Xerces.jar isn't necessary). But, do I need to remake the soap.jar and war files with 1.4 in order to make this all work? (I didn't do that because I thought I'd give the .war file a shot and see if it happened to work.)
The instructions relating to Tomcat don't seem to match up with what's installed on my system (I don't find any .sh files, for instance--maybe I should look harder?)--at any rate, I can't see how to change the CLASSPATH settings as described for earlier versions of Tomcat.
I'm using Tomcat 4.1.18, JK2 connector to Apache2, and Java 1.4.1 all on RH Linux 8.0 (I should never try this many new things at once....).
At any rate, I've put the soap.war file into the webapps directory and modifed the Tomcat server.xml file to point to it (I think
file weren'tright--my experience with the correct setting for .war files is limited) and added a section to the JK2 /Apache-side workers2.properties file to ID the context too. The error I get is from "Apache Tomcat/4.1" The requested resource <path here> is not available.
This looks like the kind of error I'd expect if the war
***************there at all or it hadn't been registered properly.*************************************************************
Suggestions welcomed!
John
This email may contain confidential material.***************
If you were not an intended recipient, please notify the sender and delete all copies.
We may monitor email to and from our network.
*************************************************************
****************************************************************************
This email may contain confidential material.
If you were not an intended recipient, please notify the sender and delete all copies.
We may monitor email to and from our network.
****************************************************************************
