You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by "Keen, Andy" <Ak...@Cayenta.com> on 2000/12/28 21:18:44 UTC

Tomcat communication

I have Tomcat v3.1 up and running without any null pointer exceptions being
thrown upon startup.  The only possible red flag I see upon startup is the
-2147483646 appearing on the third line from the end:

2000-12-28 11:44:33 - ContextManager: Adding context Ctx( /examples )
2000-12-28 11:44:33 - ContextManager: Adding context Ctx( /admin )
2000-12-28 11:44:33 - Ctx( /soap ): Set debug to 1
2000-12-28 11:44:33 - ContextManager: Adding context Ctx( /soap )
Starting tomcat. Check logs/tomcat.log for error messages
2000-12-28 11:44:33 - ContextManager: Adding context Ctx(  )
2000-12-28 11:44:33 - ContextManager: Adding context Ctx( /test )
2000-12-28 11:44:34 - Ctx( /soap ): XmlReader - init  /soap webapps\soap
2000-12-28 11:44:34 - Ctx( /soap ): Loading -2147483646 jsp
2000-12-28 11:44:35 - PoolTcpConnector: Starting HttpConnectionHandler on
8080
2000-12-28 11:44:35 - PoolTcpConnector: Starting Ajp12ConnectionHandler on
8007

My problem is that nothing on the outside succeeds with Tomcat from here on.


I need to deploy a service.  If I attempt to open http://localhost:8080/soap
from a browser to get to the admin tool, the IE browser comes back with "The
page cannot be found", and the Tomcat window shows this:

2000-12-28 11:59:40 - Ctx( /soap ): 404 R( /soap +  + null) null

If I attempt to deploy manually with the ServiceManagerClient from the
command line, again a 404 is returned, and the Tomcat window shows this:

2000-12-28 12:03:24 - Ctx( /soap ): 404 R( /soap + /servlet/rpcrouter +
null) null

Any attempt to communicate using a SOAP client, such as through the
StockQuote example program, has the same result:

2000-12-28 12:05:23 - Ctx( /soap ): 404 R( /soap + /servlet/rpcrouter +
null) null

Any ideas about what obvious piece I am missing here?

Andy Keen