Resolution:
Description
=========
Under certain circumstances, the TIBCO iProcess Engine [iPE] will continue to write to a debug log file even after properly removing the debug attribute.

Environment:
==========
   o All TIBCO iProcess Engines
   o All environments

Symptoms:
=========
Issuing a $SWDIR/util/swadm delete_attribute command on a DEBUG attribute will successfully remove the attribute from the process_attributes table but the process will continue to write to the log file.

This only occurs if debug is set using zero for the machine id, using a specific process name and using a specific process instance number.  For example, a debug string set with, "swadm set_attribute 0 BG 1 DEBUG ALL=255", would not stop writing to the debug log file if a, "swadm delete_attribute 0 BG 1 DEBUG", command is issued.

Cause:
=====
This issue is caused by a fault in the TIBCO iProcess Engine and MR 43194 has been raised to correct the issue in a future release of the product.

Resolution:
=========

To stop debug entries from writing to the file, set a DEBUG attribute on the process specifying a string of ALL=0.  For example, "swadm set_attribute 0 BG 2 DEBUG ALL=0".

To prevent the issue from occurring, set debug attributes with any of the following machine id, process name and process instance combinations.  This example uses combinations that would both write BG debug and disable properly when their attribute was deleted.

0 ALL 0
0 BG 0
1 BG 0
1 BG 1

The TIBCO iProcess Engine continues to write to the debug log file even after the debug attribute is deleted.