java.lang.ClassNotFoundException: org/eclipse/jetty/alpn/ALPN #2740
Comments
|
|
|
That didn't work. I have excluded netty-common from vertx-core and included netty-common-4.1.16.Final and the issue is still there. Here's my dependency tree output |
|
All of the netty versions need to be consistent, not just netty-common. |
|
That didn't do it either, here's the outcome of mvn dependency:tree |
|
Ok the versions all seem consistent now. Could you try calling https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/google-cloud-util/google-cloud-compat-checker/src/main/java/com/google/cloud/compatchecker/GoogleCloudCompatChecker.java from your code and see what it outputs? |
|
The first time I ran it I got the following exception: I see that On the second run I manually added: to my |
|
@ejona86 any pointers on how to fix this? ( |
|
I got this fixed by adding the following dependency |
|
Now I'm very curious about which inconsistency I missed. Do you mind providing your final dependency tree? |
|
Not at all, here you go, I have also added: Here's the dependency tree |
|
@fmatar have you tried 0.30 and/or 0.31 version? I just started using 0.32-alpha (and 0.32-beta) and stuck with this problem. Considering to downgrade and see whether it helps to temporarily mitigate this issue while it is fixed in 0.32 |
|
@n0mer I had the same issue as well with 0.30 and 0.31 |
neozwu
added
the
type: question
|
HTH - "canonical" related issue: grpc/grpc-java#3025 |
|
@garrettjonesgoogle @fmatar in my case problem was in the OS itself. Once i changed OS from |
|
In mine the fix was to add an extra jar to the I use Clojure with lein so the bit I needed to add to the project.clj was: Don't really know allot about the bootclasspath but from my reading this is really something that is dependent on the java version and ssl management you have on your setup. Also I think this might be the underlying reason behind this and #2398 Hope this helps someone |
|
As a final follow up, I want to recommend 0.33.0 or later, which bumps the grpc dependency to 1.9; this version of grpc shades tcnative, so there shouldn't be tcnative conflicts any more. @n0mer yes, alpine is known not to work (this is noted in the main README). |
|
It turns out that we needed to switch from depending on grpc-netty to grpc-netty-shaded, which we haven't done yet. I am going to reopen this issue to track the re-fix. |
|
I've been using #2813 as a canonical issue for the netty version conflict problem. Let's move further discussions there instead. |
|
Can anyone please help me with this. Application error message: 16:27:39,275 ERROR [org.hyperledger.fabric.sdk.Channel] (ServerService Thread Pool -- 146) Jetty ALPN/NPN has not been properly configured.: java.lang.IllegalArgumentException: Jetty ALPN/NPN has not been properly configured. My maven dependency tree +- org.slf4j:slf4j-api:jar:1.7.3:compile My Compat checker result: OS details: |
|
I see you're using io.netty:netty-tcnative-boringssl-static:jar:2.0.5.Final:compile and io.grpc:grpc-netty:jar:1.7.0:compile. I suggest using tcnative 2.0.6.Final with grpc 1.7. See the table in https://github.com/grpc/grpc-java/blob/master/SECURITY.md#netty |
|
@ejona86 thanks for your suggestion, but no luck ! throws the same exception :( |
|
@praveenatsolartis, it seems you're having a different problem than discussed in this issue. Please open a separate issue to avoid confusing this issue further. |
My team has built a very thing wrapper around the spanner java driver and we have ran a number of tests successfully.
An issue came up when we tried to integrate the layer we built with vert.x (http://vertx.io)
An exception is occurring on the following code block:
The following exception is being thrown:
The dependency tree is as follows:
The environment I'm developing on is the following:
OS: MacOSX
JDK Version: 1.8.0_152
Spanner Driver version: 0.32.0-beta
I believe this is a gRPC error. I have tried excluding dependencies such as grpc-netty but that hasn't sorted the issue yet.
The text was updated successfully, but these errors were encountered: