-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running gRPC with Tomcat is problematic #2996
Comments
Tomcat compatibility problems were expected to be resolved with netty-tcnative 2.0. We had trouble upgrading to the last couple of Netty releases, but it seems 4.1.11 may work out. Upgrading to 4.1.11 would allow using netty-tcnative 2.0 and thus hopefully resolve the problem you're experiencing. This is being done in #2973. This seems a duplicate of #2936 at this point, so closing. But if for some reason it's not, feel free to comment more and we can reopen. |
@joaoandremartins It looks like #2973 has been merged. Can you try again? |
Running google-cloud-pubsub version 0.17.2-alpha, still seeing the same issue. |
New gRPC version which will include the fix was not released yet, and when it will be the google-cloud-pubsub will have to upgrade to it to see any changes. |
I ran into this issue trying to use the Google Cloud PubSub API from a Spring Boot app, using Tomcat by default. The issue is explained here.
Jetty ALPN/NPN has not been properly configured
A workaround is basically to use Jetty instead of Tomcat. However, ideally this should work with Tomcat too.
After reading around a bit, I tried pulling in the netty-tcnative-boringssl-static dependency, and org.eclipse.jetty.npn.npn-api since the code appears to be checking for a
org.eclipse.jetty.npn.NextProtoNego
class in the classpath, to no avail.What can be done to make this work with Tomcat as well?
What version of gRPC are you using?
grpc-netty 1.2.0
What JVM are you using (
java -version
)?1.8.0_121
The text was updated successfully, but these errors were encountered: