-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 5/17/13 5:36 AM, Mark Thomas wrote:
> On 17/05/2013 09:28, Michael-O wrote:
>> Hi folks,
>>
>> there's now a follow-up on the issue [1]. Recap:
>> JreMemoryLeakPreventionListener reported that my webapp has
>> spawned OracleTimeoutPollingT
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Follow-up: Possible false-postive with
> JreMemoryLeakPreventionListener
> and Tomcat's JDBC Pool and OracleTimeoutPollingThread
> While I haven't exactly implemented my own JVM or an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 5/23/13 12:01 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: Follow-up: Possible false-postive with
>> JreMemoryLeakPreventionListener and Tomc
Am 2013-05-21 20:38, schrieb Mark Thomas:
On 21/05/2013 19:01, Michael-O wrote:
Mark,
I did receive an answer to the issue, citing your findings.
See verbatim copy below:
Hi Michael,
I received the following update from our developer:
*
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Follow-up: Possible false-postive with
> JreMemoryLeakPreventionListener
> and Tomcat's JDBC Pool and OracleTimeoutPollingThread
> Thanks for the pedantry: I was in fact ignoring the diff
Possible false-postive with
>>> JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
>>> OracleTimeoutPollingThread
>
>>> I suspect that the DriverManager will always be loaded by the
>>> boot ClassLoader, since the default-dispatch for Cl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
On 5/22/13 1:42 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: Follow-up: Possible false-postive with
>> JreMemoryLeakPreventionListener and Tomc
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Follow-up: Possible false-postive with
> JreMemoryLeakPreventionListener
> and Tomcat's JDBC Pool and OracleTimeoutPollingThread
> I suspect that the DriverManager will always be loaded by th
On May 22, 2013, at 11:35 AM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Nick,
>
> On 5/22/13 10:18 AM, Nick Williams wrote:
>>
>> On May 22, 2013, at 9:09 AM, Christopher Schultz wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> Ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick,
On 5/22/13 10:18 AM, Nick Williams wrote:
>
> On May 22, 2013, at 9:09 AM, Christopher Schultz wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Mark,
>>
>> On 5/21/13 2:38 PM, Mark Thomas wrote:
>>> On 21/05/2013 19:01, Mi
On May 22, 2013, at 9:09 AM, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Mark,
>
> On 5/21/13 2:38 PM, Mark Thomas wrote:
>> On 21/05/2013 19:01, Michael-O wrote:
>>> Mark,
>>>
>>> I did receive an answer to the issue, citing your findings. See
>>> verbat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 5/21/13 2:38 PM, Mark Thomas wrote:
> On 21/05/2013 19:01, Michael-O wrote:
>> Mark,
>>
>> I did receive an answer to the issue, citing your findings. See
>> verbatim copy below:
>>
>> Hi Michael,
>>
>> I received the following update fr
On 21/05/2013 19:47, Michael-O wrote:
> Am 2013-05-21 20:38, schrieb Mark Thomas:
>>> Seems like they understood the problem. But I do doubt that this is a
>>> fixed size moemory leak.
>>
>> I think the point they are trying to make is that it is only the first
>> instance of the web application to
Am 2013-05-21 20:38, schrieb Mark Thomas:
Seems like they understood the problem. But I do doubt that this is a
fixed size moemory leak.
I think the point they are trying to make is that it is only the first
instance of the web application to be unloaded that will be pinned in
memory. Subsequen
On 21/05/2013 19:01, Michael-O wrote:
> Mark,
>
> I did receive an answer to the issue, citing your findings.
> See verbatim copy below:
>
> Hi Michael,
>
> I received the following update from our developer:
>
> **
> The theoretical probl
e false-postive with
JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
OracleTimeoutPollingThread
On 17/05/2013 09:28, Michael-O wrote:
Hi folks,
there's now a follow-up on the issue [1].
Recap: JreMemoryLeakPreventionListener reported that my webapp has spawned
OracleTimeoutPoll
On 17/05/2013 15:34, Jeffrey Janner wrote:
> Michael and Mark - I happened to be reviewing how Oracle handles
> QueryTimeout yesterday on an unrelated issue and came across a
> passage in the JDBC Developers Guide (11g) that covered this
> Monitoring Thread (page E-3). My reading of it was that Or
> > -Original Message-
> > From: Mark Thomas [mailto:ma...@apache.org]
> > Sent: Friday, May 17, 2013 7:26 AM
> > To: Tomcat Users List
> > Subject: Re: Follow-up: Possible false-postive with
> > JreMemoryLeakPreventionListener and Tomcat's JDB
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Friday, May 17, 2013 7:26 AM
> To: Tomcat Users List
> Subject: Re: Follow-up: Possible false-postive with
> JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
> OracleTimeoutPollin
hr
> >> Von: "Mark Thomas"
> >> An: "Tomcat Users List"
> >> Betreff: Re: Follow-up: Possible false-postive with
> >> JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
> >> OracleTimeoutPollingThread
>
> Betreff: Re: Follow-up: Possible false-postive with
>> JreMemoryLeakPreventionListener and Tomcat's JDBC Pool and
>> OracleTimeoutPollingThread
>>
>> On 17/05/2013 09:28, Michael-O wrote:
>>> Hi folks,
>>>
>>> there's now a follow-up on the issue [1].
>>> R
Hi Mark,
thanks again for the detailed answer, details inline.
> Gesendet: Freitag, 17. Mai 2013 um 11:36 Uhr
> Von: "Mark Thomas"
> An: "Tomcat Users List"
> Betreff: Re: Follow-up: Possible false-postive with
> JreMemoryLeakPrevention
On 17/05/2013 09:28, Michael-O wrote:
> Hi folks,
>
> there's now a follow-up on the issue [1].
> Recap: JreMemoryLeakPreventionListener reported that my webapp has spawned
> OracleTimeoutPollingThread because I have set a QueryTimeout in the JDBC Pool.
> Mark Thomas noted that this is likely a b
Hi folks,
there's now a follow-up on the issue [1].
Recap: JreMemoryLeakPreventionListener reported that my webapp has spawned
OracleTimeoutPollingThread because I have set a QueryTimeout in the JDBC Pool.
Mark Thomas noted that this is likely a bug in the driver. I have taken action
and created
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/7/13 4:33 PM, Michael-O wrote:
> Am 2013-05-07 17:20, schrieb Christopher Schultz:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Michael,
>>
>> On 5/7/13 6:43 AM, Michael-O wrote:
Von: "Mark Thomas" On 07/05/2013 10:
Hello Christopher,
Am 2013-05-07 17:20, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/7/13 6:43 AM, Michael-O wrote:
Von: "Mark Thomas" On 07/05/2013 10:25,
Michael-O wrote:
Von: "Mark Thomas" On 07/05/2013 09:16,
Michael-O wrote:
Hi folks,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/7/13 6:43 AM, Michael-O wrote:
>> Von: "Mark Thomas" On 07/05/2013 10:25,
>> Michael-O wrote:
>>>
Von: "Mark Thomas" On 07/05/2013 09:16,
Michael-O wrote:
> Hi folks,
>
> I recently enabled a QueryTimeoutInte
> Von: "Mark Thomas"
> On 07/05/2013 10:25, Michael-O wrote:
> >
> >> Von: "Mark Thomas" On 07/05/2013 09:16,
> >> Michael-O wrote:
> >>> Hi folks,
> >>>
> >>> I recently enabled a QueryTimeoutInterceptor with queryTimeout of
> >>> 60 seconds in a JDBC Pool data source (7.0.37). When the app wa
> Von: "Mark Thomas"
> On 07/05/2013 10:25, Michael-O wrote:
> >
> >> Von: "Mark Thomas" On 07/05/2013 09:16,
> >> Michael-O wrote:
> >>> Hi folks,
> >>>
> >>> I recently enabled a QueryTimeoutInterceptor with queryTimeout of
> >>> 60 seconds in a JDBC Pool data source (7.0.37). When the app wa
On 07/05/2013 10:25, Michael-O wrote:
>
>> Von: "Mark Thomas" On 07/05/2013 09:16,
>> Michael-O wrote:
>>> Hi folks,
>>>
>>> I recently enabled a QueryTimeoutInterceptor with queryTimeout of
>>> 60 seconds in a JDBC Pool data source (7.0.37). When the app was
>>> shut down, Tomcat said: "The web
> Von: "Mark Thomas"
> On 07/05/2013 09:16, Michael-O wrote:
> > Hi folks,
> >
> > I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60
> > seconds in a JDBC Pool data source (7.0.37). When the app was shut down,
> > Tomcat said: "The web application [/...] appears to have star
On 07/05/2013 09:16, Michael-O wrote:
> Hi folks,
>
> I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60 seconds
> in a JDBC Pool data source (7.0.37). When the app was shut down, Tomcat said:
> "The web application [/...] appears to have started a thread named
> [OracleTimeou
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60 seconds in
a JDBC Pool data source (7.0.37). When the app was shut down, Tomcat said: "The
web application [/...] appears to have started a thread named
[OracleTimeoutPollingThread] but has failed to stop it..."
We
33 matches
Mail list logo
