You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Martin Cavanagh <ca...@con-sense-group.com> on 2007/09/21 09:21:47 UTC
Tomcat crash @ midnight - but why?
Hi everyone.
Yesterday I started a 2nd Apache Server for my program. It was
installed several months ago. Version 5.5.0.23.
The server is running on Windows 2003 Server with Java JRE 1.5.0_11
It worked fine with my program for several hours. Then exactly at
midnight it crashed.
Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1 Mal
passiert. - Which translates to,
Service "Apache Tomcat" stopped unexpectedly. This has happened once
already.
The catalina logs show
21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-443
21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
INFO: Pausing Coyote AJP/1.3 on ajp-8009
21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-443
21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
INFO: Stopping Coyote AJP/1.3 on ajp-8009
Which unfortunately isn't really particularly useful. I can't see any
other logs regarding this. How do I find out why my Tomcat crashed?
Thanks
Martin
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Markus Schönhaber <ma...@schoenhaber.de>.
Martin Cavanagh wrote:
> Why would windows report it as crashing then?
It didn't - as the excerpt from the Windows service log you posted
clearly shows. There is nothing to be read there about Tomcat "crashing"
but just about Tomcat being stopped "unexpectedly" ("unerwartet").
This means nothing more than that the Windows service manager didn't
expect Tomcat to stop because it (the service manager) wasn't told to
stop Tomcat.
As David already explained, Tomcat's log shows that it was stopped using
Tomcat-specific measures (probably by accessing the shutdown port) which
the Windows service manager knows nothing about.
> I know I didn't shut it down, I was sleeping, as I assume everyone else
> was who had access to the system......
I'd try to find out what happened on your machine at midnight. The
scheduled tasks might be something obvious to check.
Regards
mks
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Well nothing really.....
But (assuming attachements are allowed), I've attached them all (except
Std-Out - thats just junk from my program)
Martin
Pid wrote:
> What's immediately before the shutdown description in the logs?
>
> p
>
>
>
> Martin Cavanagh wrote:
>
>> Why would windows report it as crashing then?
>>
>> I know I didn't shut it down, I was sleeping, as I assume everyone else
>> was who had access to the system......
>>
>> Thanks
>>
>> Martin
>>
>> David Delbecq wrote:
>>
>>> According to your log it did not crash. It did shutdown following the
>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>> suggest you investigate possibilities that a local service is setup to
>>> shutdown tomcat at midnight on the server.
>>>
>>> The tomcat shutdown procedure is started when tomcat receive the
>>> SHUTDOWN string at the admin connector (8005 here). This connector is by
>>> default accessible only on local machine.
>>>
>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh s'exprimait en
>>> ces termes:
>>>
>>>
>>>> Hi everyone.
>>>>
>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>> installed several months ago. Version 5.5.0.23.
>>>>
>>>> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>>>
>>>> It worked fine with my program for several hours. Then exactly at
>>>> midnight it crashed.
>>>>
>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>>>> Mal passiert. - Which translates to,
>>>> Service "Apache Tomcat" stopped unexpectedly. This has happened once
>>>> already.
>>>>
>>>> The catalina logs show
>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>> INFO: Stopping service Catalina
>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>
>>>> Which unfortunately isn't really particularly useful. I can't see any
>>>> other logs regarding this. How do I find out why my Tomcat crashed?
>>>>
>>>> Thanks
>>>>
>>>> Martin
>>>>
>>>>
>>>
>>>
>>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Thats how much RAM the Virtual Machine has. I'm not sure what the
actual host machine has, but I'm assuming at least 1024 MB. I believe
this virtual machine is the only one on the Server.
Martin
Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Chuck,
>
> Caldarale, Charles R wrote:
>
>>> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>
>>> 656MB RAM
>>>
>> That's an awfully small amount of memory for a modern system, but is
>> probably not pertinent.
>>
>
> Especially when you're running VMWare server on it, ostensibly to run
> multiple OSs on shared hardware. Yipes!
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFG+mq59CaO5/Lv0PARAnzJAKCgkKIJpYUZvhtZidmj7ksuPOZhsgCgnZkP
> 9q00vG5PoMTxzZQDf42ayvk=
> =224T
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
the JVM is using the default parameters. I installed JRE 1.5.0_11 (which was upto date at the time...)
Should I be using custom parameters?
VMWare means the the host machine, doesn't know that there is no "real" hardware beneath it....
Martin
I'm not overly familiar with VMWare, but is that the memory assigned to
the OS instance? Have you configured your JVM with custom memory
parameters?
>
> p
>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Pid <p...@pidster.com>.
Christopher Schultz wrote:
> Chuck,
>
> Caldarale, Charles R wrote:
>>> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>
>>> 656MB RAM
>> That's an awfully small amount of memory for a modern system, but is
>> probably not pertinent.
>
> Especially when you're running VMWare server on it, ostensibly to run
> multiple OSs on shared hardware. Yipes!
>
> -chris
I'm not overly familiar with VMWare, but is that the memory assigned to
the OS instance? Have you configured your JVM with custom memory
parameters?
p
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chuck,
Caldarale, Charles R wrote:
>> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
>> Subject: Re: Tomcat crash @ midnight - but why?
>>
>> 656MB RAM
>
> That's an awfully small amount of memory for a modern system, but is
> probably not pertinent.
Especially when you're running VMWare server on it, ostensibly to run
multiple OSs on shared hardware. Yipes!
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+mq59CaO5/Lv0PARAnzJAKCgkKIJpYUZvhtZidmj7ksuPOZhsgCgnZkP
9q00vG5PoMTxzZQDf42ayvk=
=224T
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> The Server is started with \Tomcat\bin\tomcat5.exe //RS//Tomcat5 - is
> that normal?
Yes, that's fine.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Caldarale, Charles R wrote:
>> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
>> Subject: Re: Tomcat crash @ midnight - but why?
>>
>> There is no \bin\shutdown.bat file - so this isn't being directly
>> triggered.
>>
>
> That just means you installed from the .exe rather than the .zip
> distribution. Something could still be running around terminating the
> Tomcat service at midnight. Take a look at the properties for the
> Apache Tomcat service in the Windows Control Panel -> Admin Tools ->
> Services, and see if it has any dependencies or other unusual
> characteristics set.
>
There don't seem to be.
The Server is started with \Tomcat\bin\tomcat5.exe //RS//Tomcat5 - is
that normal?
A temp solution appeared there - it is possible to tell windows what to
do if a service stops - i could tell it to automatically restart - which
would be a solution - not the best but i saves me having to monitor it
at midnight....
Martin
> - 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 start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> There is no \bin\shutdown.bat file - so this isn't being directly
> triggered.
That just means you installed from the .exe rather than the .zip
distribution. Something could still be running around terminating the
Tomcat service at midnight. Take a look at the properties for the
Apache Tomcat service in the Windows Control Panel -> Admin Tools ->
Services, and see if it has any dependencies or other unusual
characteristics set.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Hi Charles
Caldarale, Charles R wrote:
>> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
>> Subject: Re: Tomcat crash @ midnight - but why?
>>
>> Hmm maybe this little bit of extra info helps
>>
>
> Not really, but answering Pid's question below might, as would following
> David's suggestions.
>
>
There is no \bin\shutdown.bat file - so this isn't being directly
triggered. There could of course be something triggering this in a
different way, but not via this batch file.
>> 656MB RAM
>>
>
> That's an awfully small amount of memory for a modern system, but is
> probably not pertinent.
>
I know - it is very little. That said I've got Tomcat Servers running
on machine's with much less, without having any problems.
>
>> In the config file there is the standard AJP port (8009) - what does
>> this actually do?
>>
>
> It allows connection between Tomcat and some front end such as Apache
> httpd or IIS.
>
Cool to know - but not the problem then. I can shutdown the AJP
connector then...
>
>>>>> ----- Original Message -----
>>>>> From: "Pid" <p...@pidster.com>
>>>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>>>
>>>>>
>>>>>> What's immediately before the shutdown description in the logs?
>>>>>>
>>>>>>> David Delbecq wrote:
>>>>>>>
>>>>>>>
>>>>>>>> According to your log it did not crash. It did
>>>>>>>> shutdown following the shutdown procedure (which
>>>>>>>> can be executed by bin\shutdown.bat). I suggest
>>>>>>>> you investigate possibilities that a local service
>>>>>>>> is setup to shutdown tomcat at midnight on the server.
>>>>>>>>
>
> - 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 start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> Hmm maybe this little bit of extra info helps
Not really, but answering Pid's question below might, as would following
David's suggestions.
> 656MB RAM
That's an awfully small amount of memory for a modern system, but is
probably not pertinent.
> In the config file there is the standard AJP port (8009) - what does
> this actually do?
It allows connection between Tomcat and some front end such as Apache
httpd or IIS.
> >>> ----- Original Message -----
> >>> From: "Pid" <p...@pidster.com>
> >>> Subject: Re: Tomcat crash @ midnight - but why?
> >>>
> >>>> What's immediately before the shutdown description in the logs?
> >>>>>
> >>>>> David Delbecq wrote:
> >>>>>
> >>>>>> According to your log it did not crash. It did
> >>>>>> shutdown following the shutdown procedure (which
> >>>>>> can be executed by bin\shutdown.bat). I suggest
> >>>>>> you investigate possibilities that a local service
> >>>>>> is setup to shutdown tomcat at midnight on the server.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Sorry everyone - no the the Virtual Machine has 656 MB RAM. The Host
has something > 656MB Ram (1GB?)
Martin
Peter Crowther wrote:
>> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
>> Physical Hardware:
>> 656MB RAM
>> 2.4 Ghz Xeon Processor
>>
>
> Crikey. And a host OS (what host?), VMware on top of that, then Windows
> 2003 as a guest OS? Do you have any RAM left for Tomcat?
>
> - Peter
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by Peter Crowther <Pe...@melandra.com>.
> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
> Physical Hardware:
> 656MB RAM
> 2.4 Ghz Xeon Processor
Crikey. And a host OS (what host?), VMware on top of that, then Windows
2003 as a guest OS? Do you have any RAM left for Tomcat?
- Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Hmm maybe this little bit of extra info helps
Physical Hardware:
656MB RAM
2.4 Ghz Xeon Processor
Martin Cavanagh wrote:
> Hi guys, I'm still having this problem.
>
> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
> and 26.09.
>
> We have VM Ware Server as the hardware - could this cause the problem?
>
> I have a firewall on the machine with only the HTTPS port open.
>
> In the config file there is the standard AJP port (8009) - what does
> this actually do?
>
> Hardware : VM Ware Server
> OS: Win 2003
> Tomcat Version: 5.5.23
>
> Any ideas?
>
> Thanks
>
> Martin
>
> David Smith wrote:
>> Huh?? The shutdown port explicitly binds to the localhost
>> interface. External clients cannot access it anyway. Easily
>> demonstrated with a netstat command.
>>
>> --David
>>
>>
>>
>> Martin Gainty wrote:
>>
>>> Hi Pid
>>>
>>> you're going to need a firewall if someone can telnet to your
>>> shutdown port
>>> (check server.xml for the exact port number)
>>>
>>> Martin--
>>> ----- Original Message -----
>>> From: "Pid" <p...@pidster.com>
>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>> Sent: Friday, September 21, 2007 7:19 AM
>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>
>>>
>>>
>>>
>>>> What's immediately before the shutdown description in the logs?
>>>>
>>>> p
>>>>
>>>>
>>>>
>>>> Martin Cavanagh wrote:
>>>>
>>>>> Why would windows report it as crashing then?
>>>>>
>>>>> I know I didn't shut it down, I was sleeping, as I assume everyone
>>>>> else
>>>>> was who had access to the system......
>>>>>
>>>>> Thanks
>>>>>
>>>>> Martin
>>>>>
>>>>> David Delbecq wrote:
>>>>>
>>>>>> According to your log it did not crash. It did shutdown following
>>>>>> the
>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>> suggest you investigate possibilities that a local service is
>>>>>> setup to
>>>>>> shutdown tomcat at midnight on the server.
>>>>>>
>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>> connector is
>>>>>>
>>> by
>>>
>>>
>>>>>> default accessible only on local machine.
>>>>>>
>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>> s'exprimait en
>>>>>> ces termes:
>>>>>>
>>>>>>
>>>>>>> Hi everyone.
>>>>>>>
>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>
>>>>>>> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>>>>>>
>>>>>>> It worked fine with my program for several hours. Then exactly at
>>>>>>> midnight it crashed.
>>>>>>>
>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>>>>>>> Mal passiert. - Which translates to,
>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has happened
>>>>>>> once
>>>>>>> already.
>>>>>>>
>>>>>>> The catalina logs show
>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>> pause
>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>> INFO: Stopping service Catalina
>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>> destroy
>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>
>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>> see any
>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>> crashed?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Franck Borel [mailto:borel@ub.uni-freiburg.de]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> What do you mean by paging?
http://en.wikipedia.org/wiki/Virtual_memory
http://computer.howstuffworks.com/virtual-memory.htm
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Franck Borel <bo...@ub.uni-freiburg.de>.
Charles,
>> one problem could be insufficient RAM you assigned to Tomcat.
>> How much RAM have you set to your Tomcat?
>
> Don't confuse physical RAM with the virtual memory sizing of the Java
> heap. Having insufficient RAM on the system will only result in
> excessive paging, not process termination.
What do you mean by paging?
>> You can set a minimum of RAM while you set a file
>> called setenv.bat in C:\{CATALINA_HOME}\bin\ for
>> example like this:
>
> As has been stated numerous times in this thread, the OP is running
> Tomcat as a Windows service, so no scripts are available. Heap settings
> have to be done with the tomcat5w.exe program.
Ok...I slip this.
-- Franck
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Franck Borel [mailto:borel@ub.uni-freiburg.de]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> one problem could be insufficient RAM you assigned to Tomcat.
> How much RAM have you set to your Tomcat?
Don't confuse physical RAM with the virtual memory sizing of the Java
heap. Having insufficient RAM on the system will only result in
excessive paging, not process termination. Having insufficient swap
file space could result in termination.
> You can set a minimum of RAM while you set a file
> called setenv.bat in C:\{CATALINA_HOME}\bin\ for
> example like this:
As has been stated numerous times in this thread, the OP is running
Tomcat as a Windows service, so no scripts are available. Heap settings
have to be done with the tomcat5w.exe program.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Franck Borel <bo...@ub.uni-freiburg.de>.
Hi Martin,
one problem could be insufficient RAM you assigned to Tomcat.
How much RAM have you set to your Tomcat? You can set a minimum of RAM while you
set a file called setenv.bat in C:\{CATALINA_HOME}\bin\ for example like this:
JAVA_OPTS="-server -Xms256M -Xmx512M -XX:MaxPermSize=128M"
An other idea: Are you using Xerces for you applications? There is common bug in
the standard Xerces library from SUN, how causes memory leaks.
But I would first take a look to your VMware server. Have you any possibility to
take a copy of your Tomcat on a real machine?
-- Franck
Martin Cavanagh schrieb:
> Thanks Alexey.
>
> Notifications only :(
>
> Keep the ideas coming guys!
>
> just to to check - there is no hidden setting in Tomcat which says -
> shut me down at midnight sometimes for an inexplainable reason?
>
> Martin
>
> Alexey Solofnenko wrote:
>> Maybe it is caused by automatic Windows Update. Did you check it?
>>
>> - Alexey.
>>
>> Martin Cavanagh wrote:
>>> Hi guys, I'm still having this problem.
>>>
>>> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
>>> and 26.09.
>>>
>>> We have VM Ware Server as the hardware - could this cause the problem?
>>>
>>> I have a firewall on the machine with only the HTTPS port open.
>>>
>>> In the config file there is the standard AJP port (8009) - what does
>>> this actually do?
>>>
>>> Hardware : VM Ware Server
>>> OS: Win 2003
>>> Tomcat Version: 5.5.23
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>> Martin
>>>
>>> David Smith wrote:
>>>> Huh?? The shutdown port explicitly binds to the localhost
>>>> interface. External clients cannot access it anyway. Easily
>>>> demonstrated with a netstat command.
>>>>
>>>> --David
>>>>
>>>>
>>>>
>>>> Martin Gainty wrote:
>>>>
>>>>> Hi Pid
>>>>>
>>>>> you're going to need a firewall if someone can telnet to your
>>>>> shutdown port
>>>>> (check server.xml for the exact port number)
>>>>>
>>>>> Martin--
>>>>> ----- Original Message -----
>>>>> From: "Pid" <p...@pidster.com>
>>>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>>>> Sent: Friday, September 21, 2007 7:19 AM
>>>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> What's immediately before the shutdown description in the logs?
>>>>>>
>>>>>> p
>>>>>>
>>>>>>
>>>>>>
>>>>>> Martin Cavanagh wrote:
>>>>>>
>>>>>>> Why would windows report it as crashing then?
>>>>>>>
>>>>>>> I know I didn't shut it down, I was sleeping, as I assume
>>>>>>> everyone else
>>>>>>> was who had access to the system......
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>> David Delbecq wrote:
>>>>>>>
>>>>>>>> According to your log it did not crash. It did shutdown
>>>>>>>> following the
>>>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>>>> suggest you investigate possibilities that a local service is
>>>>>>>> setup to
>>>>>>>> shutdown tomcat at midnight on the server.
>>>>>>>>
>>>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>>>> connector is
>>>>>>>>
>>>>> by
>>>>>
>>>>>
>>>>>>>> default accessible only on local machine.
>>>>>>>>
>>>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>>>> s'exprimait en
>>>>>>>> ces termes:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi everyone.
>>>>>>>>>
>>>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>>>
>>>>>>>>> The server is running on Windows 2003 Server with Java JRE
>>>>>>>>> 1.5.0_11
>>>>>>>>>
>>>>>>>>> It worked fine with my program for several hours. Then exactly at
>>>>>>>>> midnight it crashed.
>>>>>>>>>
>>>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist
>>>>>>>>> bereits 1
>>>>>>>>> Mal passiert. - Which translates to,
>>>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has
>>>>>>>>> happened once
>>>>>>>>> already.
>>>>>>>>>
>>>>>>>>> The catalina logs show
>>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>>> pause
>>>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>>>> INFO: Stopping service Catalina
>>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>>> destroy
>>>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>>>
>>>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>>>> see any
>>>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>>>> crashed?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> Martin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
--
Beste Grüße
Franck Borel
**************************************************************************
Dipl.-Hyd. Franck Borel Telefon: +49[0]761-203 3908
Universitätsbibliothek Fax : +49[0]761-203 3987
Werthmannsplatz 2 E-Mail : borel@ub.uni-freiburg.de
WWW : http://www.ub.uni-freiburg.de
D-79098 Freiburg
**************************************************************************
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Jim Cox <sh...@gmail.com>.
<snippet>
Each time when Tomcat has crashed, it has been at midnight. At exactly
midnight my program changes log directorys - from 20-09-2007 to
21-09-2007. This is a TimerTask. A thread which runs at exactly
midnight....at each of these crashes it has reported "Can't create
directory '\.cs-aterm\logs\SYSTEM\2007-09-25'". I can't help wondering
if that might somehow be related. However if that happens, it should
result in no logs being produced, not in Tomcat crashing.
</snippet>
Are you simply running out of disk space, or file handles, or some
other OS resource?
On 9/26/07, Martin Cavanagh <ca...@con-sense-group.com> wrote:
> Thanks Pid - some good tips
>
> Pid wrote:
> > Martin Cavanagh wrote:
> >
> >
> >> just to to check - there is no hidden setting in Tomcat which says -
> >> shut me down at midnight sometimes for an inexplainable reason?
> >>
> >
> > Oh yeah, forgot about that one. Filip, Remy et al have a funny sense of
> > humour - they're always building crazy easter eggs into Tomcat.
> >
> > No, Martin, there's no secret scheduled shutdown setting.
> >
> phew :)
> > I've asked about the logs before, but I'll ask again...
> > What's in the logs immediately before the shutdown?
> >
> Like I said nothing - I posted them once before - but here they come
> again. This time I'm even including the Std-Out, which is just junk
> from my program......although now I see something that could either be
> the problem - or a symptom of the problem.
>
> Each time when Tomcat has crashed, it has been at midnight. At exactly
> midnight my program changes log directorys - from 20-09-2007 to
> 21-09-2007. This is a TimerTask. A thread which runs at exactly
> midnight....at each of these crashes it has reported "Can't create
> directory '\.cs-aterm\logs\SYSTEM\2007-09-25'". I can't help wondering
> if that might somehow be related. However if that happens, it should
> result in no logs being produced, not in Tomcat crashing.
>
> I've also been using this logging technique for years (inherited from
> the previous programmer). It always worked fine - on many servers.
> > You'll need to look in catalina.out, any app logs and the access log for
> > the app.
> >
> >
> > If you're using the default JVM settings, there's a chance that you
> > might not be running on the server JVM, so your app may have a limited
> > amount of memory at it's disposal (32Mb if memory serves). If it's
> > hanging for some reason (e.g. an app internal job at midnight?) would
> > VMWare shut it down as a bad/dead process?
> >
> Hmmm - how houw I change the JVM into a Server JVM?
> > Evidence of this might be found in the logs, by unexpected gaps in
> > access log traffic, error messages in catalina.out etc.
> >
> >
> > You could also configure jvm gc logging, (google for this), which may
> > tell you something.
> >
> That sounds like this is worth looking into
> >
> > p
> >
> >
> >
> >
> >> Martin
> >>
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
> >
> >
> >
>
>
> --
> Con-Sense-GmbH
> __
> _Martin Cavanagh_
>
> Tel.: +49541 800 83 0
> Fax: +49541 800 83 99
>
> cavanagh@con-sense-group.com <ma...@con-sense-group.com>
>
> Con-Sense GmbH
> Neuer Graben 25
> 49074 Osnabrück
> www.con-sense-group.com <http://www.con-sense-group.com>
>
> Geschäftsführer Eckhard Schulz
> Amtsgericht Hildesheim HRB 3341
>
> 19.09.2007 12:21:38 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-80
> 19.09.2007 12:21:38 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 19.09.2007 12:21:39 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 19.09.2007 12:21:40 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-80
> 19.09.2007 12:21:40 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
> 19.09.2007 12:22:30 org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-80
> 19.09.2007 12:22:30 org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-8009
> 19.09.2007 12:22:30 org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 1860 ms
> 19.09.2007 12:22:30 org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> 19.09.2007 12:22:30 org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
> 19.09.2007 12:22:30 org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 19.09.2007 12:22:31 org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive soap.war
> 19.09.2007 12:22:32 org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-80
> 19.09.2007 12:22:32 org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-8009
> 19.09.2007 12:22:32 org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> 19.09.2007 12:22:32 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2140 ms
>
> 20.09.2007 10:24:39 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-80
> 20.09.2007 10:24:39 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 20.09.2007 10:24:40 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 20.09.2007 10:24:40 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-80
> 20.09.2007 10:24:40 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
> 20.09.2007 12:22:20 org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-80
> 20.09.2007 12:22:22 org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-443
> 20.09.2007 12:22:22 org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-8009
> 20.09.2007 12:22:22 org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 3281 ms
> 20.09.2007 12:22:22 org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> 20.09.2007 12:22:22 org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
> 20.09.2007 12:22:22 org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 20.09.2007 12:22:23 org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive soap.war
> 20.09.2007 12:22:24 org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-80
> 20.09.2007 12:22:24 org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-443
> 20.09.2007 12:22:24 org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-8009
> 20.09.2007 12:22:24 org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> 20.09.2007 12:22:24 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2437 ms
> 20.09.2007 12:22:27 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-80
> 20.09.2007 12:22:27 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-443
> 20.09.2007 12:22:27 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 20.09.2007 12:22:28 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 20.09.2007 12:22:28 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-80
> 20.09.2007 12:22:28 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-443
> 20.09.2007 12:22:28 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
> 20.09.2007 12:23:06 org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-443
> 20.09.2007 12:23:06 org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-8009
> 20.09.2007 12:23:06 org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 2344 ms
> 20.09.2007 12:23:06 org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> 20.09.2007 12:23:06 org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
> 20.09.2007 12:23:06 org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 20.09.2007 12:23:07 org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive soap.war
> 20.09.2007 12:23:08 org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-443
> 20.09.2007 12:23:08 org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-8009
> 20.09.2007 12:23:08 org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> 20.09.2007 12:23:08 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2141 ms
> 20.09.2007 17:25:03 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-443
> 20.09.2007 17:25:03 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 20.09.2007 17:25:04 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 20.09.2007 17:25:04 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-443
> 20.09.2007 17:25:04 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
> 20.09.2007 17:26:01 org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-443
> 20.09.2007 17:26:01 org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-8009
> 20.09.2007 17:26:01 org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 2391 ms
> 20.09.2007 17:26:01 org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> 20.09.2007 17:26:01 org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
> 20.09.2007 17:26:01 org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 20.09.2007 17:26:02 org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive soap.war
> 20.09.2007 17:26:03 org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-443
> 20.09.2007 17:26:03 org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-8009
> 20.09.2007 17:26:03 org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> 20.09.2007 17:26:03 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2640 ms
>
> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-443
> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-443
> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
> 21.09.2007 07:06:33 org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-443
> 21.09.2007 07:06:33 org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-8009
> 21.09.2007 07:06:33 org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 2453 ms
> 21.09.2007 07:06:33 org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> 21.09.2007 07:06:33 org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
> 21.09.2007 07:06:33 org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 21.09.2007 07:06:34 org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive soap.war
> 21.09.2007 07:06:35 org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-443
> 21.09.2007 07:06:35 org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-8009
> 21.09.2007 07:06:35 org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> 21.09.2007 07:06:35 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2281 ms
> 21.09.2007 07:56:05 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-443
> 21.09.2007 07:56:05 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 21.09.2007 07:56:06 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 21.09.2007 07:56:06 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-443
> 21.09.2007 07:56:06 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
> 21.09.2007 07:56:41 org.apache.coyote.http11.Http11AprProtocol init
> INFO: Initializing Coyote HTTP/1.1 on http-443
> 21.09.2007 07:56:41 org.apache.coyote.ajp.AjpAprProtocol init
> INFO: Initializing Coyote AJP/1.3 on ajp-8009
> 21.09.2007 07:56:41 org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 2610 ms
> 21.09.2007 07:56:41 org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> 21.09.2007 07:56:41 org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
> 21.09.2007 07:56:41 org.apache.catalina.core.StandardHost start
> INFO: XML validation disabled
> 21.09.2007 07:56:43 org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive soap.war
> 21.09.2007 07:56:43 org.apache.coyote.http11.Http11AprProtocol start
> INFO: Starting Coyote HTTP/1.1 on http-443
> 21.09.2007 07:56:43 org.apache.coyote.ajp.AjpAprProtocol start
> INFO: Starting Coyote AJP/1.3 on ajp-8009
> 21.09.2007 07:56:43 org.apache.catalina.storeconfig.StoreLoader load
> INFO: Find registry server-registry.xml at classpath resource
> 21.09.2007 07:56:43 org.apache.catalina.startup.Catalina start
> INFO: Server startup in 2281 ms
>
>
>
> [2007-09-19 12:22:27] [info] Running Service...
> [2007-09-19 12:22:27] [info] Starting service...
> [2007-09-19 12:22:29] [info] Service started in 1296 ms.
> [2007-09-20 10:24:39] [info] Service STOP signaled
> [2007-09-20 10:24:39] [info] Stopping service...
> [2007-09-20 10:24:40] [info] Service stopped.
> [2007-09-20 10:24:40] [info] Run service finished.
> [2007-09-20 10:24:40] [info] Procrun finished.
>
> [2007-09-20 12:22:18] [info] Running Service...
> [2007-09-20 12:22:18] [info] Starting service...
> [2007-09-20 12:22:19] [info] Service started in 1453 ms.
> [2007-09-20 12:22:27] [info] Service STOP signaled
> [2007-09-20 12:22:27] [info] Stopping service...
> [2007-09-20 12:22:28] [info] Service stopped.
> [2007-09-20 12:22:28] [info] Run service finished.
> [2007-09-20 12:22:28] [info] Procrun finished.
> [2007-09-20 12:23:03] [info] Running Service...
> [2007-09-20 12:23:03] [info] Starting service...
> [2007-09-20 12:23:04] [info] Service started in 1265 ms.
> [2007-09-20 17:25:03] [info] Service STOP signaled
> [2007-09-20 17:25:03] [info] Stopping service...
> [2007-09-20 17:25:04] [info] Service stopped.
> [2007-09-20 17:25:04] [info] Run service finished.
> [2007-09-20 17:25:04] [info] Procrun finished.
> [2007-09-20 17:25:57] [info] Running Service...
> [2007-09-20 17:25:57] [info] Starting service...
> [2007-09-20 17:25:59] [info] Service started in 1312 ms.
>
> [2007-09-21 07:06:29] [info] Running Service...
> [2007-09-21 07:06:29] [info] Starting service...
> [2007-09-21 07:06:31] [info] Service started in 1453 ms.
> [2007-09-21 07:56:05] [info] Service STOP signaled
> [2007-09-21 07:56:05] [info] Stopping service...
> [2007-09-21 07:56:06] [info] Service stopped.
> [2007-09-21 07:56:06] [info] Run service finished.
> [2007-09-21 07:56:06] [info] Procrun finished.
> [2007-09-21 07:56:38] [info] Running Service...
> [2007-09-21 07:56:38] [info] Starting service...
> [2007-09-21 07:56:39] [info] Service started in 1281 ms.
>
> 20.09.2007 22:03:18 org.apache.catalina.core.StandardWrapperValve invoke
> SCHWERWIEGEND: Servlet.service() for servlet rpcrouter threw exception
> java.io.IOException
> at org.apache.coyote.http11.InternalAprOutputBuffer.flushBuffer(InternalAprOutputBuffer.java:700)
> at org.apache.coyote.http11.InternalAprOutputBuffer.flush(InternalAprOutputBuffer.java:288)
> at org.apache.coyote.http11.Http11AprProcessor.action(Http11AprProcessor.java:967)
> at org.apache.coyote.Response.action(Response.java:183)
> at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:322)
> at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
> at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)
> at org.apache.soap.transport.TransportMessage.writeTo(TransportMessage.java:580)
> at org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:408)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:834)
> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1286)
> at java.lang.Thread.run(Unknown Source)
>
>
>
> 21.09.2007 08:04:29 org.apache.catalina.core.ApplicationContext log
> INFO: HTMLManager: init: Associated with Deployer 'Catalina:type=Deployer,host=localhost'
> 21.09.2007 08:04:29 org.apache.catalina.core.ApplicationContext log
> INFO: HTMLManager: init: Global resources are available
> 21.09.2007 08:04:29 org.apache.catalina.core.ApplicationContext log
> INFO: HTMLManager: list: Listing contexts for virtual host 'localhost'
>
>
>
>
>
>
> *** AT_Server-static Start ****
> *** AT_Server-static Ende ****
> Java-Version: 1.5.0_11-b03
> m_filePath:C:\Aterm\Tomcat
> m_fileName:besterm.properties
> xxxxxxxxxIch habe die Props gelesen----------------
> db-address = @192.168.161.61:1521:etn2
> tracelevel = 10
> db-pw = bestterm
> loglevel = 10
> errorlevel = 10
> NOT_DB_SERVER = true
> db-user = bestterm
> DB_SERVER_SOAP = http://192.168.161.61/
> soap-service-name = urn:AT_Server
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\AT_Server_error.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\AT_Server_log.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\AT_Server_trace.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> DirCreationService is activated
> xxxxxxxxxIch schreibe die Props----------------
> *** AT_Server-static Start ****
> *** AT_Server-static Ende ****
> Java-Version: 1.5.0_11-b03
> m_filePath:C:\Aterm\Tomcat
> m_fileName:besterm.properties
> xxxxxxxxxIch habe die Props gelesen----------------
> db-address = @192.168.161.61:1521:etn2
> tracelevel = 10
> db-pw = bestterm
> loglevel = 10
> errorlevel = 10
> NOT_DB_SERVER = true
> db-user = bestterm
> DB_SERVER_SOAP = http://192.168.161.61/
> soap-service-name = urn:AT_Server
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\AT_Server_error.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\AT_Server_log.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\AT_Server_trace.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> DirCreationService is activated
> xxxxxxxxxIch schreibe die Props----------------
> Creating logger
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\BTDispatcherRedirectorerror.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-20\BTDispatcherRedirectorlog.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-20
> DirCreationService is activated
> ---finish init(ServletConfig config)
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> ---CS_SAP_Conn_Soap_Client creating... urn:urn:AT_Server
> Time before call logClientProb is:Thu Sep 20 21:08:14 CEST 2007
> failed to get address from JNLP service using localhost
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:16 CEST 2007
> Problem mit der Fehler nr: 13015 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:16 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:17 CEST 2007
> Problem mit der Fehler nr: 13016 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:19 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:19 CEST 2007
> Problem mit der Fehler nr: 13017 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:20 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:20 CEST 2007
> Problem mit der Fehler nr: 13018 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:45 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:45 CEST 2007
> Problem mit der Fehler nr: 13019 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:51 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:51 CEST 2007
> Problem mit der Fehler nr: 13020 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:51 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:51 CEST 2007
> Problem mit der Fehler nr: 13021 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:51 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:51 CEST 2007
> Problem mit der Fehler nr: 13022 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:51 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13023 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13024 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13025 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13026 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13027 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13028 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13029 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:52 CEST 2007
> Problem mit der Fehler nr: 13030 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> Problem mit der Fehler nr: 13031 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> Problem mit der Fehler nr: 13032 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> Problem mit der Fehler nr: 13033 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> Problem mit der Fehler nr: 13034 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> Problem mit der Fehler nr: 13035 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> Problem mit der Fehler nr: 13036 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> Problem mit der Fehler nr: 13037 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> Problem mit der Fehler nr: 13038 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> Problem mit der Fehler nr: 13039 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> Problem mit der Fehler nr: 13040 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> Problem mit der Fehler nr: 13041 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> Problem mit der Fehler nr: 13042 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> Problem mit der Fehler nr: 13043 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> Problem mit der Fehler nr: 13044 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> Problem mit der Fehler nr: 13045 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> Problem mit der Fehler nr: 13046 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> Problem mit der Fehler nr: 13047 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> Problem mit der Fehler nr: 13048 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> Problem mit der Fehler nr: 13049 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> Problem mit der Fehler nr: 13050 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:08:55 CEST 2007
> Problem mit der Fehler nr: 13051 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> Problem mit der Fehler nr: 13052 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> Problem mit der Fehler nr: 13053 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> Problem mit der Fehler nr: 13054 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 21:09:09 CEST 2007
> Problem mit der Fehler nr: 13055 wurde aufgenommen
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> ---CS_SAP_Conn_Soap_Client start orderBasketEntries
> bestellArt:0 kdInstId:KKL spartenId:40 oeId:KA_I8 ordererUserId:cs lieferantenId:0000016149 lieferant:OPTIPLAN GMBH
> Time before call orderBasketEntries is:Thu Sep 20 21:38:22 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = orderBasketEntries
> Time after call orderBasketEntries is:Thu Sep 20 21:38:23 CEST 2007
> ---CS_SAP_Conn_Soap_Client finish orderBasketEntries
> Time before call logClientProb is:Thu Sep 20 22:01:16 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:16 CEST 2007
> Problem mit der Fehler nr: 13056 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:17 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:17 CEST 2007
> Problem mit der Fehler nr: 13057 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:19 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:19 CEST 2007
> Problem mit der Fehler nr: 13058 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:22 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:22 CEST 2007
> Problem mit der Fehler nr: 13059 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:26 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:26 CEST 2007
> Problem mit der Fehler nr: 13060 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:30 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:30 CEST 2007
> Problem mit der Fehler nr: 13061 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:31 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:31 CEST 2007
> Problem mit der Fehler nr: 13062 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:31 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:31 CEST 2007
> Problem mit der Fehler nr: 13063 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:32 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:32 CEST 2007
> Problem mit der Fehler nr: 13064 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:33 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:33 CEST 2007
> Problem mit der Fehler nr: 13065 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:33 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:33 CEST 2007
> Problem mit der Fehler nr: 13066 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:34 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:34 CEST 2007
> Problem mit der Fehler nr: 13067 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:35 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:35 CEST 2007
> Problem mit der Fehler nr: 13068 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:36 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:36 CEST 2007
> Problem mit der Fehler nr: 13069 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:36 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:36 CEST 2007
> Problem mit der Fehler nr: 13070 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:37 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:37 CEST 2007
> Problem mit der Fehler nr: 13071 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:37 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:37 CEST 2007
> Problem mit der Fehler nr: 13072 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:38 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:38 CEST 2007
> Problem mit der Fehler nr: 13073 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:39 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:39 CEST 2007
> Problem mit der Fehler nr: 13074 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:40 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:40 CEST 2007
> Problem mit der Fehler nr: 13075 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:43 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:43 CEST 2007
> Problem mit der Fehler nr: 13076 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:44 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:44 CEST 2007
> Problem mit der Fehler nr: 13077 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:49 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:49 CEST 2007
> Problem mit der Fehler nr: 13078 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:49 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:49 CEST 2007
> Problem mit der Fehler nr: 13079 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:50 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:50 CEST 2007
> Problem mit der Fehler nr: 13080 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:50 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:50 CEST 2007
> Problem mit der Fehler nr: 13081 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:52 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:52 CEST 2007
> Problem mit der Fehler nr: 13082 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:53 CEST 2007
> Problem mit der Fehler nr: 13083 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:53 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:53 CEST 2007
> Problem mit der Fehler nr: 13084 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:54 CEST 2007
> Problem mit der Fehler nr: 13085 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:54 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:54 CEST 2007
> Problem mit der Fehler nr: 13086 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:55 CEST 2007
> Problem mit der Fehler nr: 13087 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:55 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:55 CEST 2007
> Problem mit der Fehler nr: 13088 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:01:56 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:01:56 CEST 2007
> Problem mit der Fehler nr: 13089 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:02:03 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:02:03 CEST 2007
> Problem mit der Fehler nr: 13090 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:02:03 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:02:03 CEST 2007
> Problem mit der Fehler nr: 13091 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:02:04 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:02:04 CEST 2007
> Problem mit der Fehler nr: 13092 wurde aufgenommen
> Time before call logClientProb is:Thu Sep 20 22:02:05 CEST 2007
> URL = http://192.168.161.61/soap/servlet/rpcrouter - Methode = logClientProb
> Time after call logClientProb is:Thu Sep 20 22:02:05 CEST 2007
> Problem mit der Fehler nr: 13093 wurde aufgenommen
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_error.log
> Can't create directory '\.cs-aterm\logs\SYSTEM\2007-09-21'
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_log.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_trace.log
>
> *** AT_Server-static Start ****
> *** AT_Server-static Ende ****
> Java-Version: 1.5.0_11-b03
> m_filePath:C:\Aterm\Tomcat
> m_fileName:besterm.properties
> xxxxxxxxxIch habe die Props gelesen----------------
> db-address = @192.168.161.61:1521:etn2
> tracelevel = 10
> db-pw = bestterm
> loglevel = 10
> errorlevel = 10
> NOT_DB_SERVER = true
> db-user = bestterm
> DB_SERVER_SOAP = http://192.168.161.61/
> soap-service-name = urn:AT_Server
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_error.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_log.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_trace.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> DirCreationService is activated
> xxxxxxxxxIch schreibe die Props----------------
> Creating logger
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\BTDispatcherRedirectorerror.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\BTDispatcherRedirectorlog.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> DirCreationService is activated
> ---finish init(ServletConfig config)
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> *** AT_Server-static Start ****
> *** AT_Server-static Ende ****
> Java-Version: 1.5.0_11-b03
> m_filePath:C:\Aterm\Tomcat
> m_fileName:besterm.properties
> xxxxxxxxxIch habe die Props gelesen----------------
> db-address = @192.168.161.61:1521:etn2
> tracelevel = 10
> db-pw = bestterm
> loglevel = 10
> errorlevel = 10
> NOT_DB_SERVER = true
> db-user = bestterm
> DB_SERVER_SOAP = http://192.168.161.61/
> soap-service-name = urn:AT_Server
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_error.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_log.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\AT_Server_trace.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> DirCreationService is activated
> xxxxxxxxxIch schreibe die Props----------------
> Creating logger
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\BTDispatcherRedirectorerror.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-21\BTDispatcherRedirectorlog.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-21
> DirCreationService is activated
> ---finish init(ServletConfig config)
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> send mit urlString=http://192.168.161.61/AnforderungsterminalServer/servlet/BTDispatcher
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-22
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-22
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-22\AT_Server_error.log
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-22\BTDispatcherRedirectorerror.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-22
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-22\AT_Server_log.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-22
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-22\BTDispatcherRedirectorlog.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-22
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-22\AT_Server_trace.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-23
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-23
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-23\BTDispatcherRedirectorerror.log
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-23\AT_Server_error.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-23
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-23\BTDispatcherRedirectorlog.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-23
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-23\AT_Server_log.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-23
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-23\AT_Server_trace.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-24
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-24
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-24\AT_Server_error.log
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-24\BTDispatcherRedirectorerror.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-24
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-24
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-24\AT_Server_log.log
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-24\BTDispatcherRedirectorlog.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-24
> Traces will be written to \.cs-aterm\logs\SYSTEM\2007-09-24\AT_Server_trace.log
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-25
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-25
> Errors will be written to \.cs-aterm\logs\SYSTEM\2007-09-25\BTDispatcherRedirectorerror.log
> Can't create directory '\.cs-aterm\logs\SYSTEM\2007-09-25'
> logPath = /.cs-aterm\logs\SYSTEM\2007-09-25
> Logs will be written to \.cs-aterm\logs\SYSTEM\2007-09-25\BTDispatcherRedirectorlog.log
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Tim Funk <fu...@joedog.org>.
To test the TimerTask theory - I'd suggest changing the TimerTask to run
at 12:30 and see the next crash
-Tim
Pid wrote:
> Martin Cavanagh wrote:
>
>> Each time when Tomcat has crashed, it has been at midnight. At exactly
>> midnight my program changes log directorys - from 20-09-2007 to
>> 21-09-2007. This is a TimerTask. A thread which runs at exactly
>> midnight....at each of these crashes it has reported "Can't create
>> directory '\.cs-aterm\logs\SYSTEM\2007-09-25'". I can't help wondering
>> if that might somehow be related. However if that happens, it should
>> result in no logs being produced, not in Tomcat crashing.
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
My logs are being being redirected to other directorys, where log levels
are being applied. This are just the tomcat logs, since its tomcat
which is crashing.
The logs from stdout are just cases where things are still (or also)
being written to Std out -which is the exception rather than the rule.
Pid wrote:
> Martin Cavanagh wrote:
>
>
>> Each time when Tomcat has crashed, it has been at midnight. At exactly
>> midnight my program changes log directorys - from 20-09-2007 to
>> 21-09-2007. This is a TimerTask. A thread which runs at exactly
>> midnight....at each of these crashes it has reported "Can't create
>> directory '\.cs-aterm\logs\SYSTEM\2007-09-25'". I can't help wondering
>> if that might somehow be related. However if that happens, it should
>> result in no logs being produced, not in Tomcat crashing.
>>
>
> Is this the case for all 3 shutdown instances?
>
> If so, I'd suggest that understanding why that is happening will lead
> you to the cause of the shutdown...
>
> You're not really logging much from your app it would appear - is there
> any way to increase the logging level, or haven't you got much in the
> way of logging in the code?
>
> p
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Pid <p...@pidster.com>.
Martin Cavanagh wrote:
> Each time when Tomcat has crashed, it has been at midnight. At exactly
> midnight my program changes log directorys - from 20-09-2007 to
> 21-09-2007. This is a TimerTask. A thread which runs at exactly
> midnight....at each of these crashes it has reported "Can't create
> directory '\.cs-aterm\logs\SYSTEM\2007-09-25'". I can't help wondering
> if that might somehow be related. However if that happens, it should
> result in no logs being produced, not in Tomcat crashing.
Is this the case for all 3 shutdown instances?
If so, I'd suggest that understanding why that is happening will lead
you to the cause of the shutdown...
You're not really logging much from your app it would appear - is there
any way to increase the logging level, or haven't you got much in the
way of logging in the code?
p
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Pid <p...@pidster.com>.
Caldarale, Charles R wrote:
>> From: Pid [mailto:p@pidster.com]
>> Subject: Re: Tomcat crash @ midnight - but why?
>>
>> -server will do it, if it's not autoselected.
>
> Tomcat is running a Windows service, so command line options cannot be
> used.
>
> - Chuck
(doh)
> 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 start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Pid [mailto:p@pidster.com]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> -server will do it, if it's not autoselected.
Tomcat is running a Windows service, so command line options cannot be
used.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Peter Stavrinides <p....@albourne.com>.
Because tomcat is running as a service, permissions may be an issue for
creating/writing to the directory in question, most likely this is why
the task fails... unless the Timer task is a critical process don't use
System.exit(0), just check the if the task runs or not and if not log
the error/send an alert.
Peter
Martin Cavanagh wrote:
> Mark Thomas wrote:
>> Martin Cavanagh wrote:
>>
>>> Heres trouble...........the System does call System.exit(), when it
>>> can't create the directory... - so I understand why my application
>>> would
>>> stop- but why would tomcat shutdown?
>>>
>>
>> And there is the problem. System.exit() will kill the JVM (unless you
>> are running under a security manager and don't give the code permission
>> to do this). Tomcat registers a shutdown hook on startup which performs
>> a clean stop if the JVM is stopped. This is why you see what appears to
>> be a 'normal' shutdown in the logs.
>>
>> Mark
>>
> ahh good - and now I "just" need to work out why it can't create
> directorys on this one server - great!
>
> Now before I execute the System.exit I do a dump.
>
> Thanks alot. Additionaly I'll be installing the JDK so I can use the
> server JVM.
>
> Martin
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by Peter Crowther <Pe...@melandra.com>.
> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
> Now before I execute the System.exit I do a dump.
Are you sure shutting down the entire Tomcat instance is the appropriate
thing to do if you can't create the log directory? As opposed to, say,
logging the problem and returning an appropriate status code to the
client?
If you're looking for environmental factors, here's one to think about:
does the server have antivirus with real-time scanning enabled? This
can be a performance pig on Windows, and especially on slower or virtual
servers it can cause timeouts on pretty much any file operation. If it
has, you might want to consider disabling real-time scanning altogether,
or at least preventing scanning on the folders in which your log
directories will be created. The problem's not purely theoretical -
I've had clients lose SQL Server databases because of this issue, for
example.
- Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Mark Thomas wrote:
> Martin Cavanagh wrote:
>
>> Heres trouble...........the System does call System.exit(), when it
>> can't create the directory... - so I understand why my application would
>> stop- but why would tomcat shutdown?
>>
>
> And there is the problem. System.exit() will kill the JVM (unless you
> are running under a security manager and don't give the code permission
> to do this). Tomcat registers a shutdown hook on startup which performs
> a clean stop if the JVM is stopped. This is why you see what appears to
> be a 'normal' shutdown in the logs.
>
> Mark
>
ahh good - and now I "just" need to work out why it can't create
directorys on this one server - great!
Now before I execute the System.exit I do a dump.
Thanks alot. Additionaly I'll be installing the JDK so I can use the
server JVM.
Martin
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Mark Thomas <ma...@apache.org>.
Martin Cavanagh wrote:
> Heres trouble...........the System does call System.exit(), when it
> can't create the directory... - so I understand why my application would
> stop- but why would tomcat shutdown?
And there is the problem. System.exit() will kill the JVM (unless you
are running under a security manager and don't give the code permission
to do this). Tomcat registers a shutdown hook on startup which performs
a clean stop if the JVM is stopped. This is why you see what appears to
be a 'normal' shutdown in the logs.
Mark
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Darek Czarkowski wrote:
> Martin Cavanagh wrote:
>> Caldarale, Charles R wrote:
>>>> From: Darek Czarkowski [mailto:dczarkowski@infinitesource.ca]
>>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>>
>>>> Now, this would be funny, can you search the source code of the
>>>> deployed application for System.exit call?
>>>>
>>>
>>>
>> Heres trouble...........the System does call System.exit(), when it
>> can't create the directory... - so I understand why my application
>> would stop- but why would tomcat shutdown?
>>
>> It's also using the client JVM not the server JVM (I installed JRE
>> and there is no server JVM)
>
> See that is funny after all, as other users explained system.exit will
> terminate JVM and not just your application. You should NEVER use this
> call in your application. Try to deal with the error in another way.
>
I guess it is a little bit funny - nah you live - you learn.
Well thanks for the help
Martin
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Darek Czarkowski <dc...@infinitesource.ca>.
Martin Cavanagh wrote:
> Caldarale, Charles R wrote:
>>> From: Darek Czarkowski [mailto:dczarkowski@infinitesource.ca]
>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>
>>> Now, this would be funny, can you search the source code of the
>>> deployed application for System.exit call?
>>>
>>
>>
> Heres trouble...........the System does call System.exit(), when it
> can't create the directory... - so I understand why my application
> would stop- but why would tomcat shutdown?
>
> It's also using the client JVM not the server JVM (I installed JRE and
> there is no server JVM)
See that is funny after all, as other users explained system.exit will
terminate JVM and not just your application. You should NEVER use this
call in your application. Try to deal with the error in another way.
--
Darek Czarkowski
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Pid <p...@pidster.com>.
Martin Cavanagh wrote:
> Caldarale, Charles R wrote:
>>> From: Darek Czarkowski [mailto:dczarkowski@infinitesource.ca]
>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>
>>> Now, this would be funny, can you search the source code of the
>>> deployed application for System.exit call?
>>
> Heres trouble...........the System does call System.exit(), when it
> can't create the directory... - so I understand why my application would
> stop- but why would tomcat shutdown?
Because it shuts down the JVM, not your application.
http://tomcat.apache.org/tomcat-5.5-doc/security-manager-howto.html
p
> It's also using the client JVM not the server JVM (I installed JRE and
> there is no server JVM)
>> Doesn't quite fit the symptoms. When a webapp calls System.exit(), the
>> following entry does NOT appear in the logs:
>>
>> Sep 26, 2007 1:23:07 PM org.apache.coyote.http11.Http11Protocol pause
>> INFO: Pausing Coyote HTTP/1.1 on http-8080
>>
>> Whereas when the service is stopped or the shutdown string is sent to
>> the shutdown port, the above message does appear in the logs. The OP
>> did report that the "Pausing ..." message is present.
>>
>> - 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 start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Caldarale, Charles R wrote:
>> From: Darek Czarkowski [mailto:dczarkowski@infinitesource.ca]
>> Subject: Re: Tomcat crash @ midnight - but why?
>>
>> Now, this would be funny, can you search the source code of
>> the deployed application for System.exit call?
>>
>
>
Heres trouble...........the System does call System.exit(), when it
can't create the directory... - so I understand why my application would
stop- but why would tomcat shutdown?
It's also using the client JVM not the server JVM (I installed JRE and
there is no server JVM)
> Doesn't quite fit the symptoms. When a webapp calls System.exit(), the
> following entry does NOT appear in the logs:
>
> Sep 26, 2007 1:23:07 PM org.apache.coyote.http11.Http11Protocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-8080
>
> Whereas when the service is stopped or the shutdown string is sent to
> the shutdown port, the above message does appear in the logs. The OP
> did report that the "Pausing ..." message is present.
>
> - 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 start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Darek Czarkowski [mailto:dczarkowski@infinitesource.ca]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> Now, this would be funny, can you search the source code of
> the deployed application for System.exit call?
Doesn't quite fit the symptoms. When a webapp calls System.exit(), the
following entry does NOT appear in the logs:
Sep 26, 2007 1:23:07 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Whereas when the service is stopped or the shutdown string is sent to
the shutdown port, the above message does appear in the logs. The OP
did report that the "Pausing ..." message is present.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Darek Czarkowski <dc...@infinitesource.ca>.
Martin Cavanagh wrote:
> Each time when Tomcat has crashed, it has been at midnight. At
> exactly midnight my program changes log directorys - from 20-09-2007
> to 21-09-2007. This is a TimerTask. A thread which runs at exactly
> midnight....at each of these crashes it has reported "Can't create
> directory '\.cs-aterm\logs\SYSTEM\2007-09-25'". I can't help
> wondering if that might somehow be related. However if that happens,
> it should result in no logs being produced, not in Tomcat crashing.
Now, this would be funny, can you search the source code of the deployed
application for System.exit call? :p
--
Darek Czarkowski
Ph: 604 294 6557 (Ext. 113)
Fx: 604 294 6507
www.infinitesource.ca
darekc at infinitesource dot ca
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Pid <p...@pidster.com>.
Martin Cavanagh wrote:
> Thanks Pid - some good tips
> Hmmm - how houw I change the JVM into a Server JVM?
(google is your friend).
-server will do it, if it's not autoselected.
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Martin Cavanagh [mailto:cavanagh@con-sense-group.com]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> Hmmm - how houw I change the JVM into a Server JVM?
Server vs client JVM is likely to be totally irrelevant, but in any
event, run the tomcat6w.exe program, go to the Java tab, and see what is
set for Java Virtual Machine. If the "Use default" check box is set,
clear it, and enter the location of the server jvm.dll file (e.g.,
C:\jdk1.6.0\jre\bin\server\jvm.dll). You'll have to change the location
to match your JVM installation, of course.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Thanks Pid - some good tips
Pid wrote:
> Martin Cavanagh wrote:
>
>
>> just to to check - there is no hidden setting in Tomcat which says -
>> shut me down at midnight sometimes for an inexplainable reason?
>>
>
> Oh yeah, forgot about that one. Filip, Remy et al have a funny sense of
> humour - they're always building crazy easter eggs into Tomcat.
>
> No, Martin, there's no secret scheduled shutdown setting.
>
phew :)
> I've asked about the logs before, but I'll ask again...
> What's in the logs immediately before the shutdown?
>
Like I said nothing - I posted them once before - but here they come
again. This time I'm even including the Std-Out, which is just junk
from my program......although now I see something that could either be
the problem - or a symptom of the problem.
Each time when Tomcat has crashed, it has been at midnight. At exactly
midnight my program changes log directorys - from 20-09-2007 to
21-09-2007. This is a TimerTask. A thread which runs at exactly
midnight....at each of these crashes it has reported "Can't create
directory '\.cs-aterm\logs\SYSTEM\2007-09-25'". I can't help wondering
if that might somehow be related. However if that happens, it should
result in no logs being produced, not in Tomcat crashing.
I've also been using this logging technique for years (inherited from
the previous programmer). It always worked fine - on many servers.
> You'll need to look in catalina.out, any app logs and the access log for
> the app.
>
>
> If you're using the default JVM settings, there's a chance that you
> might not be running on the server JVM, so your app may have a limited
> amount of memory at it's disposal (32Mb if memory serves). If it's
> hanging for some reason (e.g. an app internal job at midnight?) would
> VMWare shut it down as a bad/dead process?
>
Hmmm - how houw I change the JVM into a Server JVM?
> Evidence of this might be found in the logs, by unexpected gaps in
> access log traffic, error messages in catalina.out etc.
>
>
> You could also configure jvm gc logging, (google for this), which may
> tell you something.
>
That sounds like this is worth looking into
>
> p
>
>
>
>
>> Martin
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
David kerber wrote:
> Is your tomcat set to roll the log files at midnight? Maybe there's
> something going on related to that?
no i don't think so - (but how do I control that - It would be cool to
use that). Its pretty much a standard Tomcat installation - with HTTPS
turned on and HTTP turned off.
My standard tomcat logs only change their filenames, when i restart tomcat.
>
>
> Pid wrote:
>> Martin Cavanagh wrote:
>>
>>
>>> just to to check - there is no hidden setting in Tomcat which says -
>>> shut me down at midnight sometimes for an inexplainable reason?
>>>
>>
>> Oh yeah, forgot about that one. Filip, Remy et al have a funny sense of
>> humour - they're always building crazy easter eggs into Tomcat.
>>
>> No, Martin, there's no secret scheduled shutdown setting.
>>
>> I've asked about the logs before, but I'll ask again...
>> What's in the logs immediately before the shutdown?
>>
>> You'll need to look in catalina.out, any app logs and the access log for
>> the app.
>>
>>
>> If you're using the default JVM settings, there's a chance that you
>> might not be running on the server JVM, so your app may have a limited
>> amount of memory at it's disposal (32Mb if memory serves). If it's
>> hanging for some reason (e.g. an app internal job at midnight?) would
>> VMWare shut it down as a bad/dead process?
>>
>> Evidence of this might be found in the logs, by unexpected gaps in
>> access log traffic, error messages in catalina.out etc.
>>
>>
>> You could also configure jvm gc logging, (google for this), which may
>> tell you something.
>>
>>
>> p
>>
>>
>>
>>
>>> Martin
>>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by David kerber <dc...@verizon.net>.
Is your tomcat set to roll the log files at midnight? Maybe there's
something going on related to that?
Pid wrote:
> Martin Cavanagh wrote:
>
>
>> just to to check - there is no hidden setting in Tomcat which says -
>> shut me down at midnight sometimes for an inexplainable reason?
>>
>
> Oh yeah, forgot about that one. Filip, Remy et al have a funny sense of
> humour - they're always building crazy easter eggs into Tomcat.
>
> No, Martin, there's no secret scheduled shutdown setting.
>
> I've asked about the logs before, but I'll ask again...
> What's in the logs immediately before the shutdown?
>
> You'll need to look in catalina.out, any app logs and the access log for
> the app.
>
>
> If you're using the default JVM settings, there's a chance that you
> might not be running on the server JVM, so your app may have a limited
> amount of memory at it's disposal (32Mb if memory serves). If it's
> hanging for some reason (e.g. an app internal job at midnight?) would
> VMWare shut it down as a bad/dead process?
>
> Evidence of this might be found in the logs, by unexpected gaps in
> access log traffic, error messages in catalina.out etc.
>
>
> You could also configure jvm gc logging, (google for this), which may
> tell you something.
>
>
> p
>
>
>
>
>> Martin
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Pid <p...@pidster.com>.
Martin Cavanagh wrote:
> just to to check - there is no hidden setting in Tomcat which says -
> shut me down at midnight sometimes for an inexplainable reason?
Oh yeah, forgot about that one. Filip, Remy et al have a funny sense of
humour - they're always building crazy easter eggs into Tomcat.
No, Martin, there's no secret scheduled shutdown setting.
I've asked about the logs before, but I'll ask again...
What's in the logs immediately before the shutdown?
You'll need to look in catalina.out, any app logs and the access log for
the app.
If you're using the default JVM settings, there's a chance that you
might not be running on the server JVM, so your app may have a limited
amount of memory at it's disposal (32Mb if memory serves). If it's
hanging for some reason (e.g. an app internal job at midnight?) would
VMWare shut it down as a bad/dead process?
Evidence of this might be found in the logs, by unexpected gaps in
access log traffic, error messages in catalina.out etc.
You could also configure jvm gc logging, (google for this), which may
tell you something.
p
> Martin
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Alexey Solofnenko <A....@mdl.com>.
InstallShield now has auto update feature too. Plus there is auto update
in antiviruses, Google Pack, other products. Also disk defragmenters may
want to reboot the machine to defragment system files. Sometimes they
log messages in EventLog.
Martin Cavanagh wrote:
> Thanks Alexey.
>
> Notifications only :(
>
> Keep the ideas coming guys!
>
> just to to check - there is no hidden setting in Tomcat which says -
> shut me down at midnight sometimes for an inexplainable reason?
>
> Martin
>
> Alexey Solofnenko wrote:
>> Maybe it is caused by automatic Windows Update. Did you check it?
>>
>> - Alexey.
>>
>> Martin Cavanagh wrote:
>>> Hi guys, I'm still having this problem.
>>>
>>> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
>>> and 26.09.
>>>
>>> We have VM Ware Server as the hardware - could this cause the problem?
>>>
>>> I have a firewall on the machine with only the HTTPS port open.
>>>
>>> In the config file there is the standard AJP port (8009) - what does
>>> this actually do?
>>>
>>> Hardware : VM Ware Server
>>> OS: Win 2003
>>> Tomcat Version: 5.5.23
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>> Martin
>>>
>>> David Smith wrote:
>>>> Huh?? The shutdown port explicitly binds to the localhost
>>>> interface. External clients cannot access it anyway. Easily
>>>> demonstrated with a netstat command.
>>>>
>>>> --David
>>>>
>>>>
>>>>
>>>> Martin Gainty wrote:
>>>>
>>>>> Hi Pid
>>>>>
>>>>> you're going to need a firewall if someone can telnet to your
>>>>> shutdown port
>>>>> (check server.xml for the exact port number)
>>>>>
>>>>> Martin--
>>>>> ----- Original Message -----
>>>>> From: "Pid" <p...@pidster.com>
>>>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>>>> Sent: Friday, September 21, 2007 7:19 AM
>>>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> What's immediately before the shutdown description in the logs?
>>>>>>
>>>>>> p
>>>>>>
>>>>>>
>>>>>>
>>>>>> Martin Cavanagh wrote:
>>>>>>
>>>>>>> Why would windows report it as crashing then?
>>>>>>>
>>>>>>> I know I didn't shut it down, I was sleeping, as I assume
>>>>>>> everyone else
>>>>>>> was who had access to the system......
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>> David Delbecq wrote:
>>>>>>>
>>>>>>>> According to your log it did not crash. It did shutdown
>>>>>>>> following the
>>>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>>>> suggest you investigate possibilities that a local service is
>>>>>>>> setup to
>>>>>>>> shutdown tomcat at midnight on the server.
>>>>>>>>
>>>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>>>> connector is
>>>>>>>>
>>>>> by
>>>>>
>>>>>
>>>>>>>> default accessible only on local machine.
>>>>>>>>
>>>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>>>> s'exprimait en
>>>>>>>> ces termes:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi everyone.
>>>>>>>>>
>>>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>>>
>>>>>>>>> The server is running on Windows 2003 Server with Java JRE
>>>>>>>>> 1.5.0_11
>>>>>>>>>
>>>>>>>>> It worked fine with my program for several hours. Then
>>>>>>>>> exactly at
>>>>>>>>> midnight it crashed.
>>>>>>>>>
>>>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist
>>>>>>>>> bereits 1
>>>>>>>>> Mal passiert. - Which translates to,
>>>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has
>>>>>>>>> happened once
>>>>>>>>> already.
>>>>>>>>>
>>>>>>>>> The catalina logs show
>>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>>> pause
>>>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>>>> INFO: Stopping service Catalina
>>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>>> destroy
>>>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>>>
>>>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>>>> see any
>>>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>>>> crashed?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> Martin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
--
------------------------------------------------------------------------
Alexey N. Solofnenko <http://trelony.cjb.net/>
Pleasant Hill, CA (GMT-8 usually)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
[OT] RE: Tomcat crash @ midnight - but why?
Posted by Peter Crowther <Pe...@melandra.com>.
> From: Andrew Miehs [mailto:andrew@2sheds.de]
> Oh - and you may want to have a serious talk with the cleaning lady,
> not that she unplugs the server for the vacuum cleaner.. ^^
Don't joke, it happened repeatedly to a box I used to manage in a
hospital. Even after we taped over the plug, writing "do not remove" on
it, she'd simply undo the tape, pull out the plug, vacuum away, and
replace the plug and tape. The same cleaner would routinely plug the
vacuum into the red power-conditioned emergency-equipment-only sockets
around the hospital...
- Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Andrew Miehs <an...@2sheds.de>.
Are you using Log4j in your application?
It has the option to do daily (midnight) rotates on log files...
Oh - and you may want to have a serious talk with the cleaning lady,
not that she unplugs the server for the vacuum cleaner.. ^^
Cheers
Andrew
On 26/09/2007, at 6:11 PM, Christopher Schultz wrote:
>
> Martin Cavanagh wrote:
>> just to to check - there is no hidden setting in Tomcat which says -
>> shut me down at midnight sometimes for an inexplainable reason?
>
> I think they removed that in 5.5.23, so you should be safe. It was fun
> while it lasted ;)
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin,
Martin Cavanagh wrote:
> just to to check - there is no hidden setting in Tomcat which says -
> shut me down at midnight sometimes for an inexplainable reason?
I think they removed that in 5.5.23, so you should be safe. It was fun
while it lasted ;)
- -chris
PS: Yes, this was a joke.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+oSl9CaO5/Lv0PARAmVwAJ4yv+fBzAFxhD4iW/RQZMFLDhtx7wCgws9o
wYQXysfkvrD1lnkoaLIVfYg=
=7IPW
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Thanks Alexey.
Notifications only :(
Keep the ideas coming guys!
just to to check - there is no hidden setting in Tomcat which says -
shut me down at midnight sometimes for an inexplainable reason?
Martin
Alexey Solofnenko wrote:
> Maybe it is caused by automatic Windows Update. Did you check it?
>
> - Alexey.
>
> Martin Cavanagh wrote:
>> Hi guys, I'm still having this problem.
>>
>> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
>> and 26.09.
>>
>> We have VM Ware Server as the hardware - could this cause the problem?
>>
>> I have a firewall on the machine with only the HTTPS port open.
>>
>> In the config file there is the standard AJP port (8009) - what does
>> this actually do?
>>
>> Hardware : VM Ware Server
>> OS: Win 2003
>> Tomcat Version: 5.5.23
>>
>> Any ideas?
>>
>> Thanks
>>
>> Martin
>>
>> David Smith wrote:
>>> Huh?? The shutdown port explicitly binds to the localhost
>>> interface. External clients cannot access it anyway. Easily
>>> demonstrated with a netstat command.
>>>
>>> --David
>>>
>>>
>>>
>>> Martin Gainty wrote:
>>>
>>>> Hi Pid
>>>>
>>>> you're going to need a firewall if someone can telnet to your
>>>> shutdown port
>>>> (check server.xml for the exact port number)
>>>>
>>>> Martin--
>>>> ----- Original Message -----
>>>> From: "Pid" <p...@pidster.com>
>>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>>> Sent: Friday, September 21, 2007 7:19 AM
>>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>>
>>>>
>>>>
>>>>
>>>>> What's immediately before the shutdown description in the logs?
>>>>>
>>>>> p
>>>>>
>>>>>
>>>>>
>>>>> Martin Cavanagh wrote:
>>>>>
>>>>>> Why would windows report it as crashing then?
>>>>>>
>>>>>> I know I didn't shut it down, I was sleeping, as I assume
>>>>>> everyone else
>>>>>> was who had access to the system......
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Martin
>>>>>>
>>>>>> David Delbecq wrote:
>>>>>>
>>>>>>> According to your log it did not crash. It did shutdown
>>>>>>> following the
>>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>>> suggest you investigate possibilities that a local service is
>>>>>>> setup to
>>>>>>> shutdown tomcat at midnight on the server.
>>>>>>>
>>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>>> connector is
>>>>>>>
>>>> by
>>>>
>>>>
>>>>>>> default accessible only on local machine.
>>>>>>>
>>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>>> s'exprimait en
>>>>>>> ces termes:
>>>>>>>
>>>>>>>
>>>>>>>> Hi everyone.
>>>>>>>>
>>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>>
>>>>>>>> The server is running on Windows 2003 Server with Java JRE
>>>>>>>> 1.5.0_11
>>>>>>>>
>>>>>>>> It worked fine with my program for several hours. Then exactly at
>>>>>>>> midnight it crashed.
>>>>>>>>
>>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist
>>>>>>>> bereits 1
>>>>>>>> Mal passiert. - Which translates to,
>>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has
>>>>>>>> happened once
>>>>>>>> already.
>>>>>>>>
>>>>>>>> The catalina logs show
>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>> pause
>>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>>> INFO: Stopping service Catalina
>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>> destroy
>>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>>
>>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>>> see any
>>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>>> crashed?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> Martin
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>>
>>
>>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Alexey Solofnenko <A....@mdl.com>.
Maybe it is caused by automatic Windows Update. Did you check it?
- Alexey.
Martin Cavanagh wrote:
> Hi guys, I'm still having this problem.
>
> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
> and 26.09.
>
> We have VM Ware Server as the hardware - could this cause the problem?
>
> I have a firewall on the machine with only the HTTPS port open.
>
> In the config file there is the standard AJP port (8009) - what does
> this actually do?
>
> Hardware : VM Ware Server
> OS: Win 2003
> Tomcat Version: 5.5.23
>
> Any ideas?
>
> Thanks
>
> Martin
>
> David Smith wrote:
>> Huh?? The shutdown port explicitly binds to the localhost
>> interface. External clients cannot access it anyway. Easily
>> demonstrated with a netstat command.
>>
>> --David
>>
>>
>>
>> Martin Gainty wrote:
>>
>>> Hi Pid
>>>
>>> you're going to need a firewall if someone can telnet to your
>>> shutdown port
>>> (check server.xml for the exact port number)
>>>
>>> Martin--
>>> ----- Original Message -----
>>> From: "Pid" <p...@pidster.com>
>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>> Sent: Friday, September 21, 2007 7:19 AM
>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>
>>>
>>>
>>>
>>>> What's immediately before the shutdown description in the logs?
>>>>
>>>> p
>>>>
>>>>
>>>>
>>>> Martin Cavanagh wrote:
>>>>
>>>>> Why would windows report it as crashing then?
>>>>>
>>>>> I know I didn't shut it down, I was sleeping, as I assume everyone
>>>>> else
>>>>> was who had access to the system......
>>>>>
>>>>> Thanks
>>>>>
>>>>> Martin
>>>>>
>>>>> David Delbecq wrote:
>>>>>
>>>>>> According to your log it did not crash. It did shutdown following
>>>>>> the
>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>> suggest you investigate possibilities that a local service is
>>>>>> setup to
>>>>>> shutdown tomcat at midnight on the server.
>>>>>>
>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>> connector is
>>>>>>
>>> by
>>>
>>>
>>>>>> default accessible only on local machine.
>>>>>>
>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>> s'exprimait en
>>>>>> ces termes:
>>>>>>
>>>>>>
>>>>>>> Hi everyone.
>>>>>>>
>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>
>>>>>>> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>>>>>>
>>>>>>> It worked fine with my program for several hours. Then exactly at
>>>>>>> midnight it crashed.
>>>>>>>
>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>>>>>>> Mal passiert. - Which translates to,
>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has happened
>>>>>>> once
>>>>>>> already.
>>>>>>>
>>>>>>> The catalina logs show
>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>> pause
>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>> INFO: Stopping service Catalina
>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>> destroy
>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>
>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>> see any
>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>> crashed?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>
>
--
------------------------------------------------------------------------
Alexey N. Solofnenko <http://trelony.cjb.net/>
Pleasant Hill, CA (GMT-8 usually)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Hi Frank
Franck Borel wrote:
> Hi Martin,
>
>> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
>> and 26.09.
>>
>> We have VM Ware Server as the hardware - could this cause the problem?
>
> What kind of network connection are you using? NAT or Bridge?
not sure and I don't have direct access to the host machine to check
this. Could this play a role? What should I be looking for. I would
have expected a Bridge...
>> I have a firewall on the machine with only the HTTPS port open.
>>
>> In the config file there is the standard AJP port (8009) - what does
>> this actually do?
>
> This is a connector, that is used to connect Apache with Tomcat. Are
> you using Apache with Tomcat? If yes look at the log file of your
> mod_jk (C:\apache2\logs\mod_jk.log).
Then the AJP port is harmless, Its a tomcat server which is working alone.
>
>> Hardware : VM Ware Server
>> OS: Win 2003
>> Tomcat Version: 5.5.23
>
>
>
> -- Franck
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Franck Borel <bo...@ub.uni-freiburg.de>.
Hi Martin,
> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09 and
> 26.09.
>
> We have VM Ware Server as the hardware - could this cause the problem?
What kind of network connection are you using? NAT or Bridge?
> I have a firewall on the machine with only the HTTPS port open.
>
> In the config file there is the standard AJP port (8009) - what does
> this actually do?
This is a connector, that is used to connect Apache with Tomcat. Are you using
Apache with Tomcat? If yes look at the log file of your mod_jk
(C:\apache2\logs\mod_jk.log).
> Hardware : VM Ware Server
> OS: Win 2003
> Tomcat Version: 5.5.23
-- Franck
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gabe,
Gabe Wong wrote:
> Sounds very much like a memory issue as echoed by others on the list.
I'm not so sure: he's getting what looks like a clean shutdown, not a VM
crash or OOME or anything like that.
If it were on Linux and he were running out of memory and the process
just disappeared, I would blame the OOM killer. I'm pretty sure that
when windows runs out of memory, Windows itself goes down. In any event,
the clean shutdown is very unexpected given all the other information we
have.
Martin, you don't have anything running in your webapp that monitors
memory usage and does a clean shutdown when memory is running low, do
you? (I imagine you would have mentioned that if you knew about it!)
> What is the Memory Heap size used by the JVM?
He said he's using the default, so the JVM is choosing the heap size for
him. He's probably getting something like a 64MB or 128MB heap.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+odl9CaO5/Lv0PARAocFAKCXWYMp1qj4XZeplgweHW+grUFw9ACffeYD
JM9eBAyqsQanFVlcGGQ6WtI=
=kfCs
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat crash @ midnight - but why?
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Gabe Wong [mailto:gabrielw@ngasi.com]
> Subject: Re: Tomcat crash @ midnight - but why?
>
> Sounds very much like a memory issue as echoed by others on the list.
I don't think so. Lack of RAM might cause performance problems due to
excessive paging, but it's not going to cause a shutdown. If there were
JVM heap issues, there would be OOME exceptions logged, and Tomcat would
not be going through a normal shutdown.
- 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 start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Gabe Wong <ga...@ngasi.com>.
Sounds very much like a memory issue as echoed by others on the list.
What is the Memory Heap size used by the JVM?
Martin Cavanagh wrote:
> Thanks Gabe.
>
> I've checked the Windows Scheduled Tasks - unfortunately they are empty.
>
> The VMWare instance has 656MB RAm.
>
> Tomcat logs are quite boring - they only indicate that the Tomcat is
> being shutdown
>
> The catalina logs show
> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-443
> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-443
> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>
> All other logs I posted 5 days ago and I don't want to repost.
>
> Thanks for everyones help
>
> Martin
>
> Gabe Wong wrote:
>> Check Windows Scheduled Tasks, to see what runs around that time.
>> Could be a resource issue. A background task or even a load spike
>> from a search bot. How much memory is allocated to the VMWare
>> instance? Also did you check the Tomcat logs?
>>
>> Martin Cavanagh wrote:
>>> Hi guys, I'm still having this problem.
>>>
>>> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
>>> and 26.09.
>>>
>>> We have VM Ware Server as the hardware - could this cause the problem?
>>>
>>> I have a firewall on the machine with only the HTTPS port open.
>>>
>>> In the config file there is the standard AJP port (8009) - what does
>>> this actually do?
>>>
>>> Hardware : VM Ware Server
>>> OS: Win 2003
>>> Tomcat Version: 5.5.23
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>> Martin
>>>
>>> David Smith wrote:
>>>> Huh?? The shutdown port explicitly binds to the localhost
>>>> interface. External clients cannot access it anyway. Easily
>>>> demonstrated with a netstat command.
>>>>
>>>> --David
>>>>
>>>>
>>>>
>>>> Martin Gainty wrote:
>>>>
>>>>> Hi Pid
>>>>>
>>>>> you're going to need a firewall if someone can telnet to your
>>>>> shutdown port
>>>>> (check server.xml for the exact port number)
>>>>>
>>>>> Martin--
>>>>> ----- Original Message -----
>>>>> From: "Pid" <p...@pidster.com>
>>>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>>>> Sent: Friday, September 21, 2007 7:19 AM
>>>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> What's immediately before the shutdown description in the logs?
>>>>>>
>>>>>> p
>>>>>>
>>>>>>
>>>>>>
>>>>>> Martin Cavanagh wrote:
>>>>>>
>>>>>>> Why would windows report it as crashing then?
>>>>>>>
>>>>>>> I know I didn't shut it down, I was sleeping, as I assume
>>>>>>> everyone else
>>>>>>> was who had access to the system......
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>> David Delbecq wrote:
>>>>>>>
>>>>>>>> According to your log it did not crash. It did shutdown
>>>>>>>> following the
>>>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>>>> suggest you investigate possibilities that a local service is
>>>>>>>> setup to
>>>>>>>> shutdown tomcat at midnight on the server.
>>>>>>>>
>>>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>>>> connector is
>>>>>>>>
>>>>> by
>>>>>
>>>>>
>>>>>>>> default accessible only on local machine.
>>>>>>>>
>>>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>>>> s'exprimait en
>>>>>>>> ces termes:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi everyone.
>>>>>>>>>
>>>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>>>
>>>>>>>>> The server is running on Windows 2003 Server with Java JRE
>>>>>>>>> 1.5.0_11
>>>>>>>>>
>>>>>>>>> It worked fine with my program for several hours. Then
>>>>>>>>> exactly at
>>>>>>>>> midnight it crashed.
>>>>>>>>>
>>>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist
>>>>>>>>> bereits 1
>>>>>>>>> Mal passiert. - Which translates to,
>>>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has
>>>>>>>>> happened once
>>>>>>>>> already.
>>>>>>>>>
>>>>>>>>> The catalina logs show
>>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>>> pause
>>>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>>>> INFO: Stopping service Catalina
>>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>>> destroy
>>>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>>>
>>>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>>>> see any
>>>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>>>> crashed?
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> Martin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
--
Regards
Gabe Wong
Private JVM JAVA Hosting Automation
http://www.ngasi.com
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Thanks Gabe.
I've checked the Windows Scheduled Tasks - unfortunately they are empty.
The VMWare instance has 656MB RAm.
Tomcat logs are quite boring - they only indicate that the Tomcat is
being shutdown
The catalina logs show
21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-443
21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
INFO: Pausing Coyote AJP/1.3 on ajp-8009
21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-443
21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
INFO: Stopping Coyote AJP/1.3 on ajp-8009
All other logs I posted 5 days ago and I don't want to repost.
Thanks for everyones help
Martin
Gabe Wong wrote:
> Check Windows Scheduled Tasks, to see what runs around that time.
> Could be a resource issue. A background task or even a load spike
> from a search bot. How much memory is allocated to the VMWare
> instance? Also did you check the Tomcat logs?
>
> Martin Cavanagh wrote:
>> Hi guys, I'm still having this problem.
>>
>> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
>> and 26.09.
>>
>> We have VM Ware Server as the hardware - could this cause the problem?
>>
>> I have a firewall on the machine with only the HTTPS port open.
>>
>> In the config file there is the standard AJP port (8009) - what does
>> this actually do?
>>
>> Hardware : VM Ware Server
>> OS: Win 2003
>> Tomcat Version: 5.5.23
>>
>> Any ideas?
>>
>> Thanks
>>
>> Martin
>>
>> David Smith wrote:
>>> Huh?? The shutdown port explicitly binds to the localhost
>>> interface. External clients cannot access it anyway. Easily
>>> demonstrated with a netstat command.
>>>
>>> --David
>>>
>>>
>>>
>>> Martin Gainty wrote:
>>>
>>>> Hi Pid
>>>>
>>>> you're going to need a firewall if someone can telnet to your
>>>> shutdown port
>>>> (check server.xml for the exact port number)
>>>>
>>>> Martin--
>>>> ----- Original Message -----
>>>> From: "Pid" <p...@pidster.com>
>>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>>> Sent: Friday, September 21, 2007 7:19 AM
>>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>>
>>>>
>>>>
>>>>
>>>>> What's immediately before the shutdown description in the logs?
>>>>>
>>>>> p
>>>>>
>>>>>
>>>>>
>>>>> Martin Cavanagh wrote:
>>>>>
>>>>>> Why would windows report it as crashing then?
>>>>>>
>>>>>> I know I didn't shut it down, I was sleeping, as I assume
>>>>>> everyone else
>>>>>> was who had access to the system......
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Martin
>>>>>>
>>>>>> David Delbecq wrote:
>>>>>>
>>>>>>> According to your log it did not crash. It did shutdown
>>>>>>> following the
>>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>>> suggest you investigate possibilities that a local service is
>>>>>>> setup to
>>>>>>> shutdown tomcat at midnight on the server.
>>>>>>>
>>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>>> connector is
>>>>>>>
>>>> by
>>>>
>>>>
>>>>>>> default accessible only on local machine.
>>>>>>>
>>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>>> s'exprimait en
>>>>>>> ces termes:
>>>>>>>
>>>>>>>
>>>>>>>> Hi everyone.
>>>>>>>>
>>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>>
>>>>>>>> The server is running on Windows 2003 Server with Java JRE
>>>>>>>> 1.5.0_11
>>>>>>>>
>>>>>>>> It worked fine with my program for several hours. Then exactly at
>>>>>>>> midnight it crashed.
>>>>>>>>
>>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist
>>>>>>>> bereits 1
>>>>>>>> Mal passiert. - Which translates to,
>>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has
>>>>>>>> happened once
>>>>>>>> already.
>>>>>>>>
>>>>>>>> The catalina logs show
>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>> pause
>>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>>> INFO: Stopping service Catalina
>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>>> destroy
>>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>>
>>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>>> see any
>>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>>> crashed?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> Martin
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>>
>>
>>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Gabe Wong <ga...@ngasi.com>.
Check Windows Scheduled Tasks, to see what runs around that time. Could
be a resource issue. A background task or even a load spike
from a search bot. How much memory is allocated to the VMWare instance?
Also did you check the Tomcat logs?
Martin Cavanagh wrote:
> Hi guys, I'm still having this problem.
>
> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
> and 26.09.
>
> We have VM Ware Server as the hardware - could this cause the problem?
>
> I have a firewall on the machine with only the HTTPS port open.
>
> In the config file there is the standard AJP port (8009) - what does
> this actually do?
>
> Hardware : VM Ware Server
> OS: Win 2003
> Tomcat Version: 5.5.23
>
> Any ideas?
>
> Thanks
>
> Martin
>
> David Smith wrote:
>> Huh?? The shutdown port explicitly binds to the localhost
>> interface. External clients cannot access it anyway. Easily
>> demonstrated with a netstat command.
>>
>> --David
>>
>>
>>
>> Martin Gainty wrote:
>>
>>> Hi Pid
>>>
>>> you're going to need a firewall if someone can telnet to your
>>> shutdown port
>>> (check server.xml for the exact port number)
>>>
>>> Martin--
>>> ----- Original Message -----
>>> From: "Pid" <p...@pidster.com>
>>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>>> Sent: Friday, September 21, 2007 7:19 AM
>>> Subject: Re: Tomcat crash @ midnight - but why?
>>>
>>>
>>>
>>>
>>>> What's immediately before the shutdown description in the logs?
>>>>
>>>> p
>>>>
>>>>
>>>>
>>>> Martin Cavanagh wrote:
>>>>
>>>>> Why would windows report it as crashing then?
>>>>>
>>>>> I know I didn't shut it down, I was sleeping, as I assume everyone
>>>>> else
>>>>> was who had access to the system......
>>>>>
>>>>> Thanks
>>>>>
>>>>> Martin
>>>>>
>>>>> David Delbecq wrote:
>>>>>
>>>>>> According to your log it did not crash. It did shutdown following
>>>>>> the
>>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>>> suggest you investigate possibilities that a local service is
>>>>>> setup to
>>>>>> shutdown tomcat at midnight on the server.
>>>>>>
>>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>>> SHUTDOWN string at the admin connector (8005 here). This
>>>>>> connector is
>>>>>>
>>> by
>>>
>>>
>>>>>> default accessible only on local machine.
>>>>>>
>>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh
>>>>>> s'exprimait en
>>>>>> ces termes:
>>>>>>
>>>>>>
>>>>>>> Hi everyone.
>>>>>>>
>>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>>
>>>>>>> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>>>>>>
>>>>>>> It worked fine with my program for several hours. Then exactly at
>>>>>>> midnight it crashed.
>>>>>>>
>>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>>>>>>> Mal passiert. - Which translates to,
>>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has happened
>>>>>>> once
>>>>>>> already.
>>>>>>>
>>>>>>> The catalina logs show
>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
>>>>>>> pause
>>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>>> INFO: Stopping service Catalina
>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>>> destroy
>>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>>
>>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>>> see any
>>>>>>> other logs regarding this. How do I find out why my Tomcat
>>>>>>> crashed?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>
>
--
Regards
Gabe Wong
Private JVM JAVA Hosting Automation
http://www.ngasi.com
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Thanks for your answers
Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin,
>
> Martin Cavanagh wrote:
>
>> Hi guys, I'm still having this problem.
>>
>> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09 and
>> 26.09.
>>
>
> Strange. What is the uptime of your operating system? Perhaps it's being
> rebooted every night?
>
No its definitely not being restarted automatically. I've had the same
session (Remote Desktop) running to the server for 4 months...
>
>> We have VM Ware Server as the hardware - could this cause the problem?
>>
>
> Probably not, but if there's some kind of warm backup going on where the
> OS is suspended for the backup, you may be running into trouble. VMware
> allows the OS to respond to events (such as SUSPEND and RESUME), and
> it's possible that your VM is rigged to shut down some services on
> SUSPEND. I doubt that very much, but it's certainly possible.
>
I don't have direct access to the VM, but I'll have this checked into.
>
>> In the config file there is the standard AJP port (8009) - what does
>> this actually do?
>>
>
> If you are using a web server along with Tomcat, the AJP connector
> allows the two to speak to one another. If you are using Tomcat all by
> itself, you can safely disable this connector.
>
Ok - I'll disable this. There is no other Web Server involved
> - -chris
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFG+mfU9CaO5/Lv0PARArvAAJ9xPomWXYlk7a+91+xGUYhQEG653ACgrqVB
> YHzpLj93/bqEDS4Tom0j5V4=
> =Np9e
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin,
Martin Cavanagh wrote:
> Hi guys, I'm still having this problem.
>
> Its happened 3 times now. Always at exactly midnight. 21.09, 25.09 and
> 26.09.
Strange. What is the uptime of your operating system? Perhaps it's being
rebooted every night?
> We have VM Ware Server as the hardware - could this cause the problem?
Probably not, but if there's some kind of warm backup going on where the
OS is suspended for the backup, you may be running into trouble. VMware
allows the OS to respond to events (such as SUSPEND and RESUME), and
it's possible that your VM is rigged to shut down some services on
SUSPEND. I doubt that very much, but it's certainly possible.
> In the config file there is the standard AJP port (8009) - what does
> this actually do?
If you are using a web server along with Tomcat, the AJP connector
allows the two to speak to one another. If you are using Tomcat all by
itself, you can safely disable this connector.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+mfU9CaO5/Lv0PARArvAAJ9xPomWXYlk7a+91+xGUYhQEG653ACgrqVB
YHzpLj93/bqEDS4Tom0j5V4=
=Np9e
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Hi guys, I'm still having this problem.
Its happened 3 times now. Always at exactly midnight. 21.09, 25.09 and
26.09.
We have VM Ware Server as the hardware - could this cause the problem?
I have a firewall on the machine with only the HTTPS port open.
In the config file there is the standard AJP port (8009) - what does
this actually do?
Hardware : VM Ware Server
OS: Win 2003
Tomcat Version: 5.5.23
Any ideas?
Thanks
Martin
David Smith wrote:
> Huh?? The shutdown port explicitly binds to the localhost interface.
> External clients cannot access it anyway. Easily demonstrated with a
> netstat command.
>
> --David
>
>
>
> Martin Gainty wrote:
>
>> Hi Pid
>>
>> you're going to need a firewall if someone can telnet to your
>> shutdown port
>> (check server.xml for the exact port number)
>>
>> Martin--
>> ----- Original Message -----
>> From: "Pid" <p...@pidster.com>
>> To: "Tomcat Users List" <us...@tomcat.apache.org>
>> Sent: Friday, September 21, 2007 7:19 AM
>> Subject: Re: Tomcat crash @ midnight - but why?
>>
>>
>>
>>
>>> What's immediately before the shutdown description in the logs?
>>>
>>> p
>>>
>>>
>>>
>>> Martin Cavanagh wrote:
>>>
>>>> Why would windows report it as crashing then?
>>>>
>>>> I know I didn't shut it down, I was sleeping, as I assume everyone
>>>> else
>>>> was who had access to the system......
>>>>
>>>> Thanks
>>>>
>>>> Martin
>>>>
>>>> David Delbecq wrote:
>>>>
>>>>> According to your log it did not crash. It did shutdown following the
>>>>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>> suggest you investigate possibilities that a local service is
>>>>> setup to
>>>>> shutdown tomcat at midnight on the server.
>>>>>
>>>>> The tomcat shutdown procedure is started when tomcat receive the
>>>>> SHUTDOWN string at the admin connector (8005 here). This connector is
>>>>>
>> by
>>
>>
>>>>> default accessible only on local machine.
>>>>>
>>>>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh s'exprimait en
>>>>> ces termes:
>>>>>
>>>>>
>>>>>> Hi everyone.
>>>>>>
>>>>>> Yesterday I started a 2nd Apache Server for my program. It was
>>>>>> installed several months ago. Version 5.5.0.23.
>>>>>>
>>>>>> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>>>>>
>>>>>> It worked fine with my program for several hours. Then exactly at
>>>>>> midnight it crashed.
>>>>>>
>>>>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>>>>>> Mal passiert. - Which translates to,
>>>>>> Service "Apache Tomcat" stopped unexpectedly. This has happened
>>>>>> once
>>>>>> already.
>>>>>>
>>>>>> The catalina logs show
>>>>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
>>>>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>> INFO: Stopping service Catalina
>>>>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
>>>>>> destroy
>>>>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>>
>>>>>> Which unfortunately isn't really particularly useful. I can't
>>>>>> see any
>>>>>> other logs regarding this. How do I find out why my Tomcat crashed?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Martin
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by David Smith <dn...@cornell.edu>.
Huh?? The shutdown port explicitly binds to the localhost interface.
External clients cannot access it anyway. Easily demonstrated with a
netstat command.
--David
Martin Gainty wrote:
>Hi Pid
>
>you're going to need a firewall if someone can telnet to your shutdown port
>(check server.xml for the exact port number)
>
>Martin--
>----- Original Message -----
>From: "Pid" <p...@pidster.com>
>To: "Tomcat Users List" <us...@tomcat.apache.org>
>Sent: Friday, September 21, 2007 7:19 AM
>Subject: Re: Tomcat crash @ midnight - but why?
>
>
>
>
>>What's immediately before the shutdown description in the logs?
>>
>>p
>>
>>
>>
>>Martin Cavanagh wrote:
>>
>>
>>>Why would windows report it as crashing then?
>>>
>>>I know I didn't shut it down, I was sleeping, as I assume everyone else
>>>was who had access to the system......
>>>
>>>Thanks
>>>
>>>Martin
>>>
>>>David Delbecq wrote:
>>>
>>>
>>>>According to your log it did not crash. It did shutdown following the
>>>>shutdown procedure (which can be executed by bin\shutdown.bat). I
>>>>suggest you investigate possibilities that a local service is setup to
>>>>shutdown tomcat at midnight on the server.
>>>>
>>>>The tomcat shutdown procedure is started when tomcat receive the
>>>>SHUTDOWN string at the admin connector (8005 here). This connector is
>>>>
>>>>
>by
>
>
>>>>default accessible only on local machine.
>>>>
>>>>En l'instant précis du 21/09/07 09:21, Martin Cavanagh s'exprimait en
>>>>ces termes:
>>>>
>>>>
>>>>
>>>>>Hi everyone.
>>>>>
>>>>>Yesterday I started a 2nd Apache Server for my program. It was
>>>>>installed several months ago. Version 5.5.0.23.
>>>>>
>>>>>The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>>>>
>>>>>It worked fine with my program for several hours. Then exactly at
>>>>>midnight it crashed.
>>>>>
>>>>>Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>>>>>Mal passiert. - Which translates to,
>>>>>Service "Apache Tomcat" stopped unexpectedly. This has happened once
>>>>>already.
>>>>>
>>>>>The catalina logs show
>>>>>21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
>>>>>INFO: Pausing Coyote HTTP/1.1 on http-443
>>>>>21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>>>>INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>>>>21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>>>>INFO: Stopping service Catalina
>>>>>21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
>>>>>INFO: Stopping Coyote HTTP/1.1 on http-443
>>>>>21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>>>>INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>>>
>>>>>Which unfortunately isn't really particularly useful. I can't see any
>>>>>other logs regarding this. How do I find out why my Tomcat crashed?
>>>>>
>>>>>Thanks
>>>>>
>>>>>Martin
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To start a new topic, e-mail: users@tomcat.apache.org
>>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To start a new topic, e-mail: users@tomcat.apache.org
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Pid <p...@pidster.com>.
What's immediately before the shutdown description in the logs?
p
Martin Cavanagh wrote:
> Why would windows report it as crashing then?
>
> I know I didn't shut it down, I was sleeping, as I assume everyone else
> was who had access to the system......
>
> Thanks
>
> Martin
>
> David Delbecq wrote:
>> According to your log it did not crash. It did shutdown following the
>> shutdown procedure (which can be executed by bin\shutdown.bat). I
>> suggest you investigate possibilities that a local service is setup to
>> shutdown tomcat at midnight on the server.
>>
>> The tomcat shutdown procedure is started when tomcat receive the
>> SHUTDOWN string at the admin connector (8005 here). This connector is by
>> default accessible only on local machine.
>>
>> En l'instant précis du 21/09/07 09:21, Martin Cavanagh s'exprimait en
>> ces termes:
>>
>>> Hi everyone.
>>>
>>> Yesterday I started a 2nd Apache Server for my program. It was
>>> installed several months ago. Version 5.5.0.23.
>>>
>>> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>>
>>> It worked fine with my program for several hours. Then exactly at
>>> midnight it crashed.
>>>
>>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>>> Mal passiert. - Which translates to,
>>> Service "Apache Tomcat" stopped unexpectedly. This has happened once
>>> already.
>>>
>>> The catalina logs show
>>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
>>> INFO: Pausing Coyote HTTP/1.1 on http-443
>>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>>> INFO: Stopping service Catalina
>>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
>>> INFO: Stopping Coyote HTTP/1.1 on http-443
>>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>>
>>> Which unfortunately isn't really particularly useful. I can't see any
>>> other logs regarding this. How do I find out why my Tomcat crashed?
>>>
>>> Thanks
>>>
>>> Martin
>>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by Martin Cavanagh <ca...@con-sense-group.com>.
Why would windows report it as crashing then?
I know I didn't shut it down, I was sleeping, as I assume everyone else
was who had access to the system......
Thanks
Martin
David Delbecq wrote:
> According to your log it did not crash. It did shutdown following the
> shutdown procedure (which can be executed by bin\shutdown.bat). I
> suggest you investigate possibilities that a local service is setup to
> shutdown tomcat at midnight on the server.
>
> The tomcat shutdown procedure is started when tomcat receive the
> SHUTDOWN string at the admin connector (8005 here). This connector is by
> default accessible only on local machine.
>
> En l'instant précis du 21/09/07 09:21, Martin Cavanagh s'exprimait en
> ces termes:
>
>> Hi everyone.
>>
>> Yesterday I started a 2nd Apache Server for my program. It was
>> installed several months ago. Version 5.5.0.23.
>>
>> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>>
>> It worked fine with my program for several hours. Then exactly at
>> midnight it crashed.
>>
>> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
>> Mal passiert. - Which translates to,
>> Service "Apache Tomcat" stopped unexpectedly. This has happened once
>> already.
>>
>> The catalina logs show
>> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
>> INFO: Pausing Coyote HTTP/1.1 on http-443
>> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
>> INFO: Pausing Coyote AJP/1.3 on ajp-8009
>> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
>> INFO: Stopping service Catalina
>> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
>> INFO: Stopping Coyote HTTP/1.1 on http-443
>> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
>> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>>
>> Which unfortunately isn't really particularly useful. I can't see any
>> other logs regarding this. How do I find out why my Tomcat crashed?
>>
>> Thanks
>>
>> Martin
>>
>
>
>
--
Con-Sense-GmbH
__
_Martin Cavanagh_
Tel.: +49541 800 83 0
Fax: +49541 800 83 99
cavanagh@con-sense-group.com <ma...@con-sense-group.com>
Con-Sense GmbH
Neuer Graben 25
49074 Osnabrück
www.con-sense-group.com <http://www.con-sense-group.com>
Geschäftsführer Eckhard Schulz
Amtsgericht Hildesheim HRB 3341
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat crash @ midnight - but why?
Posted by David Delbecq <de...@oma.be>.
According to your log it did not crash. It did shutdown following the
shutdown procedure (which can be executed by bin\shutdown.bat). I
suggest you investigate possibilities that a local service is setup to
shutdown tomcat at midnight on the server.
The tomcat shutdown procedure is started when tomcat receive the
SHUTDOWN string at the admin connector (8005 here). This connector is by
default accessible only on local machine.
En l'instant précis du 21/09/07 09:21, Martin Cavanagh s'exprimait en
ces termes:
> Hi everyone.
>
> Yesterday I started a 2nd Apache Server for my program. It was
> installed several months ago. Version 5.5.0.23.
>
> The server is running on Windows 2003 Server with Java JRE 1.5.0_11
>
> It worked fine with my program for several hours. Then exactly at
> midnight it crashed.
>
> Dienst "Apache Tomcat" wurde unerwartet beendet. Dies ist bereits 1
> Mal passiert. - Which translates to,
> Service "Apache Tomcat" stopped unexpectedly. This has happened once
> already.
>
> The catalina logs show
> 21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol pause
> INFO: Pausing Coyote HTTP/1.1 on http-443
> 21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
> INFO: Pausing Coyote AJP/1.3 on ajp-8009
> 21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
> INFO: Stopping service Catalina
> 21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol destroy
> INFO: Stopping Coyote HTTP/1.1 on http-443
> 21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
> INFO: Stopping Coyote AJP/1.3 on ajp-8009
>
> Which unfortunately isn't really particularly useful. I can't see any
> other logs regarding this. How do I find out why my Tomcat crashed?
>
> Thanks
>
> Martin
--
http://www.noooxml.org/
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org