The Server1.0 catalog contains messages in the range
BEA002601 - BEA002799. Messages in this catalog are part of the
weblogic.server
Internationalization package and the weblogic.i18n Localization package.
|
BEA-002601
|
Error: An error occurred while trying to print logs during server lifecycle operation, exception.
|
Description
| An error occurred while trying to print logs during server lifecycle operation, exception. |
|
Cause
| An exception was raised while printing logs during a server lifecycle operation (such as server startup or shutdown). |
|
Action
| No action is needed. Due to this error, server logs are not printed on the Console. Check the log file for more information. |
|
|
BEA-002602
|
Info: Shutting down name0
|
Description
| The server is shutting down a thread with the specified name |
|
Cause
| The server is shutting down a thread with the specified name |
|
Action
| No action needed. |
|
|
BEA-002603
|
Debug: ListenThread: msg
|
Description
| Debug message concerning the operation of listen threads. |
|
Cause
| Internal debug. |
|
Action
| None. |
|
|
BEA-002604
|
Debug: ListenThread: msg, e
|
Description
| Debug message concerning the exceptional operation of listen threads. |
|
Cause
| Internal debug. |
|
Action
| None. |
|
|
BEA-002605
|
Info: Adding address: ad0 to licensed client list
|
Description
| The server accepted a connection from the specified client |
|
Cause
| The server accepted a connection from the specified client |
|
Action
| No action needed |
|
|
BEA-002606
|
Error: Unable to create a server socket for listening on channel "channel". The address listenAddress0 might be incorrect or another process is using port port1: ex2.
|
Description
| The server is unable to create a server socket at the given address and port. |
|
Cause
| The address might be incorrect or another process is using the port. |
|
Action
| Please check if the listen address is valid (using ipconfig/ifconfig) and port specified is not in use by another process (using netstat). |
|
|
BEA-002607
|
Notice: Channel "channel" listening on listenAddress0:port1 was shutdown.
|
Description
| The server shutdown the listen thread and server socket. |
|
Cause
| The server or channel may have been shut down. |
|
Action
| None required unless this was unexpected. |
|
|
BEA-002608
|
Error: The ListenThread because of an error: th0
|
Description
| An exception was thrown while the listen thread was accepting client connections. |
|
Cause
| This exception is thrown when the server socket is unable to accept client connections. |
|
Action
| Check the FD limit. Tune OS parameters that deal with socket creation using ServerSocket. |
|
|
BEA-002609
|
Info: Channel Service initialized.
|
Description
| The Channel subsystem is operational. |
|
Cause
| The Channel subsystem is operational. |
|
Action
| No action required. |
|
|
BEA-002610
|
Info: Dynamic Listener Service initialized.
|
Description
| The dynamic listeners subsystem is operational. |
|
Cause
| The dynamic listeners subsystem is operational. |
|
Action
| No action required. |
|
|
BEA-002611
|
Warning: Hostname "hostname", maps to multiple IP addresses: addressString
|
Description
| The listen address of the server resolves to multiple IP addresses. |
|
Cause
| The hostname of the server resolves to multiple IP addresses. This can cause problems for the admin server. |
|
Action
| Check if this was done on purpose. |
|
|
BEA-002612
|
Notice: Channel "channel" listening on listenAddress:port did not start did not start properly.
|
Description
| The listen address listenAddress:port could not be bound within the configured grace period. |
|
Cause
| Some of the listen ports did not open or fail within the configured grace period. |
|
Action
| Ensure that none of the configured listen ports are in use by any other process. |
|
|
BEA-002613
|
Notice: Channel "channel" is now listening on listenAddress:port for protocols protocols.
|
Description
| The server successfully started the listen thread and server socket. |
|
Cause
| None. |
|
Action
| None. |
|
|
BEA-002614
|
Notice: Reopening channel "channel" on listenAddress:port.
|
Description
| The server has restarted listening on a channel after having backed off due to a socket exception while accepting client connections |
|
Cause
| A socket exception while accepting client connections caused the server to backoff. The server is now ready to accept connections. |
|
Action
| No action is needed. |
|
|
BEA-002615
|
Notice: After having failed to listen, the server is now listening on channel "channel" on listenAddress:port.
|
Description
| The server has restarted listening on a channel after having backed off due to a socket exception while accepting client connections |
|
Cause
| A socket exception while accepting client connections caused the server to backoff. The server is now ready to accept connections. |
|
Action
| No action is needed. |
|
|
BEA-002616
|
Critical: Failed to listen on channel "channel" on listenAddress:port, failure count: fails1, failing for secs2 seconds, e3
|
Description
| The server listener will retry the listen after a short delay. |
|
Cause
| The server got an exception while trying to accept client connections. It will try to backoff to aid recovery. |
|
Action
| The OS limit for the number of open file descriptor (FD limit) needs to be increased. Tune OS parameters that might help the server to accept more client connections (e.g. TCP accept back log). |
|
|
BEA-002617
|
Critical: Attempting to close and reopen the server socket on on channel "channel" on listenAddress:port.
|
Description
| The server listener is having trouble accepting a socket connection and after several simple retries failed. It is closing and reopening the server socket. |
|
Cause
| The server listener is having trouble accepting a socket connection and after several simple retries failed. It is closing and reopening the server socket. |
|
Action
| Check if the FD limit needs to be increased. Tune OS parameters that might help the server to accept more client connections. |
|
|
BEA-002618
|
Error: An invalid attempt was made to configure a channel for unconfigured protocol "name".
|
Description
| The server configuration specified a channel that uses a protocol that is not enabled. |
|
Cause
| The server configuration specified a channel that uses a protocol that is not enabled. |
|
Action
| Enabled the protocol in the server configuration. |
|
|
BEA-002619
|
Info: Not all the ListenPort(s) started properly.
|
Description
| Some of the listen ports did not open during server startup |
|
Cause
| One or more listen ports failed to open during server startup |
|
Action
| Ensure that none of the configured listen ports are in use by other process |
|
|
BEA-002620
|
Error: An invalid attempt was made to configure a channel for server "server" on an unknown listen address "name".
|
Description
| The server configuration specified a channel that uses a listen address that does not exist. |
|
Cause
| The server configuration specified a channel that uses a listen address that does not exist. |
|
Action
| Correct the server configuration. |
|
|
BEA-002621
|
Notice: Connection rejected, the server license allows connections from only ma0 unique IP addresses.
|
Description
| Clients from more distinct addresses than the license allows are trying to connect. |
|
Cause
| Clients from more distinct addresses than the license allows are trying to connect. |
|
Action
| Use a license that allows for more clients to connect. |
|
|
BEA-002622
|
Info: The protocol "name" is now configured.
|
Description
| The server has loaded a protocol making it available for outbound traffic and configurable for inbound traffic. |
|
Cause
| The server has loaded a protocol making it available for outbound traffic and configurable for inbound traffic. |
|
Action
| None. |
|
|
BEA-002623
|
Notice: Connection rejected, the server is in the state state.\r\n Starting service svr, num of total.\r\n Last service last took timems.
|
Description
| Clients are trying to connect to the server before it is in the RUNNING state. |
|
Cause
| Clients are trying to connect to the server before it is in the RUNNING state. |
|
Action
| Wait until the server has started. |
|
|
BEA-002624
|
Info: The administration protocol is "name" and is now configured.
|
Description
| The server has loaded the administration protocol making it available for outbound traffic and configurable for inbound traffic. |
|
Cause
| The server has loaded the administration protocol making it available for outbound traffic and configurable for inbound traffic. |
|
Action
| None. |
|
|
BEA-002625
|
Error: An attempt to configure channel "name" failed because of exception.
|
Description
| The dynamic configuration of a channel was invalid, or failed in some way. |
|
Cause
| The cause is detailed in the accompanying exception. |
|
Action
| Review the exception. |
|
|
BEA-002626
|
Warning: The protocol "name" could not be loaded: e.
|
Description
| The server was unable to load a protocol. |
|
Cause
| Consult the exception for why the protocol could not be loaded. |
|
Action
| Consult the exception for why the protocol could not be loaded. |
|
|
BEA-002627
|
Error: The domain configuration must have at least one admin channel on every server or no admin channels at all.
|
Description
| The domain configuration must have at least one admin channel on every server or no admin channels at all. |
|
Cause
| The server was contacted by a server that did not reflect the same admin state as itself. |
|
Action
| Modify the domain configuration so that all servers have admin channels, or enabled the domain-wide admin port. |
|
|
BEA-002628
|
Critical: Unable to export RemoteLifeCycleOperations RMI object due to th
|
Description
| Unable to export RemoteLifeCycleOperations RMI object. The ServerLifeCycleRuntime will be unable to contact this server |
|
Cause
| RMI export failed. |
|
Action
| Please report to support with the logd |
|
|
BEA-002629
|
Debug: Unable to lookup RemoteLifeCycleOperationsImpl from server serverName due to th
|
Description
| Unable to lookup RemoteLifeCycleOperations RMI object. The ServerLifeCycleRuntime will be unable to contact serverName server. |
|
Cause
| RMI lookup failed. The remote server is unreachable. |
|
Action
| Check if the remote server is shutdown. |
|
|
BEA-002630
|
Info: Accepting connections again.
|
Description
| The server is accepting client connections again after refusing connections as a part of server throttling |
|
Cause
| The server is accepting client connections again after refusing connections as a part of server throttling |
|
Action
| No action is needed. |
|
|
BEA-002631
|
Warning: Max Threshold Reached for Open Sockets [Total Open Sockets: size, Allowed Max: max], No More Connections allowed.
|
Description
| There are more clients attempting to connect to the server than the server will accept at the same time. |
|
Cause
| The MaxOpenSocketCount attribute of the server configuration defines the upper bound of the number of open sockets. |
|
Action
| Increase the MaxOpenSocketCount attribute of the server configuration. Use the server tuning tab in the console. |
|
|
BEA-002632
|
Notice: Found jrmp.jar in dir directory. JRMP Service is now enabled.
|
Description
| Found jrmp.jar in dir directory. JRMP Service is now enabled. |
|
Cause
| JRMP is enabled |
|
Action
| No action required. |
|
|
BEA-002633
|
Emergency: A port conflict was detected in the server configuration. The server is configured to listen on two ports that have the same port number and IP address. Channel "channel1" address "url" conflicts with channel "channel2" address "url".
|
Description
| A port conflict was detected in the server configuration. The server is configured to listen on two ports that have the same port number and IP address. Channel "channel1" address "url" conflicts with channel "channel2" address "url". |
|
Cause
| The server is configured to listen on two ports that have the same port number and IP address. |
|
Action
| Please ensure that the address identities [ListenAddress and ListenPort combinations] are distinct and unique. |
|
|
BEA-002634
|
Info: The server "servername" disconnected from this server.
|
Description
| The server "servername" disconnected from this server. It may have crashed, been shutdown normally or been partitioned from the network. |
|
Cause
| The remote server may have crashed, been shutdown normally or been partitioned from the network. |
|
Action
| None. |
|
|
BEA-002635
|
Info: The server "servername" connected to this server.
|
Description
| The server "servername" connected to this server. It may have been booted or a network partition may have been resolved. |
|
Cause
| The remote server may may have been booted or a network partition may have been resolved. |
|
Action
| None. |
|
|
BEA-002636
|
Error: Unable to update server "servername" with local channel information.
|
Description
| Unable to update server "servername" with local channel information. It may have crashed, been shutdown normally or been partitioned from the network. |
|
Cause
| The remote server may have crashed, been shutdown normally or been partitioned from the network. |
|
Action
| None. |
|
|
BEA-002637
|
Warning: Failed to register a disconnect listener because of e.
|
Description
| Failed to register a disconnect listener because of e. |
|
Cause
| This can happen during server start when the incoming network connection is not suitable for callbacks and the booting server does not yet have a listen port open. |
|
Action
| None. The server should eventually be connected properly. |
|
