Ping() there but it did not have any effect.
We do not use compression extension.
Thanks for the test! :-)
-Harri
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: 7. maaliskuuta 2017 23:58
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Tomcat
StateException(e);
}
}
}
private class SemaphoreSendHandler implements SendHandler {
private final Semaphore semaphore;
private SemaphoreSendHandler(Semaphore semaphore) {
this.semaphore = semaphore;
}
Hello, we have a problem that Tomcat WebSocket does not always send
asynchronous messages. This problem is random, and it has been reproduced in
Tomcat 8.5.6 and 8.5.11. Synchronized operations work fine, and also the
asynchronous operations work except in one special case. When there is a big
Hello,
the following lists Tomcat versions 8.5.0 - 8.5.12, does it mean that the
problem has been fixed in 8.5.13 and later?
https://nvd.nist.gov/vuln/detail/CVE-2017-5651
I assume that it has been fixed, as 8.5.13 readme has:
* [Fix:]
:
public static Object getCatalina() {
if (daemon != null) {
return daemon.catalinaDaemon;
}
return null;
}
But I have a feeling that there must be some better way of doing this.
-Harri
-Original Message-
From: Pesonen, Harri [mailto:harri.peso
Hello, what would be the best way to find out if any of Tomcat connectors have
failed to initialize at startup?
They could fail for many reasons, like when the port is already in use, or
keystore is missing etc.
Now Tomcat prints the error in log, but I would like to find out
programmatically
Hello, if one servlet fails to initialize, meaning that
ServletContextListener.contextInitialized() throws exception, then Tomcat still
starts (but without the servlet).
I found out that if servlet calls System.exit(1), then Tomcat dies. Is this the
only way to make this happen?
This does not
rty.
Maybe I did it wrong:
-Harri
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: 21. kesäkuuta 2017 17:28
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: How to stop Tomcat if servlet fails to initialize
On 21/06/17 13:33, Pesonen, Harri wrote
8.5.13. Maybe it is supported in 9 only.
-Harri
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: 22. kesäkuuta 2017 13:46
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: How to stop Tomcat if servlet fails to initialize
On 22/06/17 11:44, Pesonen,
It is possible to use Windows certificate store like this:
You have to enter keyAlias that matches the subject of the certificate in
Windows user's personal certificates. Then you don't need to enter password at
all.
-Harri
-Original Message-
From: John Palmer
Hello, there is this problem in 8.5.20, that is already fixed for the coming
8.5.21:
https://bz.apache.org/bugzilla/show_bug.cgi?id=61451
What is the latest version that does not have this problem? Is it 8.5.16? If I
understand correctly, this problem was introduced in 8.5.18 (not released):
I have implemented a Tomcat vault as well, it is basically a simplified version
of
https://github.com/web-servers/tomcat-vault
My version does not have keystore, so it is much easier to use.
It would be great if Tomcat would have this functionality built-in somehow.
-Harri
-Original
12 matches
Mail list logo
