How to resolve "java.lang.ArrayIndexOutOfBoundsException: Index -1000 out of bounds for length 396" error on TIBCO BusinessEvents cache engine startup

How to resolve "java.lang.ArrayIndexOutOfBoundsException: Index -1000 out of bounds for length 396" error on TIBCO BusinessEvents cache engine startup

book

Article ID: KB0071636

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition 6.X

Description

The following error was thrown when Staring the Cache Agent:-

java.lang.ArrayIndexOutOfBoundsException: Index -1000 out of bounds for length 396
        at com.tibco.cep.runtime.service.cluster.system.MetadataCache.getEntityDao(MetadataCache.java:803)
        at com.tibco.cep.runtime.service.dao.impl.tibas.ASEntityDao.getIndexConfigsFromEntity(SourceFile:392)
        at com.tibco.cep.runtime.service.dao.impl.tibas.ASEntityDao.handleIndexing(SourceFile:409)
        at com.tibco.cep.runtime.service.dao.impl.tibas.ASEntityDao.handleValueType(SourceFile:374)
        at com.tibco.cep.runtime.service.dao.impl.tibas.ASEntityDao.startHook(SourceFile:170)
        at com.tibco.cep.runtime.service.dao.impl.tibas.ASEntityDao.startHook(SourceFile:107)
        at com.tibco.cep.runtime.service.om.impl.AbstractEntityDao.start(AbstractEntityDao.java:114)
        at com.tibco.cep.runtime.service.cluster.system.MetadataCache$1.call(MetadataCache.java:330)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)

Issue/Introduction

How to resolve "java.lang.ArrayIndexOutOfBoundsException: Index -1000 out of bounds for length 396" error on TIBCO BusinessEvents cache engine startup

Environment

All Operating systems

Resolution

The above error is related to entity dao for the Event. This is caused when the child Event/Concept is set to "Cache" but the parent Event/Concept is set to "Memory only".

To resolve the issue, please keep object management type consistent between parent and child Event/Concepts.

This can be checked/verified at the cluster level of the CDD file (Cluster area -> Override section).