TIBCO ActiveMatrix Adapter for Files (FA) publisher consumes more CPU although the polling period is 60 seconds.

TIBCO ActiveMatrix Adapter for Files (FA) publisher consumes more CPU although the polling period is 60 seconds.

book

Article ID: KB0076207

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for Files for Unix and Windows -
Not Applicable -

Description

Description:
If the polling interval in Designer is configured as 60 seconds, TIBCO ActiveMatrix Adapter for Files (FA) publisher should consume CPU only during polling (that is, once in 60 seconds) as it will otherwise be in an inactive state. But FA constantly consumes CPU beyond the polling period.
Symptoms:
Although the polling interval in Designer is 60 seconds, the TIBCO ActiveMatrix Adapter for Files publisher constantly consumes CPU as if it were polling on a near constant interval.
Cause:
This high CPU consumption is due to the 'Document Delay' field in the 'Advanced Tab' of TIBCO ActiveMatrix Adapter for Files (FA) publisher. In Designer, if  'Document Delay' is configured as 1 millisecond, then CPU consumption increases. 'Document delay' is the interval between two successive publications for file adapter. The flow control of messages being published to a subscriber can be turned on by setting this field. Adapter scans the input directory for input files after every 60 seconds of the polling interval, but since 'Document Delay' is set to 1 millisecond, the publisher will try to apply a delay of 1 millisecond for publishing a message. Hence, FA constantly consumes CPU.
 

Issue/Introduction

TIBCO ActiveMatrix Adapter for Files (FA) publisher consumes more CPU although the polling period is 60 seconds.

Environment

Product: TIBCO ActiveMatrix Adapter for Files (Unix/Win) Version: 6.1.x, 6.2.x OS: All supported Operating System. --------------------

Resolution

For controlling CPU consumption, configure the 'Document Delay' field in the 'Advanced Tab' of TIBCO ActiveMatrix Adapter for Files publisher as 0 millisecond. This will control the flow of messages being published to a subscriber in the default manner. This will result in a decrease in CPU consumption.