IndexOutOfBoundsException

[Dominik Lange]

hi,

we have a problem with our solr test instance.
This instance is running with 90 cores with about 2 GB of Index-Data per core.

This worked fine for a few weeks.

Now we get an exception querying data from one core : 
java.lang.IndexOutOfBoundsException: Index: 104, Size: 11
        at java.util.ArrayList.rangeCheck(ArrayList.java:571)
        at java.util.ArrayList.get(ArrayList.java:349)
        at org.apache.lucene.index.FieldInfos.fieldInfo(FieldInfos.java:288)
        at org.apache.lucene.index.FieldInfos.fieldName(FieldInfos.java:277)
        at org.apache.lucene.index.TermBuffer.read(TermBuffer.java:86)
        at 
org.apache.lucene.index.SegmentTermEnum.next(SegmentTermEnum.java:129)
        at 
org.apache.lucene.index.SegmentTermEnum.scanTo(SegmentTermEnum.java:160)
        at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:211)
        at 
org.apache.lucene.index.TermInfosReader.terms(TermInfosReader.java:277)
        at org.apache.lucene.index.SegmentReader.terms(SegmentReader.java:961)
        at 
org.apache.lucene.index.DirectoryReader$MultiTermEnum.<init>(DirectoryReader.java:989)
        at 
org.apache.lucene.index.DirectoryReader.terms(DirectoryReader.java:626)
        at 
org.apache.solr.search.SolrIndexReader.terms(SolrIndexReader.java:302)
        at 
org.apache.lucene.search.PrefixTermEnum.<init>(PrefixTermEnum.java:41)
        at org.apache.lucene.search.PrefixQuery.getEnum(PrefixQuery.java:45)
        at 
org.apache.lucene.search.MultiTermQuery$ConstantScoreAutoRewrite.rewrite(MultiTermQuery.java:227)
        at 
org.apache.lucene.search.MultiTermQuery.rewrite(MultiTermQuery.java:382)
        at org.apache.lucene.search.BooleanQuery.rewrite(BooleanQuery.java:438)
        at 
org.apache.lucene.search.IndexSearcher.rewrite(IndexSearcher.java:311)
        at org.apache.lucene.search.Query.weight(Query.java:98)
        at org.apache.lucene.search.Searcher.createWeight(Searcher.java:230)
        at org.apache.lucene.search.Searcher.search(Searcher.java:171)
        at 
org.apache.solr.search.SolrIndexSearcher.getDocListNC(SolrIndexSearcher.java:988)
        at 
org.apache.solr.search.SolrIndexSearcher.getDocListC(SolrIndexSearcher.java:884)
        at 
org.apache.solr.search.SolrIndexSearcher.search(SolrIndexSearcher.java:341)
        at 
org.apache.solr.handler.component.QueryComponent.process(QueryComponent.java:182)
        at 
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:195)
        at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:1316)
        at 
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:338)
        at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:241)
        at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
        at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
...

All other cores are working fine with the same schema.
This problem only occurs when querying for specific data like
q=fieldA:valueA%20AND%20fieldB:valueB

By using the following query data is returned
q=*:*

Has anybody any suggestions on what is causing this problem?
Are 90 cores too much for a single solr instance?

Thanks in advance,

Dominik