Hi Mark, Thank you for a quick response. It looks the Tomcat 7.0.37 is ok with Solaris 10 on other Sun Sparc machine ... could it be hardware related? Do you have any suggestion for us to capture that possible Shutdown command and/or possible SIGTERM?
Thanks, Jay -----Original Message----- From: Mark Thomas [mailto:ma...@apache.org] Sent: Monday, February 24, 2014 12:41 PM To: Tomcat Users List Subject: Re: Tomcat 7.0.37 issue on our Sun Sparc On 24/02/2014 17:36, Jay wrote: > We newly installed Solaris 10 with all default settings on our Sun > Sparc machine (sun4u sparc SUNW,UltraAX-i2 64-bit sparcv9 kernel modules). > > The OS Version: SunOS hostname 5.10 Generic_147147-26 sun4u sparc > SUNW,UltraAX-i2. > > The Java in the environment: > java version "1.6.0_37" > Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) > Client VM (build 20.12-b01, mixed mode, sharing) > > We downloaded the apache-tomcat-7.0.37.tar.gz and just unpack it into /tmp. > Then we started the Tomcat server using ./startup.sh. > It was working ok after starting and we can see the Tomcat page on Web > Browser at the port 8080. > But The Tomcat stopped internally itself after several hours (looks > randomly) without reason. Nope. Not possible. Tomcat does not decide to shut itself down on a whim. That looks like a clean shut down so either: - something connected to the shut down port and sent the shut down command - something sent a SIGTERM to the Tomcat process. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
