The hotfix can be downloaded from the TIBCO Support Customer Portal Web UI,
using your username and password for the TIBCO Support Web.

Once logged on the hotfix can be found under the Downloads Menu:
AvailableDownloads/AMX_BPM/4.1.0/TIB_amx-bpm_4.1.0_hotfix004

Listed below is a summary of updates included. Refer to the associated readme document for any additional information.

================================================================================

Closed Issues in 4.1.0_HF-004 (This Release)

Note: Where the closed issue is related to a TIBCO Support case, the relevant
case number (CN-xxxxxxxx) or Support Request ID (SR-xxxxxx) is given in brackets
after the Issue number.

WRM-9274 (CN-01258781, CN-01446144, CN-01450736, CN-01455807)
-------------------------------------------------------------
When an in-memory process instance is created, such as calling a service process
via sub-process task, an Id is generated for the instance that is only unique to
the instance of the BPM node where it was created. If an instance is created on
another node there is a possibility that it will clash with an instance on
another node when a row is written to the PVM_INMEM_PROC_TRACKER table,
resulting in a primary key violation.

WRM-9426 (CN-01453002)
----------------------
To reduce logging produced when REST services are called, add a property called
 'logLevel' in
<BPMConfig>/data/bpm/amx.bpm.app/configuration/restserviceconfig.properties
The value of 'logLevel' can be set to one of the following integer.

NOTE: Changing this setting in Linux environments does not have any affect; the
logging level remains set to the default, ERROR.

- 0 for TRACE
- 1 for DEBUG
- 2 for INFO
- 3 for WARN
- 4 for ERROR

If this property is not added to
<BPMConfig>/data/bpm/amx.bpm.app/configuration/restserviceconfig.properties then,
by default, the log level will be 4 (ERROR level).

This only impacts logging in the REST services component.

WRM-9434 (01457371)
-------------------
Auditing certain attributes (6, 7, 19 and 20) in BRM_WORKITEM_SCHEDULED,
BRM_WORKITEM_EX_COMPLETE_WORK_ITEM and BRM_WORKITEM_OPENED messages did not
take account of timezones.

WRM-9450 (CN-01458884)
----------------------
If a BPM node has crashed or is deemed to be inactive, a periodic recovery
thread attempts to recover any instances related to that node.

This includes going through the process tracker and in-memory tracker tables.  
These are used to track the status of sub-process instances.

An error in the recovery processing sometimes caused a null pointer exception.  
This resulted in the rest of the recovery process repeatedly not completing.