Resolution:
Description:
===========
TIBCO BusinessEvents reports "java.lang.ClassNotFoundException" when procesing an input Event

Environment:
===========
TIBCO BusinessEvents versions 4.x / 5.x
All Operating Systems

Symptoms:
=========
Exception thrown in logfile by one of the worker threads.

$default.be.mt$.Thread.3] - [runtime.scheduler] &ltEventName>
java.lang.ClassNotFoundException: PlanItemExecuteRequestEvent
    at com.tibco.cep.runtime.service.loader.BEClassLoader.createEntity(BEClassLoader.java:1033)
    at com.tibco.cep.driver.jms.serializer.MapMessageSerializer.deserialize(SourceFile:60)
    at com.tibco.cep.runtime.scheduler.impl.WorkerBasedControllerV2.executeTask(WorkerBasedControllerV2.java:349)
    at com.tibco.cep.runtime.scheduler.impl.WorkerBasedControllerV2$WorkerTask.run(WorkerBasedControllerV2.java:395)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at com.tibco.cep.runtime.util.CustomBEManagedThread.run(CustomBEManagedThread.java:23)

Cause:
======
Incorrect Namespace settings for the input Event

NOTE:
-------
Enable debug (LogLevel: *:all) to print  the namespace settings for the input event in the BusinessEvents logfile.

Resolution:
========
Update namespace settings for input Event (e.g. in TIBCO BusinessWorks process, Activity JMSQueueSend) - URL and Name of Event must exist in the project.

_nm_: optional string type used to specify BusinessEvents event type
_ns_: optional string type used to specify namespace

i.e.:
_nm_="incomingEvent" _ns_="www.tibco.com/be/ontology/&ltBusinessEventFolder>/&ltincomingEventName>"