On 18/01/2013 14:11, Konstantin Preißer wrote:
> Hi Mark,
>
>>> If you set the following system property:
>>> org.apache.catalina.connector.RECYCLE_FACADES
>>>
>>> to true (e.g. in setenv.[bat|sh]) and your application is retaining
>>> references you should start to see NPEs and the stack trace sh
Hi Mark,
> > If you set the following system property:
> > org.apache.catalina.connector.RECYCLE_FACADES
> >
> > to true (e.g. in setenv.[bat|sh]) and your application is retaining
> > references you should start to see NPEs and the stack trace should
> point
> > to where the problem is.
> >
> > I
Hi,
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Thursday, January 17, 2013 1:11 PM
>
> On 17/01/2013 11:07, Steve Mactaggart wrote:
> > Hi All,
> >
> > I have been hunting a BufferOverflowException on our production system
for
> > the last while, and initial
On 17/01/2013 11:07, Steve Mactaggart wrote:
> Hi All,
>
> I have been hunting a BufferOverflowException on our production system for
> the last while, and initially thought this was resolved by issue 53119, we
> have subsequently upgraded to 7.0.32 and have still seen the issues.
>
> Reading thr
Hi All,
I have been hunting a BufferOverflowException on our production system for
the last while, and initially thought this was resolved by issue 53119, we
have subsequently upgraded to 7.0.32 and have still seen the issues.
Reading through the mailing list archive it seems I am not the only on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 10/31/2011 12:19 PM, Konstantin Kolinko wrote:
> 2011/10/31 Christopher Schultz :
>>
>> PS Is there anything to be done about connector state after an
>> OOME? Chuck contends that OOMEs aren't certain death for an
>> application and th
2011/10/31 Christopher Schultz :
>
> PS Is there anything to be done about connector state after an OOME?
> Chuck contends that OOMEs aren't certain death for an application and
> that recovery is possible.
The problem is that with OOME you do not know what exactly remained in
the broken state.
G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
On 10/31/2011 9:53 AM, Christopher Schultz wrote:
> I've only seen it once so far since switching-over to the NIO AJP
> connector a few months back, but I figured I'd report it since I
> saw it.
I'm sure this was a fluke. After playing with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
I've only seen it once so far since switching-over to the NIO AJP
connector a few months back, but I figured I'd report it since I saw
it. I'll see if I can reproduce it if possible. I'm using a standard,
vanilla synchronized request.
Configurat
