Resolution:
Description:
============
In BusinessEvents 4.0, exception java.lang.reflect.InvocationTargetException is seen upon Cache Server start-up.


Environment:
==========
TIBCO BusinessEvents 4.0.0 Studio


Symptoms:
=========
BE Cache Server throws the following exception -

java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at com.tibco.cep.runtime.service.om.ObjectManagerProvider.createOM(ObjectManagerProvider.java:76)
     at com.tibco.cep.runtime.service.om.ObjectManagerProvider.createOM(ObjectManagerProvider.java:19)
     at com.tibco.cep.runtime.session.impl.RuleSessionImpl.&ltinit>(RuleSessionImpl.java:155)
     at com.tibco.cep.runtime.session.impl.RuleSessionImpl.&ltinit>(RuleSessionImpl.java:122)

Cause:
=====
There could be many causes, check which one applies in context of issue -

1. Name of Processing unit is not specified correctly

2. Ontology(Concept, Event) in the project gets corrupted.



Resolution:
==========

1). Check if the Processing unit (PU) name is specified correctly while starting the engine. The reason for the same is that PU name is case sensitive.
  
2). Check the Ontology(Concept, Event) files in the project to see if they have become  corrupted. Open the concept/event files in Text editor outside the BE Studio and check if they have incorrect value of namespace or ownername. Currently there is no way to automatically verify this in Studio. They have to be verified manually by opening each ontology file.

In BusinessEvents 4.0, exception java.lang.reflect.InvocationTargetException is seen upon Cache Server start-up.