[
https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490383#comment-17490383
]
Ben Roling commented on STORM-3817:
-----------------------------------
[~rzo1] I got past it by mimicking the build configuration I saw in your travis
link. First I tried matching my maven version to the 2.6.3 there, which didn't
help. Then I tried matching my Java version to 1.8.0_242. Mistakenly I first
tried to match that to an Oracle JDK version and they have 1.8.0_241 but not
1.8.0_242. Anyway, that version still produced the error. Then, finally I
found and used Open JDK 1.8.0_242 and got a successful build.
I'm curious what the difference is between the Open JDK and Oracle JDK versions
that causes this.
> Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
> --------------------------------------------
>
> Key: STORM-3817
> URL: https://issues.apache.org/jira/browse/STORM-3817
> Project: Apache Storm
> Issue Type: Dependency upgrade
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Richard Zowalla
> Priority: Major
> Fix For: 2.4.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Is there any possibility to upgrade the [shaded zookeeper version
> |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64]
> from 3.4.14 to a newer version? Or are there any reasons for not doing an
> upgrade right now?
> I am doing some testing with Storm in a Java 17 environment and it looks like
> I am suffering from this Zookeeper specific issue present in 3.4.14:
> https://issues.apache.org/jira/browse/ZOOKEEPER-3779
> If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x
> UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an
> option.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
