Description:
In the application logs, we see "String too long (max length: 2000) for 'Extract Property/Attribute 'Error'" which is a result of a string value greater than 2000 assigned to the attributes of  TIBCO BusinessWorks ProcessMonitor Client log (info,success,warn,error) palettes.



Symptoms:

The following is seen in application logs:

1). String too long (max length: 2000) for "Extract Property/Attribute 'Error".

2). String index out of range: 20 java.lang.StringIndexOutOfBoundsException:
String index out of range: 20 at java.lang.String.substring(Unknown Source) at java.lang.String.subSequence(Unknown Source)
at java.util.regex.Matcher.getSubSequence(Unknown Source) at java.util.regex.Matcher.group(Unknown Source)
at com.faizsiegeln.njams.client.e.a(nJAMS:298) at com.faizsiegeln.njams.client.e.afterExecution(nJAMS:205)
at com.tibco.pe.core.Job.a(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 error in application/engine.logs is due to bad design or data which is being assigned/extracted for BusinessWorks ProcessMonitor(BWPM) Client palettes as an attribute value.
This extracted attribute value is too long, i.e. greater than 2000 characters.

String too long (max length: 2000) for 'Attribute Value' Error seen in application logs when using TIBCO BusinessWorks ProcessMonitor Client palettes.

The attribute value for TIBCO BusinessWorks ProcessMonitor(BWPM) Client activities should be less then 2000 characters. In case the TIBCO ActiveMatrix BusinessWorks (BW) process design is such that this value is dynamic, the length of the incoming value must be checked/truncated so that the activity value would be less than 2000 characters. This will ensure that the above error will not occur.