"Esta mensagem, incluindo seus anexos, é endereçada exclusivamente à(s)
pessoa(s) e/ou instituições acima indicadas e pode conter informações
confidenciais, particulares ou privilegiadas, as quais não podem, sob
qualquer forma ou pretexto, ser utilizadas, divulgadas, alteradas, impressas
ou copiadas, total ou parcialmente, por pessoas não autorizadas. No caso
desta mensagem ser recebida por erro, por favor, providencie sua exclusão de
qualquer sistema e/ou destrua quaisquer cópias reprográficas, notificando o
remetente imediatamente. Eventual erro de transmissão desta mensagem em
nenhuma hipótese constituirá renúncia à confidencialidade ou a qualquer
direito ou prerrogativa decorrente da mesma."
"This message, and any attachments, is intended only for the named person's
and/or entity's use and may contain confidential, proprietary or legally
privileged information, which shall not be used, disclosed, changed, printed
or copied, in whole or in part, by not intended recipients. If this message
is received by error, please delete it from your system and/or destroy any
hard copies of it and notify the sender, immediately. No confidentiality or
privilege is waived by any mistransmission."
-----Mensagem original-----
De: Mark Thomas [mailto:ma...@apache.org]
Enviada em: segunda-feira, 24 de fevereiro de 2014 14:41
Para: Tomcat Users List
Assunto: 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
