[#GATE-71] NullPointerException during registration, leftover roster items

IM Gateway

NullPointerException during registration, leftover roster items

Created: 09/25/06 05:34 PM Updated: 11/07/06 06:17 PM

Component/s:

Core

Affects Version/s:

1.0 Beta 2

Fix Version/s:

1.0 Beta 5

Time Tracking:

Not Specified

Support Plan Customer Issue:	No
Resolution Date:	11/07/06 06:17 PM
Acceptance Test - Add?:	No

Description

« Hide

1. register (with yahoo)
2. unregister
3. register again

Performing those steps seems to be causing a null pointer exception and a duplicate entry in the user's roster, which is likely to be leaving things in a very confused state. See referring thread.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Daniel Henninger - 09/25/06 07:15 PM

This is a tad more involved than I thought. I'm also getting a lot of entries in my roster that are supposed to be non-persistent... Of course Psi does weird things so it's also not clear that that's not the problem.

[ Permlink | « Hide ]

Clive Cox - 09/26/06 02:21 AM

I am writing my own client so I don't think its psi AND if it happens on psi then it also probably isn't me sending weird XML stanzas!

I am simply following JEP-077 to regster and unregister, so it looks like a real problem.

[ Permlink | « Hide ]

Daniel Henninger - 09/26/06 08:13 AM

chuckle Didn't mean to imply that Psi was the problem. =) It's just Psi is doing something else that's related that I'm investigating. There's definitely something busted on my end. Unfortunately, I think I've traced one of the problems to wildfire itself (the latest SVN). The other problem, where the transport itself is showing up a ton of times, is similar but not entirely related to the Psi/wildfire issues I was referring to.

As for this problem, I still haven't tracked it down. I committed some code to SVN that should help in tracking down exactly where the bug is occuring, but in the meantime I'm trying some other things.

[ Permlink | « Hide ]

Clive Cox - 09/26/06 09:12 AM

Should add I have seen this on both yahoo and icq transports; it may be transport-independent.

It seems to be some sort of internal state issue as the only solution is to reboot the wildfire server.
i.e. once it goes wrong for a user that user can never register properly again either from a client or admin - each time a jiveroster record is created with 0 (i.e. "none") sub column value and you get the null pointer exception showing on the wildfire console window.

[ Permlink | « Hide ]

Daniel Henninger - 09/26/06 09:23 AM

A restart fixes it? Wow, that adds to the mystery.

[ Permlink | « Hide ]

Clive Cox - 09/26/06 10:14 AM

Well, let me clarify.
After a restart, the bad records of "none" subscription obviously remain in the jiveroster table. But if these are cleaned out then registration can work again.

However, after things have gone wrong, even with a clean-out of the tables, registration can't work.

So that's what I mean by it being some sort of internal state.

[ Permlink | « Hide ]

Daniel Henninger - 09/26/06 12:17 PM

It also shouldn't be putting duplicates in there in the first place though. In fact it's supposed to be checking for that. =/ Interesting..

[ Permlink | « Hide ]

Daniel Henninger - 11/07/06 06:17 PM

This is fixed via another related issue closed. =)