Beware Jon,
> Am 08.03.2023 um 07:56 schrieb jonmcalexan...@wellsfargo.com.invalid
> :
>
> Fwiw, this is happening in an outbound connection originated by a springboot
> app hosted in Tomcat. Any known issues with this and handshake issues?
>
Then the tomcat sslHostConfig does not matter at
Fwiw, this is happening in an outbound connection originated by a springboot
app hosted in Tomcat. Any known issues with this and handshake issues?
Thanks,
Sent with BlackBerry Work (www.blackberry.com)
From: jonmcalexan...@wellsfargo.com.INVALID
Sent: Mar 4,
Hi,
I am encountering an issue validating my application database connectivity, it
throws java.sql.SQLException: The url cannot be null upon validation.
The application is developed using Avaya’s Orchestration designer (Eclipse) and
database validation works until 9.0.70.
I hope someone
Hi Mark Thomas and Tomcat Team,
We have a strange issue with Tomcat 9.0.72. All 204 response does not
complete in firefox. It works in the Chrome browser. If we downgrade
the tomcat
version is less than .72. Everything works on all browsers.
Dear Mesrs. Thomas, Schultz, et al.:
Changing it to "org.apache.coyote.http11.Http11NioProtocol" did the
trick. The Tomcat 9 server launched, on our cloud Midrange box, and both
it and the webapp contexts we have running seem to be working. It will,
of course, require a bit more exercise
James,
On 3/7/23 03:35, Mark Thomas wrote:
On 06/03/2023 23:58, James H. H. Lampert wrote:
On 03/03/2023 17:44, I wrote:
Ok, another question: will Tomcat 9 accept a "legacy" connector
definition in the form as shown below?
protocol="org.apache.coyote.http11.Http11Protocol"
I think your protocol line needs to include "Nio" or "apr", depending on which
one you use:
protocol="org.apache.coyote.http11.Http11NioProtocol"
or
protocol="org.apache.coyote.http11.Http11AprProtocol"
see documentation here https://tomcat.apache.org/tomcat-9.0-doc/ssl-howto.html
On 06/03/2023 23:58, James H. H. Lampert wrote:
On 03/03/2023 17:44, I wrote:
Ok, another question: will Tomcat 9 accept a "legacy" connector
definition in the form as shown below?
protocol="org.apache.coyote.http11.Http11Protocol" maxThreads="150"
SSLEnabled="true" scheme="https"
