Hitachi

Hitachi Application Server V10 Messages


KDKD10153-E

The processing did not finish within the time limit. (server name = aa....aa, server type = bb....bb, processing = cc....cc)

aa....aa

Server name

bb....bb

Server type

cc....cc

Processing

Description

The executed processing was interrupted because the time limit was exceeded. The cause of the problem varies depending on the processing output in the message.

  • create server

    The processing time of the server creation batch file (server creation shell script) has exceeded 600 seconds or the server start-up monitoring time.

  • delete server

    The processing time of the server deletion batch file (server deletion shell script) has exceeded 600 seconds.

  • start server

    The processing time of the server start-up batch file (server start-up shell script) has exceeded the server start-up monitoring time.

  • stop server

    The processing time of the server stop batch file (server stop shell script) has exceeded the server stop monitoring time.

  • monitoring server

    The processing time of the batch file for process ID acquisition (shell-script for process ID acquisition) has exceeded 600 seconds or the server start-up monitoring time.

  • get jvm system properties

    The processing time for the processing to acquire Java VM system properties of the host node exceeded 600 seconds, the server start monitoring time, or the server stop monitoring time.

  • get environmental variables

    The processing time to acquire the environment variable for the node host has exceeded 600 seconds, the server start-up monitoring time, or server stop monitoring time.

  • execute external command

    The processing time of the command executed by the host node has exceeded 600 seconds.

  • event hook command

    The processing time of the event hook command has exceeded 600 seconds.

Action

Based on the cause, perform one of the following corrective actions.

  • Of the machines listed below, check the CPU usage of the applicable machine. If the machine is overloaded, stop any unnecessary processes.

  • If the processing (processing = cc....cc) output to the message is one of the following, check the contents of the executed file: create server, delete server, start server, stop server, monitoring serverIf there is an unnecessary processing or a processing that loops unnecessarily, delete or correct that processing.

  • If the processing (processing = cc....cc) output to the message is one of the following, check the start monitoring time and stop monitoring time of each server: create server, start server, stop server, monitoring server, get jvm system properties, get environmental variablesIf the monitoring time is insufficient, use the set subcommand to change the following parameters:

    • configs.config.Configuration name of JavaEE server.hitachi-manage-info.start-timeout-in-seconds

    • hitachi-prf-configs.hitachi-prf-config.Configuration name of PRF.hitachi-manage-info.start-timeout-in-seconds

    • hitachi-webserver-configs.hitachi-webserver-config.Configuration name of web server.hitachi-manage-info.start-timeout-in-seconds

    • configs.config.Configuration name of JavaEE server.hitachi-manage-info.stop-timeout-in-seconds

    • hitachi-prf-configs.hitachi-prf-config.Configuration name of PRF.hitachi-manage-info.stop-timeout-in-seconds

    • hitachi-webserver-configs.hitachi-webserver-config.Configuration name of Web server.hitachi-manage-info.stop-timeout-in-seconds