Official | HULFT IoT Release Note Fourth Edition: July 1, 2021

HIPJ-1559

In the Windows environment, when 2,147,483 seconds (approximately 24.8 days) elapses after OS starts, HULFT IoT Agent might continuously execute file triggers and polling processing without waiting time

Phenomenon

For HULFT IoT Agent performing in the environment described at the condition to reproduce, every timer setting (monitoring interval to the monitored file and polling interval to the HULFT IoT Manager and so on) becomes invalid, and the problem that HULFT IoT Agent executes the monitoring and the polling without any intervals occurs.

This problem causes the following wrong actions and concrete influences on your environment.

  • Wrong actions

    • The setting of [Monitoring Interval] in [Transfer Settings] becomes invalid, and HULFT IoT Agent transfers the file immediately after the monitoring conditions are met.

    • The setting of [Polling Interval] in [Operation Settings] becomes invalid, and HULFT IoT Agent continues to receive and send by polling HULFT IoT Manager.

    • The setting of [Receive Queue Polling Interval] in [Operation Settings] becomes invalid, and HULFT IoT Agent continues to receive and send by polling HULFT IoT Manager.

    • The setting of [Communication Time Limit] in [Operation Settings] becomes invalid, and HULFT IoT Agent always transfers a file and executes polling regardless of the limitation of hours.

  • Concrete influences

    • A total amount of data communication in the network (communication fee) increases.

    • It might highly load the server environment and the network.

    • It might enlarge logs accumulated in the HULFT IoT Manager environment.

    • It might highly load the CPU in the HULFT IoT Agent environment because HULFT IoT Agent performs continuously.

    • It disables the operation that the user limits hours for HULFT IoT Agent to communicate.

Affected versions

From Ver.1.0.0 to Ver.1.4.1

Corrected version

Ver.1.5.0

Affected module

HULFT IoT Agent

Condition to reproduce

This phenomenon occurs when the following two conditions are met:

  • You have introduced 32 bits version HULFT IoT Agent in a Windows OS.

  • 2,147,483 seconds (approximately 24.8 days) have expired since the OS on which HULFT IoT Agent performs started.

* The number of seconds written above is the performance time of the Windows OS, not the performance time of HULFT IoT Agent.

Alternative workaround

None

Status description

If HULFT IoT Agent starts with the conditions described in the condition to reproduce met, HULFT IoT Agent operates according to the settings value.

 

(c) Saison Information Systems Co., Ltd. 2016

 

Official | HULFT IoT Release Note Fourth Edition: July 1, 2021