NPE: in JabberIqRegister/EmailConfirmationSender (#1026)

Activities

Wojciech Kapcia (Tigase) opened 6 years ago

2019-04-19 07:12:11.374 [jabber:iq:register Queue Worker 0]  WorkerThread.run()    SEVERE:   tigase.server.xmppsession.SessionManager$ProcessorWorkerThread,(jabber:iq:register Queue Worker 0) Exception during packet processing: from=c2s@ip-10-0-37-90.us-west-2.compute.internal/x_50202, to=sess-man@ip-10-0-37-90.us-west-2.compute.internal, DATA=[iq xmlns="jabber:client" type="set" id="sd19"][query xmlns="jabber:iq:register"][username]CData size: 10[/username][password]CData size: 12[/password][/query][/iq], SIZE=158, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=LOCAL, TYPE=set
java.lang.NullPointerException
	at tigase.extras.emailconfirm.EmailConfirmationSender.checkRequiredParameters(EmailConfirmationSender.java:80)
	at tigase.xmpp.impl.JabberIqRegister.createAccount(JabberIqRegister.java:454)
	at tigase.xmpp.impl.JabberIqRegister.doRegisterNewAccount(JabberIqRegister.java:709)
	at tigase.xmpp.impl.JabberIqRegister.process(JabberIqRegister.java:339)
	at tigase.server.xmppsession.SessionManager$ProcessorWorkerThread.process(SessionManager.java:2625)
	at tigase.util.processing.WorkerThread.run(WorkerThread.java:68)

Andrzej Wójcik (Tigase) commented 6 years ago

I've fixed the NPE but it happened due to the fact that email is required and this requirement was not set, so registration should fail but gracefully.

Wojciech Kapcia (Tigase) commented 6 years ago

How come it was not set?

Type	Bug
Priority	Normal
Assignee	Andrzej Wójcik (Tigase)
RedmineID	8898
Version	tigase-server-8.1.0
Spent time	45m

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#1026