Issue #2145: Exception upon index definition change

Hello,

I have the following types:

@Embeddable
public class ChangeSetRef
{
    private long   index;
    private String role;
}

@Index (members = {"refs.role", "refs.index"})
@Entity
public class ChangeSet
{
    @ElementCollection
    private Collection<ChangeSetRef> refs         = new LinkedHashSet<>();
}

If I now start up my application I get the following stacktrace:

Exception in thread "ODB-IndexActivation" java.lang.NullPointerException
at com.objectdb.o.CMV.p(CMV.java:121)
at com.objectdb.o.SCU.p(SCU.java:78)
at com.objectdb.o.VLV.m(VLV.java:165)
at com.objectdb.o.EVC.k(EVC.java:90)
at com.objectdb.o.IXS.n(IXS.java:201)
at com.objectdb.o.VIX.m(VIX.java:189)
at com.objectdb.o.VIX.g(VIX.java:157)
at com.objectdb.o.IIX.g(IIX.java:69)
at com.objectdb.o.EIX.g(EIX.java:187)
at com.objectdb.o.IIX.g(IIX.java:69)
at com.objectdb.o.IIX.f(IIX.java:58)
at com.objectdb.o.IXS.i(IXS.java:96)
at com.objectdb.o.IIS.p(IIS.java:55)
at com.objectdb.o.IXM.VA(IXM.java:454)
at com.objectdb.o.PBI.C(PBI.java:146)
at com.objectdb.o.PBI.q(PBI.java:115)
at com.objectdb.o.MBI.VD(MBI.java:83)
at com.objectdb.o.MST.U9(MST.java:783)
at com.objectdb.o.IXM.E(IXM.java:379)
at com.objectdb.o.IXM.run(IXM.java:351)
at java.lang.Thread.run(Thread.java:748)

I think this is related to my ticket http://www.objectdb.com/database/support/636. I think index changes should never cause the application to stop. Even the Doctor does not run anymore using this index definition. We use the latest ObjectDB version 2.7.2_02.

This is very urgent for us.

Best regards
Markus

> I think this is related to my ticket http://www.objectdb.com/database/support/636.

That issue was solved so this seems to be a different issue.

> I think index changes should never cause the application to stop

Of course. Agreed.

However, unfortunately the stack trace doesn't provide much information in this case.

If you can share a test case that throws the exception it would help.

Please try build 2.7.2_03.

Hello,

thanks for your fast response. The new version works as expected.

Best regards
Markus

Unfortunately we had to revert the changes in build of 2.7.2_03 in build 2.7.2_04 as they may cause duplication of index values on other types of index schema upgrades. Hopefully a better fix will be provided soon.

Please try build 2.7.2_05, which should fix the issue again.