Thanks for the update Richard, will wait for that release.

Best regards,
Rahm

From: Richard Zowalla <rich...@zowalla.com>
Date: Saturday, August 10, 2024 at 2:00 AM
To: user@storm.apache.org <user@storm.apache.org>, Dabalos, Rahmat Peter 
<rahmat.peter.daba...@ing.com>
Subject: Re: Upgraded Storm to version 2.6.3 but experiencing ClassCastException
Yes - the next release of Storm (2.6.4 or 2.7.0) should contain the fix for 
STORM-4069.
I opened a PR to avoid the ClassCastException in MasterBatchCoordinator.
If it is reviewed and merged, we should have nightlies available soon, so you 
can test, if this actually fixes your issue or if we discover similar things ;-)
Don’t know if a lot of people are using trident nowadays.

Regarding the timeline:

Storm is a volunteer driven project, i.e. it is developed and maintained by 
unpaid volunteers who donate time as they have it - concrete timelines are 
therefore difficult.
Since the last release is only a few weeks old, I assume, that the next release 
might lay somewhere after the summer break.

Gruß
Richard



Am 09.08.2024 um 14:13 schrieb Dabalos, Rahmat Peter via user 
<user@storm.apache.org>:

Hello,

Regarding the fix, this means that you will be releasing 2.6.4 with that fix am 
I right? In your estimation, how long do you think it will take? That 
information will be useful in order to align our planning as we are upgrading 
all of our tech stack into the latest versions to mitigate vulnerabilities and 
risks.

Best regards,
Rahm Dabalos

From: Dabalos, Rahmat Peter via user <user@storm.apache.org>
Date: Friday, August 9, 2024 at 7:10 PM
To: user@storm.apache.org <user@storm.apache.org>
Subject: Re: Upgraded Storm to version 2.6.3 but experiencing ClassCastException
Sorry, I can’t create a ticket in your JIRA.

But will wait for the fix thank you! Please do notify once it is available.

Best regards,
Rahm

From: Richard Zowalla <rich...@zowalla.com>
Date: Friday, August 9, 2024 at 7:07 PM
To: user@storm.apache.org <user@storm.apache.org>
Subject: Re: Upgraded Storm to version 2.6.3 but experiencing ClassCastException
Yep. Than it is most likely the JSON lib change.
We can fix this easily, I guess. I am currently on mobile, so cannot create an 
issue. If you have an ASF Jira Account, feel free to create an issue. 
Otherwise, I will do it later.

Gruß
Richard

Am 9. August 2024 12:34:15 MESZ schrieb "Dabalos, Rahmat Peter via user" 
<user@storm.apache.org>:
Thanks for the response,  Sorry and will take note of that.
The previous version of our storm topology is 2.5.0.

From: Richard Zowalla <rich...@zowalla.com>
Date: Friday, August 9, 2024 at 6:32 PM
To: user@storm.apache.org <user@storm.apache.org>
Subject: Re: Upgraded Storm to version 2.6.3 but experiencing ClassCastException
Hi,

thanks. First of all: please do not cross-post to multiple lists at once, 
thanks.

I think this might be a regression from JSON Lib upgrades/changed and needs a 
fix.

From which version did you come? Just to make sure...

Gruß
Richard

Am 9. August 2024 11:42:10 MESZ schrieb "Dabalos, Rahmat Peter via user" 
<user@storm.apache.org>:
Hello,

Upgraded our storm versions to 2.6.3 but having issues on startup. Here is the 
error log:
2024-08-07 09:30:22.749 o.a.s.u.Utils Thread-22-$mastercoord-bg0-executor[1, 1] 
[ERROR] Async loop died!
java.lang.ClassCastException: class java.lang.Integer cannot be cast to class 
java.lang.Long (java.lang.Integer and java.lang.Long are in module java.base of 
loader 'bootstrap')
  at 
org.apache.storm.trident.topology.MasterBatchCoordinator.getStoredCurrTransaction(MasterBatchCoordinator.java:235)
 ~[storm-client-2.6.3.jar:2.6.3]
  at 
org.apache.storm.trident.topology.MasterBatchCoordinator.open(MasterBatchCoordinator.java:87)
 ~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.executor.spout.SpoutExecutor.init(SpoutExecutor.java:142) 
~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.executor.spout.SpoutExecutor.call(SpoutExecutor.java:152) 
~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.executor.spout.SpoutExecutor.call(SpoutExecutor.java:50) 
~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.utils.Utils$1.run(Utils.java:393) 
[storm-client-2.6.3.jar:2.6.3]
  at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
2024-08-07 09:30:22.756 o.a.s.e.e.ReportError 
Thread-22-$mastercoord-bg0-executor[1, 1] [ERROR] Error
java.lang.RuntimeException: java.lang.ClassCastException: class 
java.lang.Integer cannot be cast to class java.lang.Long (java.lang.Integer and 
java.lang.Long are in module java.base of loader 'bootstrap')
  at org.apache.storm.utils.Utils$1.run(Utils.java:413) 
~[storm-client-2.6.3.jar:2.6.3]
  at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.lang.ClassCastException: class java.lang.Integer cannot be cast 
to class java.lang.Long (java.lang.Integer and java.lang.Long are in module 
java.base of loader 'bootstrap')
  at 
org.apache.storm.trident.topology.MasterBatchCoordinator.getStoredCurrTransaction(MasterBatchCoordinator.java:235)
 ~[storm-client-2.6.3.jar:2.6.3]
  at 
org.apache.storm.trident.topology.MasterBatchCoordinator.open(MasterBatchCoordinator.java:87)
 ~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.executor.spout.SpoutExecutor.init(SpoutExecutor.java:142) 
~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.executor.spout.SpoutExecutor.call(SpoutExecutor.java:152) 
~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.executor.spout.SpoutExecutor.call(SpoutExecutor.java:50) 
~[storm-client-2.6.3.jar:2.6.3]
  at org.apache.storm.utils.Utils$1.run(Utils.java:393) 
~[storm-client-2.6.3.jar:2.6.3]
  ... 1 more
2024-08-07 09:30:22.788 o.a.s.u.Utils Thread-22-$mastercoord-bg0-executor[1, 1] 
[ERROR] Halting process: Worker died

Best regards,
Rahm


-----------------------------------------------------------------

ATTENTION:

The information in this e-mail is confidential and only meant for the intended 
recipient. If you are not the intended recipient, don't use or disclose it in 
any way. Please let the sender know and delete the message immediately.

-----------------------------------------------------------------

-----------------------------------------------------------------

ATTENTION:

The information in this e-mail is confidential and only meant for the intended 
recipient. If you are not the intended recipient, don't use or disclose it in 
any way. Please let the sender know and delete the message immediately.

-----------------------------------------------------------------

-----------------------------------------------------------------

ATTENTION:

The information in this e-mail is confidential and only meant for the intended 
recipient. If you are not the intended recipient, don't use or disclose it in 
any way. Please let the sender know and delete the message immediately.

-----------------------------------------------------------------

-----------------------------------------------------------------

ATTENTION:

The information in this e-mail is confidential and only meant for the intended 
recipient. If you are not the intended recipient, don't use or disclose it in 
any way. Please let the sender know and delete the message immediately.

-----------------------------------------------------------------


-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended 
recipient. If you are not the intended recipient, don't use or disclose it in 
any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------

Reply via email to