On 09/04/2012 09:18, Ofer Israeli wrote:
On 08/04/2012 23:14, Stefan Mayr ste...@mayr-stefan.de wrote:
Am 08.04.2012 18:41, schrieb Ofer Israeli:
2012/4/6 Pidp...@pidster.com:
On 05/04/2012 22:17, Ofer Israeli wrote:
Y
On 5 באפר 2012, at 18:58, Konstantin
Kolinkoknst.koli...@gmail.com
On 08/04/2012 23:14, Stefan Mayr ste...@mayr-stefan.de wrote:
Am 08.04.2012 18:41, schrieb Ofer Israeli:
2012/4/6 Pidp...@pidster.com:
On 05/04/2012 22:17, Ofer Israeli wrote:
Y
On 5 באפר 2012, at 18:58, Konstantin
Kolinkoknst.koli...@gmail.com
wrote:
2012/4/5 Ofer
2012/4/6 Konstantin Kolinko knst.koli...@gmail.com:
2012/4/6 Ofer Israeli of...@checkpoint.com:
Hi Konstantin,
I agree regarding the OOM bringing TC to a state where it must be
restored, but my point remains: if there is code that handles catching this
exception and terminating the
2012/4/6 Pid p...@pidster.com:
On 05/04/2012 22:17, Ofer Israeli wrote:
Y
On 5 באפר 2012, at 18:58, Konstantin Kolinko knst.koli...@gmail.com
wrote:
2012/4/5 Ofer Israeli of...@checkpoint.com:
Mark Thomas wrote:
On 04/04/2012 17:02, Ofer Israeli wrote:
Once you have an OOME all
Am 08.04.2012 18:41, schrieb Ofer Israeli:
2012/4/6 Pidp...@pidster.com:
On 05/04/2012 22:17, Ofer Israeli wrote:
Y
On 5 באפר 2012, at 18:58, Konstantin Kolinkoknst.koli...@gmail.com
wrote:
2012/4/5 Ofer Israeliof...@checkpoint.com:
Mark Thomas wrote:
On 04/04/2012 17:02, Ofer Israeli
Mark Thomas wrote:
On 04/04/2012 17:02, Ofer Israeli wrote:
Hi all,
We have recently witnessed a strange situation. Our Tomcat (6.0.35)
listens on 2 ports: 8080 and 8009, handling HTTP and AJP
respectively. At some point in time we found that Apache is replying
HTTP 503s to all clients
2012/4/5 Ofer Israeli of...@checkpoint.com:
Mark Thomas wrote:
On 04/04/2012 17:02, Ofer Israeli wrote:
Once you have an OOME all bets are off. The JVM needs to be restarted.
There is no guarantee of reliable operation after an OOME.
Mark
Hi Mark,
I agree that there in such a situation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 4/5/12 11:57 AM, Konstantin Kolinko wrote:
1. Tomcat does not start JVM thus it cannot restart it.
You need some external tool or script or admin to perform
monitoring and (re)starts.
Asking Tomcat to restart itself after OOME
2012/4/5 Christopher Schultz ch...@christopherschultz.net:
On 4/5/12 11:57 AM, Konstantin Kolinko wrote:
1. Tomcat does not start JVM thus it cannot restart it.
You need some external tool or script or admin to perform
monitoring and (re)starts.
Asking Tomcat to restart itself after OOME
-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: Thursday, April 05, 2012 10:18 AM
To: Tomcat Users List
Subject: Re: Bug in Tomcat AJP Connector?
2012/4/5 Christopher Schultz ch...@christopherschultz.net:
On 4/5/12 11:57 AM, Konstantin Kolinko
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 4/5/12 12:18 PM, Konstantin Kolinko wrote:
2012/4/5 Christopher Schultz ch...@christopherschultz.net:
On 4/5/12 11:57 AM, Konstantin Kolinko wrote:
1. Tomcat does not start JVM thus it cannot restart it.
You need some external
Y
On 5 באפר 2012, at 18:58, Konstantin Kolinko knst.koli...@gmail.com wrote:
2012/4/5 Ofer Israeli of...@checkpoint.com:
Mark Thomas wrote:
On 04/04/2012 17:02, Ofer Israeli wrote:
Once you have an OOME all bets are off. The JVM needs to be restarted.
There is no guarantee of reliable
2012/4/6 Ofer Israeli of...@checkpoint.com:
Hi Konstantin,
I agree regarding the OOM bringing TC to a state where it must be restored,
but my point remains: if there is code that handles catching this exception
and terminating the thread, why not terminate gracefully by closing the
On 05/04/2012 22:17, Ofer Israeli wrote:
Y
On 5 באפר 2012, at 18:58, Konstantin Kolinko knst.koli...@gmail.com wrote:
2012/4/5 Ofer Israeli of...@checkpoint.com:
Mark Thomas wrote:
On 04/04/2012 17:02, Ofer Israeli wrote:
Once you have an OOME all bets are off. The JVM needs to be
On 04/04/2012 17:02, Ofer Israeli wrote:
Hi all,
We have recently witnessed a strange situation. Our Tomcat (6.0.35)
listens on 2 ports: 8080 and 8009, handling HTTP and AJP
respectively. At some point in time we found that Apache is replying
HTTP 503s to all clients and a look at netstat
15 matches
Mail list logo