Christopher,
No, I don't need to log THAT failure. But I do need to log handshake failures
where the failure to connect was a server-side decision. So (apparently) I do
need to log cases like a handshake failure in case both sides couldn't agree on
a cipher, as detailed in my question. As m
Hello Mark,
Please let me disagree with you. I have connected JVisualVM to Tomcat JVM,
run the test with 10,000 connections, performed several explicit GCs and
made a heap dump. All 10,000 WsSessions are in heap. They are referenced as
following:
this
<- wsSession - class:
org.apache.tomcat.w
Chris,
Now this is taking a weird direction…
> Am 30.07.2019 um 16:57 schrieb Christopher Schultz
> mailto:ch...@christopherschultz.net>>:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Peter,
>
> On 7/30/19 05:19, logo wrote:
>> Hi Chris,
>>
>> I am also trying to figure this ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joseph,
On 7/29/19 13:55, Joseph Dornisch wrote:
>> Joseph,
>>
>> On 7/25/19 11:53, Joseph Dornisch wrote:
>>> Hello,
>>>
>>> I have a CRL configured in my tomcat server configuration. If
>>> I update it and want to have Tomcat refresh it, I can l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 7/29/19 17:45, Mark Boon wrote:
> Apparently for compliance reasons we're required to log any failed
> connection attempt. So I'd like to know if and how I can get
> Tomcat to emit such information.
I'd try to get some clarification on tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Krishna,
On 7/30/19 06:29, కృష్ణ చైతన్య wrote:
> Is there a plan to add support for Native Memory Tracking in Apache
> Common’s jsvc?
There is no need to add support.
C:\Program Files\Apache Tomcat 9.0.22> SET
JvmArgs=XX:NativeMemoryTracking=detai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Peter,
On 7/30/19 05:19, logo wrote:
> Hi Chris,
>
> I am also trying to figure this out and get to the same error.
>
>> Am 25.07.2019 um 17:53 schrieb Joseph Dornisch
>> :
>>
>> Hello,
>>
>> I have a CRL configured in my tomcat server configura
On 30/07/2019 05:48, Kirill Ilyukhin wrote:
> Hello Mark,
>
> Please see the test case and Tomcat JVM heap dump screenshot attached.
> For sake of simplicity I do Thread.sleep() in client code instead of
> reading bytes from server.
That test case does not demonstrate a memory leak in either Tom
> Hi,
>
> Is there a plan to add support for Native Memory Tracking in Apache Common’s
> jsvc?
>
> Regards,
> Krishna Chaitanya.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: use
Hi Chris,
I am also trying to figure this out and get to the same error.
> Am 25.07.2019 um 17:53 schrieb Joseph Dornisch :
>
> Hello,
>
> I have a CRL configured in my tomcat server configuration. If I update it
> and want to have Tomcat refresh it, I can login into
> https://127.0.0.1/mana
On 29/07/2019 22:45, Mark Boon wrote:
> We're using Tomcat 8.5 + Java 8.
>
> When I do something like openssl s_client -cipher ECDHE-RSA-NULL-SHA
> -connect :443
> (where obviously ECDHE-RSA-NULL-SHA is not specified in my cipher list on the
> Tomcat server) the message on the client side is
>
11 matches
Mail list logo