The RJVM1.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: msg
|
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 ids 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: msg\nt
|
Description
| Uncatalogued debug message - please do not change |
|
Cause
| Debugging - please do not change. |
|
Action
| No action required. |
|
|
000518
|
Debug: msg\nt
|
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. |
|
|
000523
|
Info: none
|
|
000524
|
Info: Network Channel
|
|
000525
|
Info: Listen Address
|
|
000526
|
Info: Listen Port
|
|
000527
|
Info: SSL Listen Port
|
|
000529
|
Info: External DNS Name
|
|
000530
|
Info: Cluster Address
|
|
000531
|
Info: Protocol(s)
|
|
000532
|
Info: Tunneling Enabled
|
|
000533
|
Info: Outgoing Enabled
|
|
000534
|
Info: Admin Traffic Only
|
|
000535
|
Info: Admin Traffic OK
|
|
000536
|
Info: Channel Weight
|
|
000537
|
Info: Accept Backlog
|
|
000539
|
Info: Login Timeout
|
|
000540
|
Info: Login Timeout SSL
|
|
000541
|
Info: Max Message Size HTTP
|
|
000542
|
Info: Message Timeout HTTP
|
|
000543
|
Info: Max Message Size COM
|
|
000544
|
Info: Message Timeout COM
|
|
000545
|
Info: Max Message Size IIOP
|
|
000546
|
Info: Message Timeout IIOP
|
|
000547
|
Info: Idle Timeout IIOP
|
|
000548
|
Info: Max Message Size T3
|
|
000549
|
Info: Message Timeout T3
|
|
000550
|
Info: ms
|
|
000551
|
Info: secs
|
|
000552
|
Info: Administrator
|
Description
| name of Administrator channel |
|
|
000553
|
Info: Default
|
Description
| name of Default channel |
|
|
000554
|
Info: not configured
|
|
000555
|
Info: Tunneling Timeout
|
|
000556
|
Info: Tunneling Ping
|
|
000557
|
Info: Cluster Participant
|
|
000558
|
Info: Cluster Name
|
|
000559
|
Info: Cluster Multicast Address
|
|
000560
|
Info: Cluster Multicast Interface
|
|
000561
|
Info: Cluster Multicast Port
|
|
000562
|
Info: Cluster Multicast TTL (max hops)
|
|
000563
|
Info: Cluster Multicast Send Delay
|
|
000564
|
Info: Cluster Multicast Buffer Size
|
|
000565
|
Info: Native Socket IO Enabled
|
|
000566
|
Info: Java Socket IO Thread Pool %
|
|
000567
|
Info: Java Socket IO Timeout Min
|
|
000568
|
Info: Java Socket IO Timeout Max
|
|
000569
|
Info: Reverse DNS Allowed
|
|
000570
|
Info: Network Configuration for Channel "name"\n Listen Address\t\t address\n Public Address\t\t extAddress\n Http Enabled\t\t httpenabled\n Tunneling Enabled\t tunneling\n Outbound Enabled\t outbound\n Admin Traffic Enabled\t admin
|
Description
| This is a summary of network configuration settings. The default settings are based on server, ssl, and cluster configuration. Additional channels base settings on this configuration as well as network access point configuration.\n For more information, refer to the administration documentation and javadoc.\n |
|
|
000571
|
Debug: Network Configuration Detail for Channel "name"\n Channel Weight\t\t weight\n Accept Backlog\t\t backlog\n Login Timeout\t\t loginTimeoutms\n Max Message Size\t maxMessage\n Message Timeout\t messageTimeouts\n Idle Timeout\t\t idleTimeouts\n Tunneling Timeout\t tunnelTimeouts\n Tunneling Ping\t\t tunnelPing>s
|
Description
| These are the detailed network configuration settings. The default settings are based on server, ssl, and cluster configuration. Additional channels base settings on this configuration as well as network access point configuration.\n For more information, refer to the administration documentation and javadoc.\n |
|
|
000572
|
Error: The server rejected a connection attempt problem probably due to an incorrect firewall configuration or admin command.
|
Description
| While processing a bootstrap message the server could not reconcile the clients configuration with its own internal configuration. |
|
Cause
| The incoming connection attempt was probably made through an address translating firewall. WebLogic Server needs to be correctly configured for this to work. This message can also occur if an admin connection attempt, requiring admin-level security, is made on a non-admin port. |
|
Action
| Configure the public and private addresses for this WebLogic Server instance to reflect the configuration of the firewall. The private address is the actual address that the server is running on. The public address is the address that external clients use to connect. |
|
