-
Notifications
You must be signed in to change notification settings - Fork 25
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
NullPointerException when calling deserialiser #10
Comments
This moves the instantiation of the plugin thread objects after the creation of the deserialiser. Previously, the threads were trying to access the deserialiser which wasn't initialised yet and were trying to work with a null pointer. Resolves: OpenTSDB#10
@muffix mate, have you fixed the issue? Any luck with getting messages from kafka queue? I was playing around this plugin, but was not able to run it because of serialisation issue. |
With the changes from #11 it works for me. |
__ |
Yours looks like a completely different issue @mancubus77. It can't find the class |
You right mate, sorry |
* Instantiate plugin threads after deserialiser This moves the instantiation of the plugin thread objects after the creation of the deserialiser. Previously, the threads were trying to access the deserialiser which wasn't initialised yet and were trying to work with a null pointer. Resolves: #10 * Fix the name of the deserialiser config setting Config entries are case sensitive and the readme previously incorrectly capitalised "Deserializer". Signed-off-by: Chris Larsen <[email protected]>
I've had some trouble getting this plugin to run and was facing a NullPointerException when it reads the first message.
When a new consumer group is created, that group instantiates the specified deserialiser and creates the plugin thread. In its constructor, the thread then goes and gets the deserialiser from the consumer group.
However, since the consumer group first starts the thread and then instantiates the Deserialiser, the reference to the deserialiser in the thread object is null. This reference is never updated which is eventually causing a null pointer exception when the first message comes in.
I think the creation of the threads should happen after the deserialiser is initialised.
The text was updated successfully, but these errors were encountered: