Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect handling of topology.message.timeout.secs #24

Open
DevInsanity opened this issue Sep 29, 2015 · 1 comment
Open

Incorrect handling of topology.message.timeout.secs #24

DevInsanity opened this issue Sep 29, 2015 · 1 comment

Comments

@DevInsanity
Copy link

Attempting to set the topology.message.timeout.secs config value results in a class cast exception:

java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer
    at backtype.storm.contrib.jms.spout.JmsSpout.open(JmsSpout.java:160) ~[stormjar.jar:?]

(Note: this stack trace was produced from the 0.9.0 release, but it looks like the current code has the same issue.)

It looks like the typical method in other parts of Storm is to null-check the value, then cast to Number and call intValue on the result.

See also: https://groups.google.com/forum/#!topic/storm-user/SX2gEBfNEFg

@DevInsanity
Copy link
Author

After raising this, I was considering fixing it myself, but noticed that #9 exists, which looks like it's an out-of date fix for this very issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant