Netty conflicts of gRPC and Lagom
See original GitHub issueI would like to use both Google Cloud Java library and Lagom. Both gRPC (dependency of Google Cloud Java) and Lagom use Netty but not the same version which cause conflicts and error while booting up:
Caused by: java.lang.NoClassDefFoundError: Could not initialize class io.netty.handler.ssl.OpenSslEngine
Lagom Version (1.2.x / 1.3.x / etc)
Everything works fine on Lagom 1.4.-M3 but problem persists on all other gPRC.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Lagom gRPC Example
I am running Lagom scala gRPC example ... failed: Connection refused\n\tat io.grpc.netty.shaded.io.netty.channel.unix.Errors.
Read more >Armeria vs Lagom Framework | What are the differences?
It is your go-to microservice framework for any situation. You can build any type of microservice leveraging your favorite technologies, including gRPC, Thrift, ......
Read more >Grpc netty handler libraries are conflicting with OpenJSSE
I'm facing a classCastException issue while using grpc netty handlers along with OpenJSSE. We are working on gRPC calls (which use Netty ......
Read more >kamon-io/Kamon - Gitter
Hi Team, I am trying to integrate the Kamon into the Lagom Microservice. At the time of server startup, I am seeing the...
Read more >Top 10 Microservices frameworks for 2022 | by Anil Kurmi
Vert.x gRPC is a module that will align the programming style of Google gRPC ... It's built on top of Netty and uses...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@idoshamun thank you for the example project… that’s a big help!
The configuration error is happening because there is still a definition for
lagom-gcp-demo-stream-impl
inbuild.sbt
, but the files have been removed. You can comment out or delete that definition to fix the error.Also, as a testing note for anyone else trying to reproduce. You need to specify a Google Cloud project ID for the service to start. Running
GOOGLE_CLOUD_PROJECT=test sbt runAll
was enough to get me past that error.Once it’s running, open another terminal and run
curl http://localhost:9000/api/hello
. This succeeds, but also logs a stack trace in therunAll
console with the Netty error.Great to hear @idoshamun. I’ll close this issue, because I don’t think there’s any good way to prevent this from happening at the framework level.