Description:
In a TIBCO ActiveMatrix BusinessWorks application having TIBCO BusinessWorks ProcessMonitor (BWPM ) client pallets (log activities such as info, success, warning and error ) and configured with instantPush=true, the error below may be seen in the application and the application stops/job fails.

java.lang.IndexOutOfBoundsException: index: -1
        at javolution.util.d.get(nJAMS:191)
        at com.faizsiegeln.njams.client.palette.Error.eval(nJAMS:29)
        at com.tibco.pe.core.TaskImpl.eval(Unknown Source)
        at com.tibco.pe.core.Job.a(Unknown Source)
        at com.tibco.pe.core.Job.k(Unknown Source)
        at com.tibco.pe.core.JobDispatcher$JobCourier.a(Unknown Source)
        at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source)


Symptoms:
The error below is seen in the Application logs when TIBCO BusinessWorks ProcessMonitor (BWPM ) client pallets log activity is executed and the job fails.

2015 Nov 20 18:54:07:283 GMT +5 BW.BWPMKrishTestDynamic Error [] null Job-86008 Error in [Process Definition.process/LogError]
java.lang.IndexOutOfBoundsException: index: -1
    at javolution.util.d.get(nJAMS:209)
    at com.faizsiegeln.njams.client.palette.Error.eval(nJAMS:31)
    at com.tibco.pe.plugin.Activity.eval(Unknown Source)
    at com.tibco.pe.core.TaskImpl.eval(Unknown Source)
    at com.tibco.pe.core.Job.a(Unknown Source)
    at com.tibco.pe.core.Job.k(Unknown Source)
    at com.tibco.pe.core.JobDispatcher$JobCourier.a(Unknown Source)
    at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source)
Cause:
This issue will occur only when you have set instantPush=true and maxQueueLength(=20) is reached. This happens when communication with the TIBCO Enterprise Message Service server is affected, specifically when the  log activity is executed and an event messages is going to be sent at same time. When the parameter "instantPush=true" it will try to send the event (for activity) and the log activity is executed at same time. However, when "instantPush=false", this issue will not be seen. This means the event message was not sent at the time when the log activity was executed.