Thanks guys for quick reply!
Martin, axis happiness looks OK -- complains about missing xmlsec.jar but I
would doubt that would cause this issue?
With regard to logs, it doesn't appear that I have a tomcat.log! How odd.
There is a catalina.log. Everyhting looks OK there save the last two lines:
Jun 12, 2009 10:54:27 AM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: Failed shutdown of Apache Portable Runtime
Kind of odd...
Chuck, doesn't appear that I have a startup.bat or a shutdown.bat. This
bootstrap.jar is what came with Tomcat it appears.
C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin>dir
Volume in drive C has no label.
Volume Serial Number is 1CD8-D342
Directory of C:\Program Files\Apache Software Foundation\Tomcat 5.5\bin
06/12/2009 03:16 AM <DIR> .
06/12/2009 03:16 AM <DIR> ..
08/28/2008 08:10 PM 24,093 bootstrap.jar
08/28/2008 08:10 PM 52,313 commons-logging-api-1.1.1.jar
08/28/2008 08:10 PM 13,017 tomcat-juli.jar
08/28/2008 08:12 PM 57,344 tomcat5.exe
08/28/2008 08:12 PM 98,304 tomcat5w.exe
5 File(s) 245,071 bytes
2 Dir(s) 15,063,793,664 bytes free
Please note that when I run that tomcat5.exe it has the same behavior as
outlined about -- prints similar output to what I first listed and then
hangs.
Any other ideas?
On Fri, Jun 12, 2009 at 11:25 AM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Brad Heller [mailto:brad.hel...@gmail.com]
> > Subject: bootstrap.jar hangs on startup/shutdown/restart.
> >
> > I was using Tomcat 6.0 but I've moved to Tomcat 5.5 as I was
> > hoping my issue would be resolved be migrating.
>
> No, you're just more likely to introduce other problems. Stay on 6.0.
>
> > The problem seems to be that any time I try to execute
> > bootstrap.jar Tomcat does it's thing and then just...
> > kind of ....hangs there.
>
> If you're not using the supported startup scripts, then you're largely on
> your own.
>
> Does the problem exist using the proper startup.bat and shutdown.bat
> scripts? If they work properly, you need to debug your procedure.
>
> Note that failure of Tomcat to terminate is usually caused by a webapp
> starting up extra threads and failing to manage them properly; the JVM will
> wait until all non-daemon threads have exited before shutting down.
>
> Take a thread dump when Tomcat is in this state and find out what's still
> running.
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
