Error List

Error List for the ‘WL92-NodeManager’ Category

BEA-300035 - Error :arg0

Description:
Error condition encountered by the node manager.

Cause:
Details of the cause are provided in the message.

WL92-NodeManager ,

BEA-300011 - Could not execute command cmd for server svrName using the node manager, because the target machine configuration was not found. This feature is applicable only for servers that are started up through the node manager

Description:
The command cmd cannot be executed for the server svrName, because no machine is associated with this server. The server should be started using the node manager.

Cause:
The user attempted to use the node manager to perform an operation on a server that is only valid if the server was started using the node manager.

WL92-NodeManager ,

BEA-300022 - Could not execute command cmd for server svrName using the node manager, due to an internal error.

Description:
Command cmd could not be executed on server svrName using the node manager.

Cause:
This is an internal error.

WL92-NodeManager

BEA-300037 - The state change notification registration failed. The server will only be able to respond to the GETSTATE messages by the node manager. Reason : arg0

Description:
Registration of the node manager agent for state change notification of the server failed. The server will not proactively be able to notify the node manager of its changed state.

Cause:
See the message for details.

WL92-NodeManager ,

BEA-300012 - Could not execute command cmd for server svrName using the node manager, because the node manager configuration for target machine machName was not found.

Description:
The node manager is not configured for the machine associated with server svrName.

Cause:
This is an internal error.

WL92-NodeManager ,

BEA-300026 - The node manager command servlet was unable to send a reply to the node manager health query.

Description:
The node manager command servlet was unable to send a reply to the node manager health query.

Cause:
This is an internal error.

WL92-NodeManager

BEA-300000 - arg0

Description:
Uncatalogued debug message – please do not change.

Cause:
Debugging – please do not change.

WL92-NodeManager ,

BEA-300040 - I/O error while writing node manager status change message.

Description:
An I/O error occurred while attempting to write a node manager status change message to the standard output stream. While the server will continue to run, this will prevent the node manager from being able to continue monitoring the server properly.

Cause:
Possibly the standard output stream has been closed or the node manager has stopped monitoring.

WL92-NodeManager , , , , , , , , , , ,

BEA-300013 - Could not execute command cmd for server svrName using the node manager, because the node manager configuration for target machine machName was not found. This feature is applicable only for servers that were started up using the node manager.

Description:
The node manager is not configured for machine null.

Cause:
The user attempted to use the the node manager to perform an operation on a server that is only valid if the server was started using the node manager.

WL92-NodeManager ,

BEA-300027 - The node manager command servlet received an invalid command.

Description:
The node manager command servlet received an invalid internal query.

Cause:
This is an internal error.

WL92-NodeManager