Skip navigation.
Downloads | Product Documentation | Support

WebLogicServer Subsystem Messages The WebLogicServer1.0 catalog contains messages in the range BEA000200 - BEA000399. Messages in this catalog are part of the `weblogic.t3.srvr` Internationalization package and the `weblogic.i18n` Localization package.
BEA-000200 | Alert: The proper license key was not found. maxAddresses=newMaxAddresses0 licenseException1
Description | licenseException1 As a result, the server will now accept connections from only newMaxAddresses0 addresses.
Cause | The license.bea file does not have a tag for LICENSE PRODUCT= (any of the following) "WebLogic" "Tengah" "WebLogic/JDBC" "Tengah/JDBC" "jdbcKona/T3"
Action | Obtain a fresh license.bea file from BEA Systems.
BEA-000201 | Notice: Thread "thread0" listening on port port1, ip address addr2
Description | The server is listening on the designated port and address.
Cause | Server was started.
Action | No action required.
BEA-000202 | Notice: Thread "thread0" listening on port port1.
Description | The server is listening in the designated port.
Cause | Server was started.
Action | No action required.
BEA-000203 | Notice: Reopening listen socket on port port0.
Description | The server has restarted listening on port after having backed off due to 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-000204 | Critical: Failed to listen on port port0, failure count: fails1, failing for secs2 seconds, e3
Description | The server ListenThread 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-000205 | Notice: After having failed to listen, the server is now listening on port port0.
Description | The server has restarted listening on port after having backed off due to 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-000206 | Critical: Attempting to close and reopen the server socket on port port0.
Description | The server ListenThread is having trouble accepting a socket connection and after several simple retries failed. It is closing and reopening the server socket.
Cause | The server ListenThread 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-000207 | Emergency: Unable to create a server socket for: listenAddress0, port: port1. ex2 The address listenAddress0 might be incorrect or another process is using port port1.
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 in use by another process (using netstat)
BEA-000208 | Emergency: Unable to create a server socket for port: port0. ex1 Perhaps another process is using port port0.
Description | Failed to open port.
Cause | Perhaps another process is using the port.
Action | Check to see if another process is using the port in question (e.g. with netstat).
BEA-000209 | Emergency: ListenThread.run() failed: 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-000210 | Emergency: The WebLogic Server is no longer listening for connections.
Description | The server stops listening during the shutdown process.
Cause | The server was shutdown.
Action | Unless the server was shutdown intentionally, restart the WebLogic server.
BEA-000211 | 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-000212 | Notice: Connection rejected, filter blocked sock0, fe1
Description | The incoming message was not recognised as one of the supported protocols
Cause | The incoming message was not recognised as one of the supported protocols
Action | Ensure that the server is configured for the relevant protocol
BEA-000213 | 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-000214 | Info: WebLogic Server "name1" version:\nversion0 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.\n (c) 1999, 2000, 2001 BEA Systems, Inc.
Description | The startup banner used when a server starts up.
Cause | The startup banner used when a server starts up.
Action | No action needed.
BEA-000215 | Info: Loaded License : licenseLocation0
Description | Prints where the license file was loaded from
Cause | Prints where the license file was loaded from
Action | No action needed
BEA-000216 | Notice: WebLogic Server Started
Description | Boot process completed successfuly.
Cause | Boot process completed successfuly.
Action | No action required.
BEA-000217 | Critical: Failed to fully suspend the server due to: e0
Description | An error occurred while the server was changing state from RUNNING to STANDBY.
Cause | One or more subsystems failed to suspend preventing the server from going into STANDBY state.
Action | The exception trace contains information about which subsystem failed. If the error is more system oriented please contact support with the logs.
BEA-000218 | Alert: Server shutdown has been requested by requester0
Description | The server is requested to shutdown.
Cause | The server is requested to shutdown.
Action | No action needed.
BEA-000219 | Alert: The shutdown sequence has been initiated.
Description | The shutdown sequence has been initiated.
Cause | This message is logged when the server has started the shutdown process.
Action | No action needed.
BEA-000220 | Notice: Cannot shutdown the server, the request was from a null user (Principal).
Description | The server refused to shutdown since the command came from an unauthorized user.
Cause | The server refused to shutdown since the command came from an unauthorized user.
Action | Only users within the Administrators group can shutdown the server. Please retry the command with a user having admin credentials.
BEA-000221 | Notice: Cannot shutdown the server, the request was from a nameless user (Principal).
Description | The server refused to shutdown since the command came from an unauthorized user.
Cause | The server refused to shutdown since the command came from an unauthorized user.
Action | Only users within the Administrators group can shutdown the server. Please retry the command with a user having admin credentials.
BEA-000222 | Notice: Cannot disable server logins, the request was from a null user (Principal).
Description | The server refused to lock itself since the command came from an unauthorized user.
Cause | The server refused to lock itself since the command came from an unauthorized user.
Action | If you are an administrator, retry the command with an user having enough privileges to perform this operation.
BEA-000223 | Notice: Cannot disable server logins, the request was from a nameless user (Principal).
Description | The server refused to lock itself since the command came from an unauthorized user.
Cause | The server refused to lock itself since the command came from an unauthorized user.
Action | If you are an administrator, retry the command with an user having enough privileges to perform this operation.
BEA-000224 | Notice: Cannot enable server logins, the request was from a null user (Principal).
Description | The server refused to unlock itself since the command came from an unauthorized user.
Cause | The server refused to unlock itself since the command came from an unauthorized user.
Action | If you are an administrator, retry the command with an user having enough privileges to perform this operation.
BEA-000225 | Notice: Cannot enable server logins, the request was from a nameless user (Principal).
Description | The server refused to unlock itself since the command came from an unauthorized user.
Cause | The server refused to unlock itself since the command came from an unauthorized user.
Action | If you are an administrator, retry the command with an user having enough privileges to perform this operation.
BEA-000226 | Alert: The enabling of server logins has been requested by requester0
Description | The server has been requested to unlock itself and enable server logins again.
Cause | The server has been requested to unlock itself and enable server logins again.
Action | No action needed.
BEA-000227 | Alert: Server logins have been enabled.
Description | Server logins have been enabled.
Cause | Server logins have been enabled.
Action | No action needed.
BEA-000228 | Alert: The disabling of server logins has been requested by requester0
Description | The server is about to lock itself and prevent further logins
Cause | A LOCK command was issued by an administrator.
Action | No action needed.
BEA-000229 | Alert: Server logins have been disabled.
Description | Server logins have been disabled.
Cause | A LOCK command was issued by an administrator.
Action | No action needed.
BEA-000230(retired) | Critical: Failed to submit shutdown pending command: e0
Description | Failed to submit shutdown pending command
Cause | Command failed
Action | Check the exception trace for more information
BEA-000231 | Info: Waiting secs0 seconds for server shutdown.
Description | The server will wait for specified seconds before starting shutdown
Cause | A shutdown command was issued with a wait time. The server will wait for specified seconds before starting shutdown
Action | A cancel shutdown command can be issued during the wait time to cancel the shutdown process. Otherwise no action is needed.
BEA-000232 | Info: Server shutdown is commencing NOW and is irreversible.
Description | Server shutdown is commencing NOW and is irreversible.
Cause | A shutdown command was issued by an administrator.
Action | No action is needed.
BEA-000233 | Info: Requesting all threads to perform their own shutdown.
Description | Requesting all threads to perform their own shutdown. This is a part of server shutdown.
Cause | Requesting all threads to perform their own shutdown. This is a part of server shutdown.
Action | No action is needed.
BEA-000234(retired) | Info: Waiting secs0 seconds for threads to complete shutdown.
Description | Waiting for specified seconds for threads to complete shutdown.
Cause | Deprecated funtionality
Action | Deprecated funtionality
BEA-000235(retired) | Critical: Failed to submit shutdown command: e0
Description | Failed to submit shutdown command
Cause | Not used
Action | Not used
BEA-000236 | Info: Stopping execute threads.
Description | The WebLogic kernel is being shutdown as part of the shutdown process.
Cause | An administrator issued a shutdown command
Action | No action needed.
BEA-000237 | Emergency: Server shutdown due to fatal exception: e0
Description | Server shutdown due to fatal exception
Cause | The shutdown process failed due to a fatal exception
Action | Please check the logs for more information. If the error is more system oriented please contact support with the logs
BEA-000238 | Info: Shutdown has completed.
Description | Shutdown has completed.
Cause | Shutdown has completed.
Action | No action needed.
BEA-000239 | Alert: The cancellation of server shutdown has been requested by requester0
Description | The server is requested to cancel a pending shutdown operation
Cause | An administrator issued a cancel shutdown command
Action | No action needed
BEA-000240 | Notice: Cannot cancel the server shutdown, the request was from a null user (Principal).
Description | Cannot cancel the server shutdown, the request was from a null user (Principal).
Cause | The user used to issue the cancel shutdown operation does not have enough privileges.
Action | The command can only be executed by a user from the Admin group. Please retry the command with the right privilieges.
BEA-000241 | Notice: Cannot cancel the server shutdown, the request was from a nameless user (Principal).
Description | Cannot cancel the server shutdown, the request was from a nameless user (Principal).
Cause | The user used to issue the cancel shutdown operation does not have enough privileges.
Action | The command can only be executed by a user from the Admin group. Please retry the command with the right privilieges.
BEA-000242 | Alert: Cannot cancel server shutdown: there is already no shutdown in progress.
Description | Cannot cancel server shutdown: there is already no shutdown in progress.
Cause | Cannot cancel server shutdown as the server is not in the state 'Shutdown in Progress'.
Action | No action needed. Please check the console for the state of the server.
BEA-000243 | Alert: It is too late to cancel the server shutdown: the shutdown is already in progress.
Description | It is too late to cancel the server shutdown: the shutdown is already in progress.
Cause | The server has already started shutting down. Its too late to cancel shutdown at this point
Action | No action needed.
BEA-000244 | Info: Cancelling server shutdown.
Description | Cancelling server shutdown.
Cause | An administrator has issued a cancel shutdown operation
Action | No action needed.
BEA-000245 | Alert: Failed to correctly inform all server components that shutdown was canceled: e0
Description | Shutdown was canceled, but the event to notify any interested server subsystems that shutdown was canceled did not get sent.
Cause | Internal system error
Action | Some subsystems or applications may need to be restarted.
BEA-000246 | Info: Server shutdown has been canceled and logins are enabled.
Description | Server shutdown has been canceled and logins are enabled.
Cause | The cancel shutdown operation was successful.
Action | No action needed.
BEA-000247 | Info: Server shutdown has been cancelled, but note that logins are disabled. If desired, enable logins separately.
Description | Server shutdown has been canceled, but note that logins are disabled. If desired, enable logins separately.
Cause | Enable logins using the UNLOCK command
Action | Enable logins using the UNLOCK command
BEA-000248 | Critical: Problem while trying to get localized T3Srvr message, messageid m0, e1
Description | An exception occurred while trying to find a localized message.
Cause | The localized version of the message could not be found.
Action | No action required.
BEA-000249 | Critical: Sorry, because weblogic.ConsoleInputEnabled=true the server can only be shut down from the command line. Type the command "shut" in the window in which the server was started.
Description | Property weblogic.ConsoleInputEnabled is set to true.
Cause | weblogic.ConsoleInputEnabled was set true on the server startup command line.
Action | To shutdown the server type the command "shut" in the window in which the server was started.
BEA-000250(retired) | Critical: Not listening for SSL, th0
Description | An exception occurred in the context of opening a listen port for SSL.
Cause | This is a summary message and usually is preceeded by a more detailed message or messages indicating why the server will not listen for SSL.
Action | Examine the log and correct any SSL misconfiguration indicated.
BEA-000251(retired) | Info: Switched to group "gid0"
Description | The server switched to the specified group after opening the listen port
Cause | A non-privileged group was specifed. The server switched to the desired group before accepting client requests.
Action | No action needed.
BEA-000252(retired) | Critical: Cannot switch to group "gid0"
Description | The server is unable to switch to the specified group
Cause | The server is unable to switch to the specified group
Action | Ensure that the group exists
BEA-000253(retired) | Info: Switched to user "gid0"
Description | Server switched to the specified user before accepting client requests.
Cause | A non-privileged user was specified as a server startup property. The server switched to the specified before accepting client connections.
Action | No action needed.
BEA-000254(retired) | Critical: Cannot switch to user "gid0"
Description | Cannot switch to the specified non-privileged user
Cause | Cannot switch to the specified non-privileged user
Action | Ensure that the user exists
BEA-000255(retired) | Critical: Not listening on administrative port, th0
Description | Not used
Cause | Not used
Action | Not used
BEA-000256 | Info: Invoking name0.main(args1)
Description | The server runs a startup/shutdown class.
Cause | The server configuration specifies start- and shutdown classes to run.
Action | No action required.
BEA-000257 | Critical: Exception reading command: e0
Description | Server could not read command from shell window.
Cause | An exception occurred while reading commands from the shell window.
Action | Disable shell command input property weblogic.ConsoleInputEnabled
BEA-000258 | Info: command [cmd0]
Description | The server console received the specified command and is about to execute it
Cause | The server console received the specified command and is about to execute it
Action | No action needed.
BEA-000259 | Info: Console: Profiling enabled
Description | Console: Profiling enabled
Cause | Console: Profiling enabled
Action | No action needed.
BEA-000260 | Info: Console: Profiling disabled
Description | Console: Profiling disabled
Cause | Console: Profiling disabled
Action | Console: Profiling disabled
BEA-000261 | Critical: system user is not permitted to shutdown, e0
Description | The server could not be shutdown because the user is not permitted to shutdown the server.
Cause | The server was not shutdown because the user is not authorized to shutdown the user.
Action | Look at the exception text in e0 for more information on diagnosing the problem. Look for previous log messages for more information on the authorization failure. If the user down not have permission to shutdown the server but should, use the console to define a policy for this server that allows the user to shutdown.
BEA-000262 | Error: No such command: cmd0
Description | The server did not recognize the command.
Cause | Unknown command was entered.
Action | Please refer to the list of known commands.
BEA-000263 | Info: GC: Before free/total=free0/total1 (percent2%)
Description | Shows GS statistics before forcing GC
Cause | Shows GS statistics before forcing GC
Action | No action needed.
BEA-000264 | Info: GC: After free/total=free0/total1 (percent2%)
Description | Shows GS statistics after forcing GC
Cause | Shows GS statistics after forcing GC
Action | No action needed.
BEA-000265 | Notice: Attempt to unbind ClientContext "cc0" that is not bound.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000266 | Info: cc0 has n1.
Description | Deprecated funtionality
Cause | Deprecated funtionality
Action | Deprecated funtionality
BEA-000267 | Info: cc0 had a negative workQueueDepth of n1
Description | Deprecated funtionality
Cause | Deprecated funtionality
Action | Deprecated funtionality
BEA-000268 | Critical: Failed to send unsolicted message "obj0" to client, e1
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000269 | Info: The connection to the client using "cc0" has been unexpectedly lost due to reason1. The server is initiating a hard disconnect.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000270 | Info: Timing out "cc0" because it was idle.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000271 | Info: Ignoring a repeated request to schedule the death of "cc0".
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000272 | Info: Scheduling the death of "cc0".
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000273 | Info: Removing "cc0" because of hard disconnect timeout.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000274 | Info: Removing "cc0" because of soft disconnect timeout.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000275 | Info: Soft disconnect pending for min0.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000276 | Info: Hard disconnect pending for min0.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000277 | Info: Idle disconnect pending for min0.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000278 | Critical: Destroy of workspace key "key0" failed, th1
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000279(retired) | Critical: Error setting event connect parameters, e0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000280(retired) | Critical: Error generating connect event, e0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000281(retired) | Critical: Error setting event disconnect parameters, e0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000282(retired) | Critical: Error generating disconnect event, e0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000283 | Critical: Failed to marshal response, ioe0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000284 | Critical: Unexpected failure to marshal response, rte0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000285(retired) | Critical: ExecutionContext received an unexpected softDisconnect.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000286 | Critical: Failed to invoke startup class "name0", th1
Description | Could not run a startup class to completion.
Cause | An exception occurred in a startup class.
Action | Determine the error in the startup class code and restart the server. To work around the problem, set the "abort on startup failure" property to false.
BEA-000287 | Info: Invoking startup class: name0.startup(args1)
Description | Invoking startup class with the specified arguments
Cause | Invoking startup class with the specified arguments
Action | No action needed
BEA-000288 | Info: name0 reports: result1
Description | The invoked startup class returned the following status
Cause | Logs the return value of the startup class
Action | No action needed.
BEA-000289 | Critical: Failed to invoke shutdown class "name0", th1
Description | Could not run a shutdown class to completion.
Cause | An exception occurred in a shutdown class.
Action | Determine the error in the shutdown class code and restart the server.
BEA-000290 | Info: Invoking shutdown class: name0.shutdown(args1)
Description | Invoking shutdown class
Cause | The server is invoking shutdown classes as a part of shutdown
Action | No action needed.
BEA-000291 | Info: name0 reports: result1
Description | The server logs the return value of the shutdown class
Cause | The server logs the return value of the shutdown class
Action | No action needed.
BEA-000292 | 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-000293(retired) | Critical: name0 missed action event, e1
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000294(retired) | Alert: name0 missed trigger event generation, e1
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000295(retired) | Alert: name0 missed trigger event, e1
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000296(retired) | Alert: Security configuration problem with certificate file filename0, th1
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000297 | Error: Inconsistent security configuration, th0
Description | The initialization of SSL failed due to an exception when loading the private key, loading the server certificates, loading the trusted CA certificates, or setting the trust validator.
Cause | An exception occurred in SSL initialization.
Action | Look at the exception in th0 for more information on diagnosing the problem.
BEA-000298 | Notice: Certificate expires in days0 days: cert1
Description | A server certificate or trusted CA certificate expires in days0 days.
Cause | The certificate is about to expire.
Action | Obtain a new server certificate or trusted CA certificate before it expires.
BEA-000299(retired) | Critical: Running low strength (exportable) WebLogic Server build and full strength (domestic) SSL license.\n Only low strength (exportable) SSL connections will be accepted.
Description | Running low strength (exportable) WebLogic Server build and full strength (domestic) SSL license.\n Only low strength (exportable) SSL connections will be accepted.
Cause | Running low strength (exportable) WebLogic Server build and full strength (domestic) SSL license.\n Only low strength (exportable) SSL connections will be accepted.
Action | No action needed
BEA-000300 | Info: Certificate contents: cert0
Description | The contents of the certificate used for SSL are logged in this message.
Cause | The server logs the certificate contents so it is clear what certificate is used for SSL.
Action | Verify that the correct certificate is being used as the server certificate.
BEA-000301 | Warning: Using only low strength (exportable) cipher suites with a full strength (domestic) license and certificates.
Description | All of the ciphers suites in the Ciphersuites attribute of the SSL MBean are low strength (exportable), but the license allows full strength SSL support and the server certificate is also full strength.
Cause | The cipher suites are of low strength while the license and certificates allow full strength.
Action | If full strength cipher suites are desired, modify the Ciphersuites attribute of the SSL MBean to include full strength cipher suites.
BEA-000302(retired) | Critical: SSLListenThread failed in call to weblogic.net.http.Handler.init(), th0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000303 | Critical: The proper license key for SSL was not found. e0\n Not listening for SSL.
Description | The license check for SSL failed because the proper license key for SSL was not found or an exception occurred in the license checking code.
Cause | The license.bea file does not have a tag for LICENSE PRODUCT= (any of the following) "SSL/Domestic" "SSL/Export"
Action | Obtain a fresh license.bea file from BEA Systems.
BEA-000304 | Critical: Attempting to use full strength (domestic) certificates without a full strength (domestic) license.
Description | The server certificate is a full strength (domestic) certificate, but the license only allows low strength (export) SSL support.
Cause | Full strength certificates can not be used with a low strength SSL license.
Action | Specify the correct low strength (exportable) certificates in the WebLogic configuration, or obtain a full strength (domestic) license.
BEA-000305(retired) | Critical: Attempting to use full strength (domestic) certificates without a full strength (domestic) software build.
Description | Attempting to use full strength (domestic) certificates without a full strength (domestic) software build.
Cause | Attempting to use full strength (domestic) certificates without a full strength (domestic) software build.
Action | Specify the correct low strength (exportable) certificates in the WebLogic configuration, or obtain a full strength (domestic) build of the WebLogic server.
BEA-000306 | Critical: Cannot use SSL, no certificates have been specified in the WebLogic configuration.
Description | There were no certificates in either the keystore or the Server Certificate File.
Cause | No certificates can be found for use by SSL.
Action | If using a KeyStore for the server certificate, then set the ServerPrivateKeyAlias in the SSL MBean. If using the Server Certificate File, ensure that valid certificates are contained within the file.
BEA-000307 | Info: Exportable key maximum lifespan set to uses0 uses.
Description | The ExportKeyLifespan attribute of the SSL MBean is used to set the Exportable key maximum lifespan in SSL. The value set is uses0.
Cause | The server logs the exportable key maximum lifespan so it is clear what lifespan is being used.
Action | Verify that the lifespan is the desired value.
BEA-000308 | Info: Using full strength (domestic) SSL.
Description | The SSL license allows full strength (domestic) and the server certificate is also full strength (domestic).
Cause | With a full strength SSL license and a full strength server certificate, the server is using full strength SSL.
Action | Verify that full strength SSL support is the desired behavior.
BEA-000309 | Error: Attempting to use a full strength (domestic) cipher suite without a full strength (domestic) license.
Description | One or more of the ciphers suites in the Ciphersuites attribute of the SSL MBean are not exportable and are of full strength (domestic). The use of a full strength cipher suite requires a full strength (domestic) SSL license.
Cause | There is a mismatch between the strength of the cipher suite and the strength of the SSL license.
Action | Obtain a full strength (domestic) SSL license or only specify cipher suites that are low strength (exportable).
BEA-000310 | Info: Using low strength (exportable) SSL.
Description | All of the ciphers suites listed in the Ciphersuites attribute of the SSL MBean are low strength (exportable). The SSL license is also low strength.
Cause | The server only supports low strength (exportable) SSL.
Action | Verify that low strength (exportable) SSL is acceptable in your environment.
BEA-000311 | Warning: Attempting to use low strength (exportable) certificates with a full strength (domestic) license.
Description | The server certificates are low strength (exportable), but the license allows for full strength (domestic) SSL support.
Cause | The server certificate is of different strength than the license.
Action | To take advantage of the full strength license, obtain and use full strength (domestic) certificates.
BEA-000312(retired) | Critical: Cannot require clients to have certificates without specifying a valid value for SSL TrustedCAFileName.
Description | Cannot require clients to have certificates without specifying a valid value for SSL TrustedCAFileName.
Cause | Cannot require clients to have certificates without specifying a valid value for SSL TrustedCAFileName.
Action | Specify a valid value for SSL TrustedCAFileName
BEA-000313(retired) | Info: Using number0 client root CAs.
Description | Not used
Cause | Not used
Action | Not used
BEA-000314 | Alert: The execution class "class0" did not retrieve a T3Executable or T3ExecutableLazy.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000315 | Alert: Unexpected failure of T3ExecutableLazy, th0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000316 | Critical: enableWatchDog() is not permitted from within a server.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000317 | Critical: disableWatchDog() is not permitted from within a server.
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000318(retired) | Info: Bound WARManager at name0
Description | Deprecated functionality
Cause | Deprecated functionality
Action | Deprecated functionality
BEA-000319(retired) | Info: Prevented user "user0" from submitting to topic "topic1"
Description | Not used
Cause | Not used
Action | Not used
BEA-000320 | Info: Error creating Runtime MBean for Execute Queue name
Description | Error creating Runtime MBean for Execute Queue
Cause | An internal system error
Action | Please contact support with the server logs
BEA-000321 | Info: Error creating Runtime MBean for Timer t
Description | Error creating Runtime MBean for Timer
Cause | Internal system error
Action | Please contact support with the server logs
BEA-000322(retired) | Info: Error creating Runtime MBean for Server t
Description | Not used
Cause | Not used
Action | Not used
BEA-000323 | Info: Error creating Runtime MBean for JVM t
Description | Error creating Runtime MBean for JVM
Cause | Internal system error
Action | Please contact support with the server logs
BEA-000324 | Info: License allows full strength (domestic) SSL.
Description | The license.bea file allows full strength (domestic) SSL.
Cause | The license.bea file has a tag for LICENSE PRODUCT= "SSL/Domestic"
Action | None required as this is an informational message.
BEA-000325 | Info: License allows low strength (export) SSL.
Description | The license.bea file allows low strength (export) SSL.
Cause | The license.bea file does not have a tag for LICENSE PRODUCT= "SSL/Domestic" but does have a tag for LICENSE PRODUCT= "SSL/Export"
Action | Verify that low strength (export) SSL support is the desired behavior.
BEA-000326 | Notice: thread0 delay listening for port1 seconds
Description | Use this property in the cluster environment. The http request handling will be delayed so that the current node will have more time to acknowledge the existence of other cluster members.
Cause | "ListenDelaySecs" is present within the directive
Action | Adjust the delay time or remove it from directive
BEA-000327 | Notice: Starting WebLogic Admin Server "servername0" for domain "domainname1"
Description | The server is starting as an admin server.
Cause | The server was started as an admin server (i.e. the -Dweblogic.admin.host switch is not present).
Action | No action required.
BEA-000328 | Notice: Starting WebLogic Managed Server "servername0" for domain "domainname1"
Description | The server is starting as a managed server.
Cause | The server was started as a managed server (i.e. the -Dweblogic.admin.host switch was used to refer the managed server to what admin server to boot from).
Action | No action required.
BEA-000329 | Notice: Started WebLogic Admin Server "servername0" for domain "domainname1" running in Production Mode
Description | The server started in a mode that is optimized for production use.
Cause | The production-mode of the server is enabled.
Action | Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
BEA-000330 | Notice: Started WebLogic Managed Server "servername0" for domain "domainname1" running in Production Mode
Description | The server started in a mode that is optimized for production use.
Cause | The production-mode of the server is enabled.
Action | Set the weblogic.ProductionModeEnabled property of the domain in the startup script file to change the server mode.
BEA-000331 | Notice: Started WebLogic Admin Server "servername0" for domain "domainname1" running in Development Mode
Description | The server started in a mode that is optimized for development use.
Cause | The production-mode of the server is disabled (default).
Action | Set the ProductionModeEnabled property of the domain in the configuration script to change the server mode.
BEA-000332 | Notice: Started WebLogic Managed Server "servername0" for domain "domainname1" running in Development Mode
Description | The server started in a mode that is optimized for development use.
Cause | The production-mode of the server is disabled (default).
Action | Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
BEA-000333 | Warning: Queue usage is greater than QueueLengthThresholdPercent "percent%" of the maximum queue size. We'll try to allocate ThreadsIncrease "threads" thread(s) to help.
Description | All threads in the queue are busy. No idle threads are available.
Cause | The server is very busy.
Action | Review the execute queue settings.
BEA-000334(retired) | Warning: "percent%" of starting server free memory available.
Description | The Server selfhealth monitoring service has detected free memory less than the specified percentage
Cause | The Server selfhealth monitoring service has detected free memory less than the specified percentage
Action | The server is running at less that the specified memory threshold. Monitor the server for performance and memory related errors.
BEA-000335 | Warning: Percent of starting server free memory is now at "percent%". This is less than the configured threshold of "threshold%". We will try to garbage collect, but you may consider rebooting.
Description | The servers free memory is less than the configured threshold. We will try to garbage collect to free up memory.
Cause | The servers free memory is less than the configured threshold
Action | If the server is running low on memory and does not have enough memory to handle the load you may consider rebooting with the more memory
BEA-000336 | Warning: After garbage collecting, server free memory is at "percent%".
Description | Displays the server free memory after a force GC
Cause | Displays the server free memory after a force GC
Action | No action is needed
BEA-000337 | Error: name has been busy for "elapsedTime" seconds working on the request "curReq", which is more than the configured time (StuckThreadMaxTime) of "maxTime" seconds.
Description | It was found that a thread is busy for longer than the configured warning timeout.
Cause | Either the server is extremely busy or the thread is hung.
Action | Monitor the method the hung thread is running. Use the console monitor execute request feature or take a thread-dump (weblogic.Admin THREAD_DUMP).
BEA-000338 | Emergency: All threads appear busy, we will try to help by allocating (ThreadsIncrease) "count" more thread(s).
Description | The server appears extremely busy or the application is deadlocked.
Cause | All threads in the default queue are busy.
Action | Monitor the methods the hung threads are running. Use the console monitor execute request feature or take a thread-dump (weblogic.Admin THREAD_DUMP).
BEA-000339 | Info: name has become "unstuck".
Description | A thread previously struck is now available
Cause | A thread previously struck is now available
Action | No action needed
BEA-000340 | 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-000341 | 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-000342 | Emergency: Unable to initialize the server: msg
Description | The server could not be initialize fully.
Cause | An exception occurred during the server initialization.
Action | Analyze the weblogic.log to determine the cause due to which the server did not initialize completely.
BEA-000343 | Warning: Health monitor for "name" failed to register because of exception "e".
Description | An internal problem prevented the health monitoring subsystem to be started properly.
Cause | Please refer to the exception printed in the log message.
Action | Please refer to the exception printed in the log message.
BEA-000344 | Warning: Health monitor for "name" failed to unregister because of exception "e".
Description | An internal problem prevented the health monitoring subsystem to be started properly.
Cause | Please refer to the exception printed in the log message.
Action | Please refer to the exception printed in the log message.
BEA-000349 | 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-000350 | Emergency: Unable to create a server socket on Channel channelName for: listenAddress0, port: port1. ex2 Perhaps the address listenAddress0 is incorrect or another process is using port port1.
Description | Could not create a server socket.
Cause | Perhaps the address is incorrect or another process is using the port.
Action | Make sure the port information is correct and no other process uses the port (e.g. using netstat).
BEA-000351 | Emergency: Unable to create a server socket on Channel channelName for port: port0. ex1 Perhaps another process is using port port0.
Description | Could not create a server socket.
Cause | Perhaps another process is using the port.
Action | Make sure the port information is correct and no other process uses the port (e.g. using netstat).
BEA-000352 | Notice: Thread "thread0" stopped listening on port port1
Description | The server is no longer listening on the respective port.
Cause | The server is being shutdown.
Action | No action required.
BEA-000353 | Notice: Thread "thread0" stopped listening on port port1, ip address addr2
Description | The server is no longer listening on the respective port/address.
Cause | The server is being shutdown.
Action | No action required.
BEA-000354 | Notice: Thread "thread0" listening on port port1
Description | The server is listening on the respective port.
Cause | Server was started.
Action | No action required.
BEA-000355 | Notice: Thread "thread0" listening on port port1, ip address addr2
Description | The server is listening on the respective port/address.
Cause | The server was started.
Action | No action required.
BEA-000356 | Notice: Starting WebLogic Independent Managed Server "servername0" for domain "domainname1"
Description | The server was started with managed server independence enabled. This allows the managed server to restart without the administration server running.
Cause | Server started with the managed server independence mode enabled.
Action | No action required.
BEA-000357 | Notice: Started WebLogic Independent Managed Server "servername0" for domain "domainname1" running in Development Mode
Description | The server was started in development mode. The managed server will restart without the administration server running. Managed server independence is enabled.
Cause | Server started with the managed server independence mode enabled.
Action | No action required.
BEA-000358 | Notice: Started WebLogic Independent Managed Server "servername0" for domain "domainname1" running in Production Mode
Description | The server started in a mode that is optimized for production use.
Cause | The production-mode of the server is enabled.
Action | Set the ProductionModeEnabled property of the domain in the configuration file to change the server mode.
BEA-000359 | Emergency: Either the ListenPort on the ServerMBean or the ListenPort on the SSLMBean has to be enabled by setting its associated ListenPortEnabled field to true
Description | Neither the plain, not the ssl port are enabled.
Cause | Neither the plain, not the ssl port are enabled.
Action | Enable at least one port to allow user traffic to the server.
BEA-000360 | Notice: Server started in state mode
Description | Server in SUSPEND state.
Cause | The startup mode was set to SUSPENDED.
Action | No action required.
BEA-000361 | Critical: Server failed during initialization of server subsystem ==> serverService
Description | The server could not be started due to problems starting a subsystem.
Cause | Please refer to the log entry to further analyze the problem.
Action | Please refer to the log entry to further analyze the problem.
BEA-000362 | Critical: Server subsystem "serverService" failed
Description | A subsystem of the server failed.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000363 | Critical: Server subsystem "serverService" failed during suspend
Description | A subsystem of the server failed during the suspend operation.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000364 | Critical: Server failed during initialization. Exception:e
Description | The server failed to start due to initialization problems.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000365 | Notice: Server state changed to state
Description | The control state of the server changed.
Cause | The server progressed through the startup or shutdown sequence.
Action | No action required.
BEA-000366 | Critical: Server failed to shutdown. Exception: e
Description | The server failed to shutdown due to an exception.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000367 | Info: Start monitoring handshake with local NodeManager complete.
Description | The handshake between the starting server and the nodemanager completed.
Cause | Server is starting.
Action | No action required.
BEA-000368 | Error: Start Monitoring handshake with local NodeManager failed, Exception - arg.
Description | The handshake between the starting server and the nodemanager failed.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000369 | Info: Stop Monitoring handshake with local NodeManager complete.
Description | The handshake between the stopping server and the nodemanager completed.
Cause | The server was suspended or shutdown.
Action | No action required.
BEA-000370 | Error: Stop Monitoring handshake with local NodeManager failed, Exception - arg.
Description | The handshake between the stopping server and the nodemanager failed.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000371 | Error: Error in Server Shutdown: th0.
Description | An unexpected error occurred during the server shutdown process.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000372 | 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.
Action | Check if this was done on purpose.
BEA-000373 | Warning: An attempt to set the number of threads on execute queue "name" to count could not be honored for it exceeds the configured maximum of max. The server is very busy and automatically increased the number of available threads to the maximum configured.
Description | The server is very busy and automatically increased the number of available threads to the maximum configured.
Cause | The server is very busy or an application is deadlocked.
Action | Set the ThreadsMaximum attribute of the ExecuteQueue "name" via the console or in the configuration file.
BEA-000374 | Notice: Waiting for ExecuteQueue name to finish count pending requests
Description | Waiting for ExecuteQueue name to finish count pending requests
Cause | Server found pending requests in one of the execute queues while suspending. The server will wait for the requests to complete.
Action | No action is required.
BEA-000375 | Error: Error starting MDB t
Description | The attempt to start processing message driven beans failed during server startup.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000376 | Critical: \n****************************************************\nServer failed to gracefully shutdown.\nUse Force shutdown command to bring the server down\n****************************************************\ne
Description | The server failed to gracefully shutdown due to an exception.
Cause | Please inspect the log file for indications of the root cause of the failure.
Action | Please inspect the log file for indications of the root cause of the failure.
BEA-000377 | Info: Starting WebLogic Server with name Version version from vendor
Description | The first message emitted on server startup.
Cause | Server is starting.
Action | No action is needed.
BEA-000378 | Notice: Server failed to shutdown within the configured timeout of timeout seconds. The server process will exit now.
Description | Force shutdown did not complete within the configured timeout period. The server process will exit.
Cause | Force shutdown is taking too long to complete.
Action | No action is needed.
BEA-000379 | Notice: Cannot shutdown the server, the request was from an unauthorized user (Principal).
Description | The server refused to shutdown since the command came from an unauthorized user.
Cause | The server refused to shutdown since the command came from an unauthorized user.
Action | Only users within the Administrators group can shutdown the server. Please retry the command with a user having admin credentials.
BEA-000380 | Notice: Cannot start the server, the request was from an unauthorized user (Principal).
Description | The server start is refused since the command came from an unauthorized user.
Cause | The server start is refused since the command came from an unauthorized user.
Action | Only authorized users can start the server. Please retry the command with a user having admin credentials.
BEA-000381 | Notice: Cannot suspend the server, the request was from an unauthorized user (Principal).
Description | The server suspension is refused since the command came from an unauthorized user.
Cause | The server suspension is refused since the command came from an unauthorized user.
Action | Only authorized users can suspend the server. Please retry the command with a user having appropriate credentials.
BEA-000382 | Notice: Cannot resume the server, the request was from an unauthorized user (Principal).
Description | The server resumption is refused since the command came from an unauthorized user.
Cause | The server resumption is refused since the command came from an unauthorized user.
Action | Only authorized users can resume the server. Please retry the command with a user having appropriate credentials.
BEA-000383 | Notice: Cannot get the licenses of the server, the request was from a nameless user (Principal).
Description | A nameless user cannot get the licenses of WebLogic Server.
Cause | The request for server licenses is refused because the request came from a nameless user (Principal).
Action | Only authorized users can get the licenses of a server. Please retry the request with an authorized user.
BEA-000384 | Notice: Cannot get the licenses of the server, the request was from an anonymous user (Principal).
Description | An anonymous user cannot get the licenses of WebLogic Server.
Cause | The request for server licenses is refused because the request came from an anonymous user.
Action | Only authorized, non-anonymous users can get the licenses of a server. Please retry the request with an authorized user.
BEA-000385 | Notice: Cannot get the server states, the request was from an anonymous user (Principal).
Description | An anonymous user cannot get the states of servers.
Cause | The request for server states is refused because the request came from an anonymous user.
Action | Only authorized, non-anonymous users can get the states of servers. Please retry the request with an authorized user.
BEA-000386 | Notice: Cannot get the server version, the request was from an anonymous user (Principal).
Description | An anonymous user cannot get the versions of servers.
Cause | The request for server versions is refused because the request came from an anonymous user.
Action | Only authorized, non-anonymous users can get the versions of servers. Please retry the request with an authorized user.
BEA-000387 | Notice: Cannot get the server thread dump, the request was from an anonymous user (Principal).
Description | An anonymous user cannot get thread dumps of servers.
Cause | The request for server thread dumps is refused because the request came from an anonymous user.
Action | Only authorized, non-anonymous users can get thread dumps of servers. Please retry the request with an authorized user.
BEA-000388 | Notice: JVM called WLS shutdown hook. The server will force shutdown now
Description | JVM called WLS shutdown hook. The server will force shutdown now
Cause | JVM called WLS shutdown hook. The server will force shutdown now
Action | No action is needed.
BEA-000389 | Warning: The configured custom SSL TrustManager, arg0, is not an implementation of TrustManagerJSSE.
Description | The custom SSL TrustManager must be an implementation of TrustManagerJSSE, but the configured TrustManager is not.
Cause | The wrong trust manager has been configured, or the wrong interface was implemented.
Action | Verify the class of the configured TrustManager, and the interface implemented.
BEA-000398 | Critical: The server became busy and all the thread were stuck beyond the acceptable configured stuck thread duration. We will reject any new client requests and commence rejection of any pending requests in the queue to enable failover or a gracefull failure. Then we will force suspend the server after waitTime seconds.
Description | The server became busy and all the thread were stuck beyond the acceptable configured stuck thread duration. We will reject any new client requests and commence rejection of any pending requests in the queue to enable failover or a gracefull failure. Then we will force suspend the server after waitTime seconds. This will remove the server from the cluster and put it in a state where you can gather some diagnostics like threaddumps but the threads may have moved if some time has past.
Cause | The server became busy or stuck and the thread were stuck beyond the acceptable configured stuck thread duration.
Action | Try to see why the server threads are stuck. Thread dumps/state analysis from this server and the external endpoints where the requests were being made to will show the root cause of the problem.
BEA-000399 | Notice: Aborting the Graceful shutdown as Forced shutdown of server already started.
Description | Graceful shutdown did not complete within the configured timeout period. The server process is now forced shutdown.
Cause | Graceful shutdown is taking too long to complete.
Action | No action is needed.