Cases Where the Agent Memory Is Used Up

In the following cases, the Agent may use more memory than allocated, and the memory may be used up:

• When large files are transferred

• When the communication speed between Agent and HULFT is slow on the receiving side

 

If Agent terminates unsuccessfully due to the 'OutOfMemoryError', modify the memory size that Agent can use by using 'jvm.options' in the Agent configuration file (agent.conf) as shown below.

Example:

jvm.options=-Xms64M -Xmx256M -XX:MaxDirectMemorySize=2048m

 

When Agent terminates unsuccessfully due to the 'OutOfMemoryError', no communication occurs for the corresponding transfer and the session ends after the non-communication time-out according to the settings in HULFT. Additionally, restart of Agent may be required.

 

We recommend that Agent should be installed in an environment equipped with at least dual-core processors if large files are transferred.