I love it when a memory leak bites the dust .. it's a great feeling to
extend process life.
Fixed one yesterday in a capture/encode buffer of my mp3 streamer.
Kudos, Mark!
:)
John
On 1/12/19, i...@flyingfischer.ch wrote:
> Am 11.01.19 um 18:23 schrieb Mark Thomas:
>> Found it.
>>
>> The leak
Am 11.01.19 um 18:23 schrieb Mark Thomas:
> Found it.
>
> The leak impacted NIO and NIO2 when used with OpenSSL.
>
> The bug is in Tomcat Native. I have a fix that I am currently testing.
> That fix should be in the next Tomcat Native release.
>
> For those interested in the technical details, Tomc
On 11/01/2019 21:07, Christopher Schultz wrote:
> Mark,
>
> On 1/11/19 13:50, Mark Thomas wrote:
>> On 11/01/2019 17:31, Christopher Schultz wrote:
>>> Mark,
>>>
>>> On 1/11/19 12:23, Mark Thomas wrote:
On 10/01/2019 19:55, Mark Thomas wrote:
>>>
>>>
> I've just tracked down one lea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/11/19 13:50, Mark Thomas wrote:
> On 11/01/2019 17:31, Christopher Schultz wrote:
>> Mark,
>>
>> On 1/11/19 12:23, Mark Thomas wrote:
>>> On 10/01/2019 19:55, Mark Thomas wrote:
>>
>>>
>>
I've just tracked down one leak although
On 11/01/2019 17:31, Christopher Schultz wrote:
> Mark,
>
> On 1/11/19 12:23, Mark Thomas wrote:
>> On 10/01/2019 19:55, Mark Thomas wrote:
>
>>
>
>>> I've just tracked down one leak although it is a relatively small
>>> one. Next steps are to fix that leak and then find the next one.
>>> And t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/11/19 12:23, Mark Thomas wrote:
> On 10/01/2019 19:55, Mark Thomas wrote:
>
>
>
>> I've just tracked down one leak although it is a relatively small
>> one. Next steps are to fix that leak and then find the next one.
>> And then repeat
On 10/01/2019 19:55, Mark Thomas wrote:
> I've just tracked down one leak although it is a relatively small one.
> Next steps are to fix that leak and then find the next one. And then repeat.
Found it.
The leak impacted NIO and NIO2 when used with OpenSSL.
The bug is in Tomcat Native. I have
On 10/01/2019 17:31, john.e.gr...@wellsfargo.com wrote:
> The first troubleshooting step should be to take a heap dump and analyze it
> with a tool like Eclipse MAT.
If you read the entire thread you will see that I have already done
that. The Java Heap (in fact all the JVM managed pools) were
Mason, Mark, etc...
> -Original Message-
> From: Mark Thomas
> Sent: Thursday, January 10, 2019 10:45 AM
> To: users@tomcat.apache.org
> Subject: Re: Tomcat memory growth while using TLS
>
> On 09/01/2019 14:24, Mark Thomas wrote:
> > On 09/01/20
On 09/01/2019 14:24, Mark Thomas wrote:
> On 09/01/2019 10:14, Mark Thomas wrote:
>> It may be you are seeing the same thing. Or you may have found a memory
>> leak. The next step would be to use a profiler to see where the memory
>> is being used.
>
> Using NIO + OpenSSL with the settings from
On 09/01/2019 10:14, Mark Thomas wrote:
> On 08/01/2019 23:51, Mason Meier wrote:
>> Hello,
>>
>> I'm running Tomcat-8.5 with TLS and I've noticed substantial memory growth
>> with requests over time, to the point that if I run Tomcat in Docker and
>> make constant requests to it, Docker will kill
Am 09.01.19 um 11:14 schrieb Mark Thomas:
> On 08/01/2019 23:51, Mason Meier wrote:
>> Hello,
>>
>> I'm running Tomcat-8.5 with TLS and I've noticed substantial memory growth
>> with requests over time, to the point that if I run Tomcat in Docker and
>> make constant requests to it, Docker will kil
On 08/01/2019 23:51, Mason Meier wrote:
> Hello,
>
> I'm running Tomcat-8.5 with TLS and I've noticed substantial memory growth
> with requests over time, to the point that if I run Tomcat in Docker and
> make constant requests to it, Docker will kill the container due to
> excessive memory utiliz
Hello,
I'm running Tomcat-8.5 with TLS and I've noticed substantial memory growth
with requests over time, to the point that if I run Tomcat in Docker and
make constant requests to it, Docker will kill the container due to
excessive memory utilization. The problem occurs with standalone Tomcat as
14 matches
Mail list logo
