Home » Support » Issue Tracking » java.lang.ClassCastException: com.objectdb.o.RFV cannot be cast to com.objectdb.o.RSV

java.lang.ClassCastException: com.objectdb.o.RFV cannot be cast to com.objectdb.o.RSV

Type: BugVersion: 2.5.2Priority: HighStatus: FixedReplies: 2
#1

The following query:

SELECT count(m) FROM Message m WHERE m.attachments.original=:template

is generating this exception:

[ObjectDB 2.5.1_05] Unexpected exception (Error 990)
  Generated by Java HotSpot(TM) 64-Bit Server VM 1.6.0_32 (on Windows 7 6.1).
Please report this error on http://www.objectdb.com/database/issue/new
com.objectdb.o.InternalException: java.lang.ClassCastException: com.objectdb.o.RFV cannot be cast to com.objectdb.o.RSV
java.lang.ClassCastException: com.objectdb.o.RFV cannot be cast to com.objectdb.o.RSV
at com.objectdb.o.RSV.compareTo(RSV.java:158)
at com.objectdb.o.RFV.compareTo(RFV.java:138)
at com.objectdb.o.VAL.J(VAL.java:789)
at com.objectdb.o.EXR$e.c(EXR.java:190)
at com.objectdb.o.VAR.aA(VAR.java:864)
at com.objectdb.o.VAR.az(VAR.java:807)
at com.objectdb.o.XQI.Vt(XQI.java:69)
at com.objectdb.o.TQI.Vt(TQI.java:67)
at com.objectdb.o.MQI.Vt(MQI.java:143)
at com.objectdb.o.GQI.Uu(GQI.java:130)
at com.objectdb.o.PRG.ag(PRG.java:679)
at com.objectdb.o.PRG.af(PRG.java:553)
at com.objectdb.o.QRM.U6(QRM.java:265)
at com.objectdb.o.MST.U6(MST.java:933)
at com.objectdb.o.WRA.U6(WRA.java:293)
at com.objectdb.o.WSM.U6(WSM.java:113)
at com.objectdb.o.STC.r(STC.java:450)
at com.objectdb.o.SHN.aj(SHN.java:489)
at com.objectdb.o.SHN.K(SHN.java:156)
at com.objectdb.o.HND.run(HND.java:132)
at java.lang.Thread.run(Thread.java:662)

(The referenced template is id#156591; the expected result is 0)

Updated: I found that I get essentially the same error when the parameter type is a Drill instead of a Template.

Updated: Sample data file removed now that the issue is resolved.

#2

Just tried with version 2.5.2 and got no exception. Could you please try it?

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#3

Thank you, yes this issue is now resolved in today's 2.5.2 build.


Post Reply

To post a reply and/or subscribe to update notifications - please login