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

Decoder NullPointerException masks underlying exception #164

Closed
masseyke opened this issue Mar 25, 2024 · 1 comment · Fixed by #168
Closed

Decoder NullPointerException masks underlying exception #164

masseyke opened this issue Mar 25, 2024 · 1 comment · Fixed by #168

Comments

@masseyke
Copy link

If I have an mdb file where one of the fields is the wrong type (in this case, lat and lon were stored as strings rather than doubles), then Decoder attempts to throw this exception:

java.lang.IllegalArgumentException: argument type mismatch
	at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:65)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
	at [email protected]/com.maxmind.db.Decoder.decodeMapIntoObject(Decoder.java:441)
	at [email protected]/com.maxmind.db.Decoder.decodeMap(Decoder.java:341)
	at [email protected]/com.maxmind.db.Decoder.decodeByType(Decoder.java:162)
	at [email protected]/com.maxmind.db.Decoder.decode(Decoder.java:151)
	at [email protected]/com.maxmind.db.Decoder.decodeMapIntoObject(Decoder.java:434)
	at [email protected]/com.maxmind.db.Decoder.decodeMap(Decoder.java:341)
	at [email protected]/com.maxmind.db.Decoder.decodeByType(Decoder.java:162)
	at [email protected]/com.maxmind.db.Decoder.decode(Decoder.java:151)
	at [email protected]/com.maxmind.db.Decoder.decode(Decoder.java:76)
	at [email protected]/com.maxmind.db.Reader.resolveDataPointer(Reader.java:411)
	at [email protected]/com.maxmind.db.Reader.getRecord(Reader.java:185)
	at [email protected]/com.maxmind.geoip2.DatabaseReader.get(DatabaseReader.java:280)
	at [email protected]/com.maxmind.geoip2.DatabaseReader.getCity(DatabaseReader.java:365)
	at [email protected]/com.maxmind.geoip2.DatabaseReader.tryCity(DatabaseReader.java:359)

Then Decoder attempts to format a nice message explaining to the user what the problem is, but in doing so throws a NullPointerException because some optional fields are null (in this case average_income is null):

java.lang.NullPointerException: Cannot invoke "Object.getClass()" because "parameters[index]" is null
	at [email protected]/com.maxmind.db.Decoder.decodeMapIntoObject(Decoder.java:450)
	at [email protected]/com.maxmind.db.Decoder.decodeMap(Decoder.java:341)
	at [email protected]/com.maxmind.db.Decoder.decodeByType(Decoder.java:162)
	at [email protected]/com.maxmind.db.Decoder.decode(Decoder.java:151)
	at [email protected]/com.maxmind.db.Decoder.decodeMapIntoObject(Decoder.java:434)
	at [email protected]/com.maxmind.db.Decoder.decodeMap(Decoder.java:341)
	at [email protected]/com.maxmind.db.Decoder.decodeByType(Decoder.java:162)
	at [email protected]/com.maxmind.db.Decoder.decode(Decoder.java:151)
	at [email protected]/com.maxmind.db.Decoder.decode(Decoder.java:76)
	at [email protected]/com.maxmind.db.Reader.resolveDataPointer(Reader.java:411)
	at [email protected]/com.maxmind.db.Reader.getRecord(Reader.java:185)
	at [email protected]/com.maxmind.geoip2.DatabaseReader.get(DatabaseReader.java:280)
	at [email protected]/com.maxmind.geoip2.DatabaseReader.getCity(DatabaseReader.java:365)
	at [email protected]/com.maxmind.geoip2.DatabaseReader.tryCity(DatabaseReader.java:359)

So the user never gets the message about a field being stored with the wrong type, and instead is confused by a NullPointerException. I think line 450 probably ought to just ignore any parameters where parameters[index] is null.

More information on how to produce a file that caused this is at https://discuss.elastic.co/t/geoip-challenges-custom-city-mmdb/355173/13.

@masseyke masseyke changed the title Docoder NullPointerException masks underlying exception Decoder NullPointerException masks underlying exception Mar 25, 2024
@horgh
Copy link
Contributor

horgh commented Mar 25, 2024

Thank you for the report! Yes, checking for null there seems like it would be the thing to do.

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

Successfully merging a pull request may close this issue.

2 participants