ArrayIndexOutOfBoundsException

java.lang.ArrayIndexOutOfBoundsException: 7


at chemaxon.sss.search.StructureSearch.restoreHitIndexes(StructureSearch.java:1284)


at chemaxon.sss.search.StructureSearch.findNext0(StructureSearch.java:5437)


at chemaxon.sss.search.StructureSearch.findFirst0(StructureSearch.java:5217)


at chemaxon.sss.search.StructureSearch.findFirst(StructureSearch.java:5177)


at chemaxon.sss.search.MolSearch.findNextEnumerated(MolSearch.java:1114)


at chemaxon.sss.search.MolSearch.findNextFiltered(MolSearch.java:1004)


at chemaxon.sss.search.MolSearch.findFirst(MolSearch.java:896)

Hi Trevor,





Could you send the query and target molecules for this search? Were you using the latest JChem version?





Cheers,


Szabolcs

This is using the latest chem but I don't have access to the structures that generated this unfortunately.

I see. We will need to reproduce the problem in order to fix it.


Is it possible to somehow get the query molecule at least?


Then we could try to search in a large database to reproduce the bug.





If the stack trace was in a log file, the query structure may be logged somewhere before or after the error message? (For example, for the JChem web application example, each query is reported in the log file.)





Szabolcs

It is really hard to capture information for these runtime exceptions - there is no local exception handling anywhere near this code since this isn't a documented exception that the method can throw.

You are right. In future JChem versions we will catch all exceptions inside search classes and include the query and target molecules in the error message. (These errors are relatively rare, so they won't fill up log files.)





JChem 3.2.12 is already in the testing phase and we are not planning more patch releases for 3.2, so most probably this functionality will appear in the next major release, JChem 5.0.





Szabolcs