RJVM Subsystem Message Catalog

e-docs > WebLogic Server > Messages > RJVM

RJVM Subsystem Messages

The RJVM 1.0 catalog contains messages in the range 500 - 599. Messages in this catalog are part of the weblogic.rjvm Internationalization package and the weblogic.i18n Localization package.

000500

Debug:

Description	Uncatalogued debug message - please do not change
Cause	Debugging - please do not change.
Action	No action required.

000501

Info: Peergone send failed - target unreachable

000502

Info: Peergone send failed - target already gone

000503

Error: Incoming message header or abbreviation processing failed\n e

Description	While processing an incoming message an error was encountered. It is likely that the message was corrupted.
Cause	While processing an incoming message an error was encountered. It is likely that the message was corrupted.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000504

Error: Unmarshal exception: received illegal command code:\ne

Description	A message containing an invalid command code was received. This message cannot be processed.
Cause	A message containing an invalid command code was received. This message cannot be processed. One of the possible reasons is that the message was corrupted in transit.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000505

Error: Peer did not send us a valid heartbeat interval - using the default heartbeat specified as a property.

Description	A message containing an invalid heartbeat interval was received. The default heartbeat interval will be used for communication with the peer.
Cause	The incoming message has an invalid heartbeat interval. This is either due to message corruption in transit or to an invalid choice for the heartbeat interval on the peer attempting to establish communication with this JVM.
Action	If the peer attempting to establish communication is over-riding the default heartbeat interval, please ensure that a valid interval is used. If not, please contact BEA support with the server logs and configuration.

000506

Error: Closing: connection because of problem

Description	While processing an incoming message an error was encountered. As a result, communication with the corresponding peer will be terminated.
Cause	This JVM has received an incoming message that is incompatible with the way the protocols are supposed to work.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000507

Warning: Could not create/send request to close duplicate connection message\n e

Description	In attempting to close a duplicate connection from a peer JVM, an error was encountered.
Cause	Creation of the message to request closing a connection or sending of the message caused an IO error.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000508

Error: Id: id in use by: o, can not install ri

Description	The id id is already associated and in use by o and hence cannot be used in associated with ri.
Cause	The id id is already associated and in use by o and hence cannot be used in associated with ri.
Action	Please ensure that unique id's are used in registeration.

000509

Error: Finder not initialized

Description	This JVM does not have a finder associated with it. It will not be possible to dispatch messages through this JVM without a finder.
Cause	This JVM is being created without a valid finder.
Action	Please ensure that a valid finder is used when creating this JVM.

000510

Warning: Unsolicited response: resp

Description	This incoming response could not be dispatched since there is no corresponding request.
Cause	A duplicate response has been received for a request that has already received its response.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000511

Warning: Unsolicited error response for: rid

Description	This incoming error response could not be dispatched since there is no corresponding request.
Cause	A duplicate error response has been received for a request that has already received its response or its error response.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000512

Info: New heartbeat period: val1 is different from established heartbeat period: val2 - using established heartbeat period

000513

Info: Failure in heartbeat trigger for RJVM: id\n t.

Description	This is usually a temporary failure.
Cause	This failure indicates a temporary failure in the heartebeat trigger mechanism.
Action	No action is necessary. This is usually a temporary failure.

000514

Error: openConnection() failed\n e

Description	A HTTP connection could not be created.
Cause	Possible causes are an invalid target address or the target not being active or reachable.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000515

Error: execute failed\n t

Description	A failure was encountered when handling the incoming HTTP message.
Cause	A failure was encountered when handling the incoming HTTP message.
Action	This is in all likelihood a temporary situation. No user action is necessary. If this situation continues, please contact BEA support with the server logs and configuration.

000516

Error: The HTTP Scavenger could not schedule a trigger\n e

Description	A failure was encountered when scheduling a scavenger of idle connections.
Cause	A failure was encountered when scheduling a scavenger of idle connections.
Action	This failure indicates a critical condition of the Timer subsystem of the WebLogic server. Please contact BEA support with the server logs and configuration.

000517

Debug:

Description	Uncatalogued debug message - please do not change
Cause	Debugging - please do not change.
Action	No action required.

000518

Debug:

Description	Uncatalogued debug message - please do not change
Cause	Debugging - please do not change.
Action	No action required.

000519

Warning: Unable to connect to a remote server on address address and port port with protocol protocol. The Exception is t

Description	Unable to connect to a remote server on address address and port port with protocol protocol. The Exception is t
Cause	The target is either not reachable or is not active.
Action	Please ensure that the target is active.

000520

Info: Network Configuration\ninfo

Description

This is a summary of network configuration settings. The default channel and default admin channel base these settings on server, ssl, and cluster configuration. Additional channels base settings on this configuration as well as network channel and network access point configuration.\n For more information, refer to the administration documentation and javadoc.\n

000521

Emergency: No default listen port was enabled for the server. The default plain-text and/or default SSL port must be enabled in addition to those on the optional configured channels. If the plain text port is disabled, ensure that SSL is configured and that the SSL port is enabled.

Description	No default listen port was enabled for the server. The default plain-text and/or default SSL port must be enabled in addition to those on the optional configured channels.
Cause	No default listen port was enabled for the server. The default plain-text and/or default SSL port must be enabled in addition to those on the optional configured channels.
Action	No default listen port was enabled for the server. If the plain text port is disabled, ensure that SSL is configured and that the SSL port is enabled.

000522

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 "address1" port port conflicts with channel "channel2" address "address2" port port.

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 "address1" port port conflicts with channel "channel2" address "address2" port port.
Cause	The server is configured to listen on two ports that have the same port number and IP address. Channel "channel1" address "address1" port port conflicts with channel "channel2" address "address2" port port.
Action	Please ensure that the address identities [ListenAddress and ListenPort combinatione] are distinct and unique.