Restrictions on Multiple Simultaneous Executions of Agent Startup or Update Confirmation
In Agent Version 2.4.0 or later, you cannot execute multiple instances of the following types of processing at the same time on the same directory (except for the case when you start up Agent as a Windows service):
-
Agent startup on sending side
-
Agent startup on receiving side
-
Agent update confirmation
While executing an instance of one of these processing types, the activation control file (agent-activate.lock) is created and locked in the following directory:
{Agent installation directory}/bin
When the startup or update confirmation processing instance completes, the activation control file (agent-activate.lock) is automatically unlocked and then deleted.
The error messages related to multiple simultaneous executions are as follows:
a) | Failed to lock the activation control file.[{Agent installation directory}/bin/agent-activate.lock] Agent may already be running. Check the status of Agent or wait for a while and try again. |
This message is output when the locking of the activation control file (agent-activate.lock) fails. | |
Another instance of Agent startup or Agent update confirmation processing may already be in execution on Agent in the same directory. | |
Use the Agent Status Confirmation command to check the status, or wait for a while and try again. |
b) | Failed to open or lock the activation control file.[{Agent installation directory}/bin/agent-activate.lock] |
This message is output when the opening or locking of the activation control file (agent-activate.lock) fails. | |
The user who executes the command may not have the permissions required to handle the installation directory or the activation control file (agent-activate.lock). Check the permissions and try again. | |
Or, another instance of Agent startup or Agent update confirmation processing may already be in execution on Agent in the same directory. Also check the status of Agent. |
c) | Failed to delete the activation control file.[{Agent installation directory}/bin/agent-activate.lock] |
This message is output when the automatic deletion of the activation control file (agent-activate.lock) fails. | |
Check that another instance of Agent startup or Agent update confirmation processing is not in execution, and then delete the activation control file manually. | |
If you cannot delete the file manually because the file is locked, use one of the following methods to check that the target startup process has been finished, and then try deleting again. |
Target Process
jp.co.saison.sis.hulft.tsubomi.webconnect.exec.Main
For Windows
Confirm whether the target Java process has been terminated by checking the Task Manager List provided by the OS.
For Linux
Confirm whether the target Java process has been terminated by using the process status display command (ps command).