. It definitely can affect your
SSL if you're using JSSE+JCE...
George
-Original Message-
From: Peter Robbins [mailto:peter.robb...@jamfsoftware.com]
Sent: Monday, July 25, 2016 3:25 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: NullPointerExceptions from Coyote ov
2016-07-25 23:25 GMT+02:00 Peter Robbins :
> > If you also have tomcat-native installed…
> No tomcat-native in any environment I saw, but I’ll make sure we check on
> that config.
>
> We’re not knowingly plugging Bouncy Castle into the Tomcat SSL mix at all.
> We
> If you also have tomcat-native installed…
No tomcat-native in any environment I saw, but I’ll make sure we check on that
config.
We’re not knowingly plugging Bouncy Castle into the Tomcat SSL mix at all. We
only use it in application logic after registering it with
Security.addProvider() in
2016-07-22 22:16 GMT+02:00 Peter Robbins :
> Just to update, we were able to work around this by changing our
> server.xml connector config from:
>
> protocol="HTTP/1.1"
> to:
> protocol="org.apache.coyote.http11.Http11Nio2Protocol"
>
Just to update, we were able to work around this by changing our server.xml
connector config from:
protocol="HTTP/1.1"
to:
protocol="org.apache.coyote.http11.Http11Nio2Protocol"
sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation"
Somewhere deep within
That’s good to know. In the short term I think we’re going to revert back to
the 8.0.x branch and see if we can find put together a more isolated repro war
to try to nail this thing down. Thanks for your help!
Peter
On 7/20/16, 7:40 AM, "Rémy Maucherat" wrote:
2016-07-20
2016-07-20 13:59 GMT+02:00 Peter Robbins :
> Ok I'll see if I can dig BC out of the application and have it actually
> start up to try to see if that's the case.
>
> You're saying there are known compatibility issues with Tomcat NIO https
> if you register another
Ok I'll see if I can dig BC out of the application and have it actually start
up to try to see if that's the case.
You're saying there are known compatibility issues with Tomcat NIO https if you
register another j2ee security provider? The errors we're seeing don't seem
crypto related apart
2016-07-20 2:54 GMT+02:00 Peter Robbins :
> Without JCE or BC? Both are pretty critical for core functionality and
> didn't cause any issues until 8.5.3 entered the mix. Any known issues there
> I should be aware of?
>
You still need to test something. You don't
Without JCE or BC? Both are pretty critical for core functionality and didn't
cause any issues until 8.5.3 entered the mix. Any known issues there I should
be aware of?
Peter
On Jul 19, 2016 6:24 PM, R?my Maucherat wrote:
2016-07-19 23:51 GMT+02:00 Peter Robbins
2016-07-19 23:51 GMT+02:00 Peter Robbins :
> Hi there,
>
> JCE, Bouncy Castle 1.48
>
> Maybe try without that first.
Rémy
Hi there,
Versions: Tomcat 8.5.3, JDK 1.8 + JCE, Bouncy Castle 1.48, Ubuntu 14.04 &
16.04,Windows 2012 R2
I’m running into an issue where we are getting NullPointerExceptions from the
Coyote connector in a Tomcat web application.
This is an existing, stable web application that was recently
12 matches
Mail list logo