-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add a README section on supported runtime environments & workarounds #2039
Comments
@saturnism Can you be more specific what did not work well in Tomcat or Netty? |
I encountered this issue today with the Cloud Pub/Sub client library. With Spring Boot, I got the error "Jetty ALPN/NPN has not been properly configured" at runtime. These were my dependencies:
The code worked without modification after I made Spring Boot use Jetty instead of Tomcat.
|
Note has been added in the main README. We still need to add links to Supported environments on each module. |
Yes, I just started using the PubSub API within a Spring Boot app and I'm getting this too. After reading a bit on this, I tried importing the netty-tcnative-boringssl-static dependency, as well as org.eclipse.jetty.npn.npn-api (since the code throwing this error is checking for |
@jabubake Can we close the issue now since the notes has been added? |
Ideally, we would want gRPC to work with Tomcat seamlessly too. |
Seems like a fix for this is coming out on a next release of the grpc-java library. |
Yesterday I have encountered the same problem with spring boot and pubsub lib. Even when I'm using Jetty I'm still getting "Jetty ALPN/NPN has not been properly configured." |
We have upgraded to grpc 1.4 which removes the conflict with Tomcat. Since the underlying issue should be fixed, I'm going to close this out. |
gRPC currently don't work well in embedded Tomcat or embedded Netty envs. Document what we know works and don't work and work arounds.
Specifically, if someone uses the client lib in Spring Boot, they need to exclude tomcat starter and use jetty starter instead.
Corollary to this, in each module's README, refer to this section for supported envs.
The text was updated successfully, but these errors were encountered: