Resolution:
Description:
============
All TIBCO iProcess Workspace (Browser) (iPWB) releases from 10.6.x to 11.2.x (inclusive) have two logging options that are both inadvertently enabled by default:

    appLogActive    
    echoToJsxLog

Environment:
===========
   o All iProcess Workspace (Browser) releases from 10.6.x to 11.2.x (inclusive).

Symptoms:
========
There are two possible negative side effects from this.  These side effects pertain to both the iPWB application and any custom Web Client Component (WCC) applications.

Side Effect 1.
In some cases where large amounts of data are being exchanged with the action processor, this can have a negative effect on User Interface (UI) response time.

Specifically, if large amounts of data are included in the request to the action processor, the processing will be slower because of logging.  Possible examples of operations that could create requests with large amounts of data are:

                Starting cases
                Keeping or releasing workitems
                Modifying data for a case
                Triggering an event with case data
                Performing a jump to on a case and specifying case data

Typically, but not always, large requests are created for these operations when large memo fields are used.  It is the size of the requests to the action processor that is the factor.  The size of the response from the action processor does not significantly impact the UI response time when logging is enabled.

Side Effect 2.
Memory usage in the browser will continually increase at a rate based on the amount of data being exchanged bi-directionally between the browser and the action processor.  The memory usage only accumulates for the duration of the browser session.  Closing and reopening the browser clears the accumulated memory.

Cause:
=====
Product defect causing the application log to be active by default.

Resolution:
==========
MR43262 has been raised for this issue and it will be corrected in a future release.

Workaround:
The following record element can be added to config.xml to disable this logging:

    <!--
    The &ltrecord jsxid="logging" element controls logging options.
    Attributes:
        - appLogActive - if "true" the Application will be initially set to
                         write all messages to the log.
        - echoToJsxLog - if "true" all Application Log messages will be echoed
                         to the Application Monitor.
    Setting either or both of these to true can be useful in debugging, but can
    affect application performance and should generally be set to false in a
    deployed production environment.
    -->
    &ltrecord jsxid="logging" type="ipc"
            appLogActive="false"
            echoToJsxLog="false" />

Note: TIBCO iProcess Workspace (Browser) versions prior to 10.6.x have logging turned off by default.

Keywords/Tags:
= = = = = = = = =