You could still see it from the 'ps' command on Linux, with all of the myriad threads showing up. I have to kill the head pid to stop it. I'm sure it's configuration related if others have Tomcat stop just fine with all of the servlets defined that come with Axis. I've just done a basic install within an existing web app. By just commenting out the new servlet and servlet-mapping entries in web.xml, Tomcat will shut down normally.
Thanks, David ----- Original Message ----- From: "Trieu, Jason T - CNF" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 07, 2003 9:22 AM Subject: RE: Tomcat doesn't stop with axis installed > David, > > >From the exception below, it looks like Tomcat was already down. What was > it that shows Tomcat still running? > > Jason > > -----Original Message----- > From: David Wall [mailto:[EMAIL PROTECTED] > Sent: Friday, July 04, 2003 4:03 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Tomcat doesn't stop with axis installed > > > Well, I do see this exception in catalina.out: > > Stopping service Tomcat-Standalone > java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350) > at > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124) > at java.net.Socket.<init>(Socket.java:268) > at java.net.Socket.<init>(Socket.java:95) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint > .java:326) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java > :397) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav > a:619) > at java.lang.Thread.run(Thread.java:479) > [ERROR] PoolTcpEndpoint - -Caught exception trying to unlock accept. > <java.net.ConnectException: Connection refused> > java.lang.NullPointerException > at > org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint > .java:338) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java > :397) > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav > a:619) > at java.lang.Thread.run(Thread.java:479) > [ERROR] PoolTcpEndpoint - -Caught exception trying to close socket. > <java.lang.NullPointerException> [WARN] PoolTcpEndpoint - -Reinitializing > ServerSocket > > > But I just noted that I see this anyway. If I just uncomment out the > various entries in web.xml that reference the Axis code, then it doesn't > report any other exceptions, but it fails to stop. I've not done anything > but start the application, then stopped it. The only difference between the > two test runs is the changed web.xml -- one with the various axis servlets > defined, the other without. > > I am running with a security manager, and I noted that I needed a BUNCH of > policy entries to get tomcat even started with Axis installed (I'm running > on RedHat Linux, though, with JDK 1.3.1, and I also use Apache 2.0 as the > HTTP front-end using mod_jk with AJP13 connectors): > > // For AXIS > permission java.io.FilePermission > "${catalina.base}/webapps/ssd/WEB-INF/server-config.wsdd", "read,write"; > permission java.io.FilePermission > "${catalina.base}/webapps/ssd/WEB-INF/attachments", "read,write"; > permission java.io.FilePermission > "${catalina.base}/webapps/ssd/WEB-INF/attachments/-", "read,write,delete"; > permission java.io.FilePermission > "${catalina.base}/webapps/ssd/WEB-INF/jwsClasses", "read,write"; > permission java.io.FilePermission > "${catalina.base}/webapps/ssd/WEB-INF/jwsClasses/-", "read,write,delete"; > permission java.io.FilePermission "${catalina.home}/common/-", > "read"; > permission java.io.FilePermission "${catalina.home}/bin/-", "read"; > permission java.io.FilePermission "/home/java3.2/jdk1.3.1_07/-", > "read"; > permission java.lang.RuntimePermission > "accessClassInPackage.sun.tools.*"; > permission java.lang.RuntimePermission "accessDeclaredMembers"; > > Perhaps I have something misconfigured still, and that's what I'm trying to > track down. I have been using Apache SOAP, which works great, but I'd like > to get Axis going for the various improvements > > David > > > ----- Original Message ----- > From: "Steve Viens" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; "'David Wall'" <[EMAIL PROTECTED]> > Sent: Friday, July 04, 2003 11:50 AM > Subject: RE: Tomcat doesn't stop with axis installed > > > > David, > > > > I'm using the same/similar setup and Tomcat shuts down fine via the > > shutdown.bat script. > > > > Axis 1.1 > > Tomcat 4.1.24 > > > > I'm also running on Windows and sing J2SDK 1.4.1. Could it be a > > service you've deployed under Tomcat? Have you checked the Tomcat or > > Axis logs (or the console) for exceptions or other problems? I've > > noticed that Tomcat occationally does not respond to the shutdown.bat > > script after encountering an exception of some kind. > > > > Steve > > > > -----Original Message----- > > From: David Wall [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 04, 2003 2:16 PM > > To: [EMAIL PROTECTED] > > Subject: Tomcat doesn't stop with axis installed > > > > > > I have a web app that starts/stops fine "as is." But when I added the > > servlet/servlet-mappings to support Axis 1.1, tomcat (catalina 4.1) > > doesn't shutdown anymore, as if the servlets (two are loaded at > > startup per the web.xml file in the distro) that are started are not > > stopping. > > > > Is there anything special I need to do to allow Tomcat to be stopped > > normally even with Axis installed? Maybe there's a port conflict? > > > > Thanks, > > David > > > >
