[jira] [Resolved] (STORM-3914) Several External Modules as not being tested for JDK 11
[ https://issues.apache.org/jira/browse/STORM-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3914. Fix Version/s: 2.6.0 Resolution: Fixed > Several External Modules as not being tested for JDK 11 > --- > > Key: STORM-3914 > URL: https://issues.apache.org/jira/browse/STORM-3914 > Project: Apache Storm > Issue Type: Improvement > Components: build >Reporter: Bipin Prasad >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Github actions for JDK11 "external" does not include several external > modules, however they are included for JDK8 build. > Change the JDK11 github actions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (STORM-3943) May I ask that you can configure a user password to log in for security verification when visiting storm ui. Check the official website security verification is not ver
[ https://issues.apache.org/jira/browse/STORM-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754821#comment-17754821 ] zfy68 commented on STORM-3943: -- [~alekstorm] > May I ask that you can configure a user password to log in for security > verification when visiting storm ui. Check the official website security > verification is not very clear. storm version 1.2.3 > > > Key: STORM-3943 > URL: https://issues.apache.org/jira/browse/STORM-3943 > Project: Apache Storm > Issue Type: Question > Components: storm-ui >Affects Versions: 1.2.3 > Environment: cluster >Reporter: zfy68 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-3955) Dependabot recommended update to maven-core
[ https://issues.apache.org/jira/browse/STORM-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad reassigned STORM-3955: --- Assignee: Bipin Prasad > Dependabot recommended update to maven-core > --- > > Key: STORM-3955 > URL: https://issues.apache.org/jira/browse/STORM-3955 > Project: Apache Storm > Issue Type: Task >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > > Bump org.apache.maven:maven-core from 3.6.0 to 3.8.1 in > /storm-buildtools/storm-maven-plugins > PR: https://github.com/apache/storm/pull/3567 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3955) Dependabot recommended update to maven-core
Bipin Prasad created STORM-3955: --- Summary: Dependabot recommended update to maven-core Key: STORM-3955 URL: https://issues.apache.org/jira/browse/STORM-3955 Project: Apache Storm Issue Type: Task Reporter: Bipin Prasad Bump org.apache.maven:maven-core from 3.6.0 to 3.8.1 in /storm-buildtools/storm-maven-plugins PR: https://github.com/apache/storm/pull/3567 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3953) Update RELEASING.md
[ https://issues.apache.org/jira/browse/STORM-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad updated STORM-3953: Description: . > Update RELEASING.md > --- > > Key: STORM-3953 > URL: https://issues.apache.org/jira/browse/STORM-3953 > Project: Apache Storm > Issue Type: Task > Components: documentation >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3954) Remove Logback pulled in by Zookeeper
Richard Zowalla created STORM-3954: -- Summary: Remove Logback pulled in by Zookeeper Key: STORM-3954 URL: https://issues.apache.org/jira/browse/STORM-3954 Project: Apache Storm Issue Type: Bug Affects Versions: 2.6.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 We are using log4j2, so better to replace an additional logging provider which lurked in by the recent 3.9.0 upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (STORM-3953) Update RELEASING.md
[ https://issues.apache.org/jira/browse/STORM-3953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bipin Prasad reassigned STORM-3953: --- Assignee: Bipin Prasad > Update RELEASING.md > --- > > Key: STORM-3953 > URL: https://issues.apache.org/jira/browse/STORM-3953 > Project: Apache Storm > Issue Type: Task > Components: documentation >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Minor > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3953) Update RELEASING.md
Bipin Prasad created STORM-3953: --- Summary: Update RELEASING.md Key: STORM-3953 URL: https://issues.apache.org/jira/browse/STORM-3953 Project: Apache Storm Issue Type: Task Components: documentation Reporter: Bipin Prasad Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3952) Add github action to deploy storm on AWS EKS
Bipin Prasad created STORM-3952: --- Summary: Add github action to deploy storm on AWS EKS Key: STORM-3952 URL: https://issues.apache.org/jira/browse/STORM-3952 Project: Apache Storm Issue Type: Task Reporter: Bipin Prasad -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3951) Add github action to deploy storm on Google Cloud Platform
Bipin Prasad created STORM-3951: --- Summary: Add github action to deploy storm on Google Cloud Platform Key: STORM-3951 URL: https://issues.apache.org/jira/browse/STORM-3951 Project: Apache Storm Issue Type: Task Components: build Reporter: Bipin Prasad -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3950) Modernize storm-jdbc
Richard Zowalla created STORM-3950: -- Summary: Modernize storm-jdbc Key: STORM-3950 URL: https://issues.apache.org/jira/browse/STORM-3950 Project: Apache Storm Issue Type: Dependency upgrade Components: storm-jdbc Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (STORM-3950) Modernize storm-jdbc
[ https://issues.apache.org/jira/browse/STORM-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated STORM-3950: --- Fix Version/s: 2.6.0 > Modernize storm-jdbc > > > Key: STORM-3950 > URL: https://issues.apache.org/jira/browse/STORM-3950 > Project: Apache Storm > Issue Type: Dependency upgrade > Components: storm-jdbc >Affects Versions: 2.5.0 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STORM-3949) libthrift 0.18.1
Richard Zowalla created STORM-3949: -- Summary: libthrift 0.18.1 Key: STORM-3949 URL: https://issues.apache.org/jira/browse/STORM-3949 Project: Apache Storm Issue Type: Dependency upgrade Affects Versions: 2.5.0 Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3782) Refactor KafkaOffsetMetric to use V2 metrics
[ https://issues.apache.org/jira/browse/STORM-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3782. Fix Version/s: 2.6.0 Assignee: Rui Li (was: Bipin Prasad) Resolution: Fixed > Refactor KafkaOffsetMetric to use V2 metrics > > > Key: STORM-3782 > URL: https://issues.apache.org/jira/browse/STORM-3782 > Project: Apache Storm > Issue Type: Improvement >Reporter: Rui Li >Assignee: Rui Li >Priority: Minor > Fix For: 2.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > https://github.com/apache/storm/blob/master/external/storm-kafka-client/src/main/java/org/apache/storm/kafka/spout/metrics/KafkaOffsetMetric.java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3771) Execute doCleanup in its own timer thread without lock
[ https://issues.apache.org/jira/browse/STORM-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3771. Fix Version/s: 2.6.0 Resolution: Fixed > Execute doCleanup in its own timer thread without lock > -- > > Key: STORM-3771 > URL: https://issues.apache.org/jira/browse/STORM-3771 > Project: Apache Storm > Issue Type: Improvement > Components: storm-server >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > _Sometimes doCleanup can take a long time (several minutes) while holding > submitLock. This slows down other "submitLock" dependent activities. Execute > doCleanup without a lock and within its own timer thread. Ignore exception > that may occur inside doCleanup() method._ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3762) Set a default character set in InputStreamReader to solve potential garbled problems
[ https://issues.apache.org/jira/browse/STORM-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3762. Fix Version/s: 2.6.0 Resolution: Fixed > Set a default character set in InputStreamReader to solve potential garbled > problems > > > Key: STORM-3762 > URL: https://issues.apache.org/jira/browse/STORM-3762 > Project: Apache Storm > Issue Type: Improvement >Reporter: dbgp2021 >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When a InputStreamReader is used, the parameter setting of a default > character set is recommended to solve potential garbled problems. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3883) Upgrade com.esotericsoftware.kryo from 3.0.3 to 4.0.2
[
https://issues.apache.org/jira/browse/STORM-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved STORM-3883.
Resolution: Duplicate
> Upgrade com.esotericsoftware.kryo from 3.0.3 to 4.0.2
> -
>
> Key: STORM-3883
> URL: https://issues.apache.org/jira/browse/STORM-3883
> Project: Apache Storm
> Issue Type: Dependency upgrade
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Building storm with Kryo 3.0.3 using Java 11, gives warnings on the use of
> reflection in 3.0.3.
>
> {code:java}
> [ERROR] WARNING: An illegal reflective access operation has occurred
> [ERROR] WARNING: Illegal reflective access by
> com.esotericsoftware.kryo.util.UnsafeUtil
> (file:/Users/bprasad/.m2/repository/com/esotericsoftware/kryo/3.0.3/kryo-3.0.3.jar)
> to constructor java.nio.DirectByteBuffer(long,int,java.lang.Object)
> [ERROR] WARNING: Please consider reporting this to the maintainers of
> com.esotericsoftware.kryo.util.UnsafeUtil
> [ERROR] WARNING: Use --illegal-access=warn to enable warnings of further
> illegal reflective access operations
> [ERROR] WARNING: All illegal access operations will be denied in a future
> release
> {code}
>
> Upgrade to version 4.0.2. (Note that version 5.x.x gives compile errors).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (STORM-3397) Upgrade to Zookeeper 3.5
[ https://issues.apache.org/jira/browse/STORM-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3397. Resolution: Duplicate > Upgrade to Zookeeper 3.5 > > > Key: STORM-3397 > URL: https://issues.apache.org/jira/browse/STORM-3397 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.0.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > Zookeeper 3.5 has a stable release now. We should upgrade I think. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3869) Bump hadoop-common from 2.10.1 to 3.2.3
[ https://issues.apache.org/jira/browse/STORM-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3869. Resolution: Duplicate > Bump hadoop-common from 2.10.1 to 3.2.3 > --- > > Key: STORM-3869 > URL: https://issues.apache.org/jira/browse/STORM-3869 > Project: Apache Storm > Issue Type: Task > Components: blobstore, storm-blobstore-migration, storm-hdfs, > storm-hdfs-oci >Reporter: Bipin Prasad >Priority: Major > > Automatically generated pull request by dependabot > [https://github.com/apache/storm/pull/3484] > Needs to be fixed to get a clean build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3915) Fix test failure in JDK 8 and 11 for storm-cassandra
[
https://issues.apache.org/jira/browse/STORM-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved STORM-3915.
Resolution: Won't Fix
We are in the process of upgrading to Cassandra 4 in
https://github.com/apache/storm/pull/3525
Build switched from 8 to 11 as baseline, so this issue isn't up2date anymore.
> Fix test failure in JDK 8 and 11 for storm-cassandra
>
>
> Key: STORM-3915
> URL: https://issues.apache.org/jira/browse/STORM-3915
> Project: Apache Storm
> Issue Type: Improvement
> Components: build, storm-cassandra
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Major
>
> Github action for JDK8 fails with message:
> {code:java}
> Error: Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test)
> on project storm-cassandra: There are test failures.
> 7150Error:
> 7151Error: Please refer to
> /home/runner/work/storm/storm/external/storm-cassandra/target/surefire-reports
> for the individual test results.
> 7152Error: Please refer to dump files (if any exist) [date].dump,
> [date]-jvmRun[N].dump and [date].dumpstream.
> 7153Error: ExecutionException The forked VM terminated without properly
> saying goodbye. VM crash or System.exit called?
> 7154Error: Command was /bin/sh -c cd
> /home/runner/work/storm/storm/external/storm-cassandra &&
> /usr/lib/jvm/temurin-8-jdk-amd64/jre/bin/java -Xmx3g
> -XX:+HeapDumpOnOutOfMemoryError -jar
> /home/runner/work/storm/storm/external/storm-cassandra/target/surefire/surefirebooter1740914470713932382.jar
> /home/runner/work/storm/storm/external/storm-cassandra/target/surefire
> 2023-04-28T18-24-45_882-jvmRun2 surefire38252873504194138tmp
> surefire_303399085227568856114tmp
> 7155Error: Error occurred in starting fork, check output in log
> 7156Error: Process Exit Code: 1
> 7157Error: Crashed tests:
> 7158Error: org.apache.storm.cassandra.trident.MapStateTest
> 7159Error: org.apache.maven.surefire.booter.SurefireBooterForkException:
> ExecutionException The forked VM terminated without properly saying goodbye.
> VM crash or System.exit called?
> 7160Error: Command was /bin/sh -c cd
> /home/runner/work/storm/storm/external/storm-cassandra &&
> /usr/lib/jvm/temurin-8-jdk-amd64/jre/bin/java -Xmx3g
> -XX:+HeapDumpOnOutOfMemoryError -jar
> /home/runner/work/storm/storm/external/storm-cassandra/target/surefire/surefirebooter1740914470713932382.jar
> /home/runner/work/storm/storm/external/storm-cassandra/target/surefire
> 2023-04-28T18-24-45_882-jvmRun2 surefire38252873504194138tmp
> surefire_303399085227568856114tmp
> 7161Error: Error occurred in starting fork, check output in log
> 7162Error: Process Exit Code: 1
> 7163Error: Crashed tests:
> 7164Error: org.apache.storm.cassandra.trident.MapStateTest
> 7165Error:at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:532)
> 7166Error:at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkOnceMultiple(ForkStarter.java:405)
> 7167Error:at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:321)
> 7168Error:at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:266)
> 7169Error:at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1314)
> 7170Error:at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
> 7171Error:at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
> 7172Error:at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> 7173Error:at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> 7174Error:at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> 7175Error:at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> 7176Error:at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> 7177Error:at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> 7178Error:at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> 7179Error:at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> 7180Error:at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> 7181Error:at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> 7182Error:at org.apache.maven.Def
[jira] [Resolved] (STORM-3943) May I ask that you can configure a user password to log in for security verification when visiting storm ui. Check the official website security verification is not very
[ https://issues.apache.org/jira/browse/STORM-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3943. Resolution: Won't Fix Better to ask on the user@ list. > May I ask that you can configure a user password to log in for security > verification when visiting storm ui. Check the official website security > verification is not very clear. storm version 1.2.3 > > > Key: STORM-3943 > URL: https://issues.apache.org/jira/browse/STORM-3943 > Project: Apache Storm > Issue Type: Question > Components: storm-ui >Affects Versions: 1.2.3 > Environment: cluster >Reporter: zfy68 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3901) Upgrade Kryo from version 4 to version 5.4.0
[ https://issues.apache.org/jira/browse/STORM-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3901. Fix Version/s: 2.6.0 Resolution: Fixed > Upgrade Kryo from version 4 to version 5.4.0 > > > Key: STORM-3901 > URL: https://issues.apache.org/jira/browse/STORM-3901 > Project: Apache Storm > Issue Type: New Feature >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Jdk 11 onwards has several changes to the reflection API. Kryo version 4 uses > prejdk API thru its used o reflectasm (shaded) jar. > Remove reflectasm-shaded, and update Kryo version to 5.4.0. > The new version of Kryo does not automatically switch to Java serialization. > Change the default serializer to automatically register all java classes like > the prior version 4. > Change storm code due to new API's in Kryo version 5.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3946) Upgrade Netty BOM
[ https://issues.apache.org/jira/browse/STORM-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3946. Fix Version/s: 2.6.0 Assignee: Richard Zowalla Resolution: Fixed > Upgrade Netty BOM > - > > Key: STORM-3946 > URL: https://issues.apache.org/jira/browse/STORM-3946 > Project: Apache Storm > Issue Type: Dependency upgrade >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Fix For: 2.6.0 > > > We are referencing a super old version of netty, which is conflicting with > Cassandra 4. We should try an upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3792) Change pom.xml to use more test JVM threads without reuse
[ https://issues.apache.org/jira/browse/STORM-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3792. Fix Version/s: 2.6.0 Resolution: Fixed > Change pom.xml to use more test JVM threads without reuse > - > > Key: STORM-3792 > URL: https://issues.apache.org/jira/browse/STORM-3792 > Project: Apache Storm > Issue Type: Improvement > Components: blobstore, examples, integration-test, storm-hdfs, > storm-hive, storm-kafka, storm-kafka-client, storm-kafka-monitor, > storm-server, storm-sql >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Maven surefire plugin configuration has two important flags: > (1) reuseForks - setting of true mean reuse created JVMs. > (2) forkCount - number of JVMs to create for testing. Pure number is an > absolute count, whereas 1.0C means same as the number of CPUs. > Reusing forked JVMs can cause somewhat indeterminate failures in test when > global class instances are not properly initialized or cleaned. An example of > such a singleton class Time. > Not reusing will cause a slowdown in tests. > To mitigate this slowdown, wherever the "forkCount=1", change it to > "forkCount=1.0C" and add reuseForks=false if not already present. However, > some modules (example storm-hdfs) forkCount cannot be increased from 1 to > 1.0C, due to either resources limits or global locking (as in hdfs tests). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STORM-3845) Upgrade activemq version from 5.15.3 to 5.18.2
[ https://issues.apache.org/jira/browse/STORM-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla resolved STORM-3845. Fix Version/s: 2.6.0 Resolution: Fixed > Upgrade activemq version from 5.15.3 to 5.18.2 > -- > > Key: STORM-3845 > URL: https://issues.apache.org/jira/browse/STORM-3845 > Project: Apache Storm > Issue Type: Improvement > Components: examples, storm-jms, storm-mqtt >Affects Versions: 2.5.0 >Reporter: Bipin Prasad >Assignee: Bipin Prasad >Priority: Major > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Upgrade activemq version from 5.15.3 to 5.18.2 in storm-mqtt and storm-jms > modules and remove the older guava dependency. > Requires JDK11. -- This message was sent by Atlassian Jira (v8.20.10#820010)
