On 08/04/2012 23:14, Stefan Mayr wrote:
> Am 08.04.2012 18:41, schrieb Ofer Israeli:
> > 2012/4/6 Pid:
> >> On 05/04/2012 22:17, Ofer Israeli wrote:
> >>> Y
> >>>
> >>> On 5 באפר 2012, at 18:58, "Konstantin
> >>> Kolinko&quo
2012/4/6 Pid :
> On 05/04/2012 22:17, Ofer Israeli wrote:
> > Y
> >
> > On 5 באפר 2012, at 18:58, "Konstantin Kolinko"
> wrote:
> >
> >> 2012/4/5 Ofer Israeli :
> >>> Mark Thomas wrote:
> >>>> On 04/04/2012 17:02, Ofer
2012/4/6 Konstantin Kolinko :
> 2012/4/6 Ofer Israeli :
> > 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, w
Y
On 5 באפר 2012, at 18:58, "Konstantin Kolinko" wrote:
> 2012/4/5 Ofer Israeli :
>> 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.
>>> Th
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 A
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 showed that indeed Apache could not communic
Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ofer,
>
> On 2/27/12 6:11 AM, Ofer Israeli wrote:
>> Christopher Schultz wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>>
>>> Ofer,
>>>
>&
Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ofer,
>
> On 2/23/12 1:57 PM, Ofer Israeli wrote:
>> Felix Schumacher wrote:
>>> Am 23.02.2012 19:32, schrieb Ofer Israeli:
>>>> Caldarale, Charles R wrote:
>>>&
Felix Schumacher wrote:
> Am 23.02.2012 19:50, schrieb Ofer Israeli:
>> Felix Schumacher wrote:
>>> Am 23.02.2012 19:32, schrieb Ofer Israeli:
>>>> Caldarale, Charles R wrote:
>>>>>> From: Ofer Israeli [mailto:of...@checkpoint.com]
>>>>&
Felix Schumacher wrote:
> Am 23.02.2012 19:32, schrieb Ofer Israeli:
>> Caldarale, Charles R wrote:
>>>> From: Caldarale, Charles R
>>>> Subject: RE: Tomcat with mod_jk becomes irresponsive after working
>>>> for awhile
>>>
>>>> Y
Felix Schumacher wrote:
> Am 23.02.2012 19:32, schrieb Ofer Israeli:
>> Caldarale, Charles R wrote:
>>>> From: Ofer Israeli [mailto:of...@checkpoint.com]
>>>> Subject: RE: Tomcat with mod_jk becomes irresponsive after working
>>>> for awhile
>&g
Caldarale, Charles R wrote:
>> From: Caldarale, Charles R
>> Subject: RE: Tomcat with mod_jk becomes irresponsive after working
>> for awhile
>
>> You might want to take a thread dump of Tomcat and see just what is
>> going on.
>
> Also look in the Tomcat logs (there are several) to see if errors
Caldarale, Charles R wrote:
>> From: Ofer Israeli [mailto:of...@checkpoint.com]
>> Subject: RE: Tomcat with mod_jk becomes irresponsive after working
>> for awhile
>
>> I am in the situation where the server is giving 503s for all
>> incoming requests, so I
André Warnier wrote:
> Ofer Israeli wrote:
>> All,
>>
>> I have a deployment on Windows 2003 Server using Apache 2.2.16,
>> Tomcat 5.5.30 and mod_jk 1.2.31. Apache and Tomcat reside on the
>> same machine. The communication is fine for days / weeks, but at
>>
All,
I have a deployment on Windows 2003 Server using Apache 2.2.16, Tomcat 5.5.30
and mod_jk 1.2.31. Apache and Tomcat reside on the same machine. The
communication is fine for days / weeks, but at some point all requests to the
server (to Apache) that use mod_jk return HTTP 503.
The error tha
15 matches
Mail list logo
