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

Time triggered batch update does not accept null value #19

Open
wgromniak opened this issue Jan 19, 2019 · 0 comments
Open

Time triggered batch update does not accept null value #19

wgromniak opened this issue Jan 19, 2019 · 0 comments
Assignees

Comments

@wgromniak
Copy link
Contributor

userStream.updateTimeTriggeredBatch(id, 1000, null, null);

causes

net.quedex.api.common.CommunicationException: Error sending message
	at net.quedex.api.user.UserMessageSender.lambda$sendMessageQueued$7(UserMessageSender.java:168)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException: null
	at net.quedex.api.user.UserMessageSender.createBatchNode(UserMessageSender.java:151)
	at net.quedex.api.user.UserMessageSender.lambda$sendTimeTriggeredBatchUpdate$4(UserMessageSender.java:123)
	at net.quedex.api.user.UserMessageSender.lambda$sendMessageQueued$7(UserMessageSender.java:164)
	... 3 common frames omitted

@mchalapuk, @HubertBubert, CC.

@wgromniak wgromniak self-assigned this Feb 6, 2019
wgromniak pushed a commit to wgromniak/java-api that referenced this issue Feb 6, 2019
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