-
Notifications
You must be signed in to change notification settings - Fork 872
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
NPE during database upgrade #7512
Comments
Reason is simple. On 2.1.19 country was not required. Just checked in old version of Orienteer - it's null. So during upgrade it leads to NPE because of this code of Locale: public Locale(String language, String country, String variant) {
if (language== null || country == null || variant == null) {
throw new NullPointerException();
}
baseLocale = BaseLocale.getInstance(convertOldISOCodes(language), "", country, variant);
localeExtensions = getCompatibilityExtensions(language, "", country, variant);
} |
Guys this issue is already in progress and fixed by storage team I am assigning it back to us |
Fixed, @PhantomYdn could you try now? |
Hi @PhantomYdn did you have a chance to look on it? |
@PhantomYdn is it possible to provide some ETA when you will be able to check issue? |
Hi @PhantomYdn could you provide an update on this issue? |
Closing the issue because of no response. In case, please reopen it. |
OrientDB Version: 2.2.20
Java Version: 7
OS: linux
We had db which run on 2.1.19. But now we tried to run it on instance of Orienteer which use 2.2.20. So OrientDB tried to convert DB and failed with the following exception:
What can be done to prevent this failing?
The text was updated successfully, but these errors were encountered: