The Diameter.Core1.0 catalog contains messages in the range
BEA340000 - BEA341000. Messages in this catalog are part of the
com.bea.wcp.diameter.i18n
Internationalization package and the com.bea.wcp.diameter.i18n Localization package.
|
BEA-340000
|
Notice: WebLogic Diameter Node "name" has started
|
Description
| WebLogic Diameter Node "name" has started |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340002
|
Error: WebLogic Diameter Node "name" failed to start
|
Description
| WebLogic Diameter Node "name" failed to start |
|
|
BEA-340003
|
Notice: WebLogic Diameter Node "name" has been stopped
|
Description
| WebLogic Diameter Node "name" has been stopped |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340004
|
Error: WebLogic Diameter Node "name" failed to stop
|
Description
| WebLogic Diameter Node "name" failed to stop |
|
|
BEA-340005
|
Error: Invalid WebLogic Diameter configuration file "name": msg
|
Description
| Invalid WebLogic Diameter configuration file "name": msg |
|
|
BEA-340006
|
Notice: Loaded WebLogic Diameter configuration from "name"
|
Description
| Loaded WebLogic Diameter configuration from "name" |
|
|
BEA-340007
|
Error: Invalid WebLogic Diameter applications configuration file "name": msg
|
Description
| Invalid WebLogic Diameter applications configuration file "name": msg |
|
|
BEA-340008
|
Notice: Loaded WebLogic Diameter applications configuration from "name"
|
Description
| Loaded WebLogic Diameter applications configuration from "name" |
|
|
BEA-340009
|
Notice: Incoming connections from arbitrary (dynamic) peers enabled
|
Description
| Incoming connections from arbitrary (dynamic) peers enabled |
|
|
BEA-340010
|
Error: Exception in method rcvMessage of session class "class"
|
Description
| Exception in method rcvMessage of session class "class" |
|
|
BEA-340011
|
Error: Exception in method rcvMessage of application class "class"
|
Description
| Exception in method rcvMessage of application class "class" |
|
|
BEA-340012
|
Notice: Peer "host" transitioned from state "fromState" to "toState"
|
Description
| Peer "host" transitioned from state "fromState" to "toState" |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340013
|
Warning: Failed to connect to peer "host"
|
Description
| Failed to connect to peer "host" |
|
Cause
| Unable to connect to configured peer |
|
Action
| Check peer configuration |
|
|
BEA-340014
|
Warning: Transaction not found for answer with hop-by-hop id "id" from peer "host"
|
Description
| Transaction not found for answer with hop-by-hop id "id" from peer "host" |
|
Cause
| An answer was probably already received for the pending request |
|
Action
| Check Diameter application |
|
|
BEA-340015
|
Warning: Capabilities exchange with peer "host" failed because there were no common applications
|
Description
| Capabilities exchange with peer "host" failed because there were no common applications |
|
Cause
| There were no common Diameter applications with peer "host" |
|
Action
| Check Diameter application configuration |
|
|
BEA-340016
|
Warning: Capabilities exchange with peer "host" failed because there was no common security
|
Description
| Capabilities exchange with peer "host" failed because there was no common security |
|
Cause
| There were no common security with peer "host" |
|
Action
| Check Diameter security configuration |
|
|
BEA-340017
|
Error: Unable to load or initialize application "name"
|
Description
| Unable to load or initialize application "name" |
|
Cause
| An exception was thrown while initialization the application "name" |
|
Action
| Check application class or configuration |
|
|
BEA-340018
|
Notice: Loaded application "name"
|
Description
| Loaded application "name" |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340019
|
Error: Duplicate definition in configuration for peer "name"
|
Description
| Duplicate definition in configuration for peer "name" |
|
Cause
| There was a duplicate definition for peer "name" in the Diameter configuration file |
|
Action
| Check configuration file for duplicate peer definition |
|
|
BEA-340020
|
Warning: Unable to stop peer "name"
|
Description
| Unable to stop peer "name" |
|
|
BEA-340021
|
Error: Route configuration invalid - no definition for peer "name"
|
Description
| Route configuration invalid - no definition for peer "name" |
|
Cause
| The Diameter configuration file contained invalid route information because the peer "name" was not found |
|
Action
| Check Diameter route configuration |
|
|
BEA-340022
|
Error: Duplicate route configuration for realm "name"
|
Description
| Duplicate route configuration for realm "name" |
|
Cause
| The Diameter configuration file contained duplicate route information for realm "name" |
|
Action
| Check Diameter route configuration |
|
|
BEA-340023
|
Error: Duplicate definition in configuration for application "name"
|
Description
| Duplicate definition in configuration for application "name" |
|
Cause
| The Diameter configuration file contained a duplicate defintion for application "name" |
|
Action
| Check Diameter application configuration |
|
|
BEA-340024
|
Notice: Destination host for Diameter Sh application requests is "host"
|
Description
| Destination host for Diameter Sh application requests is "host" |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340025
|
Notice: Destination realm for Diameter Sh application is "realm"
|
Description
| Destination realm for Diameter Sh application is "realm" |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340026
|
Info: Message received for connection: connection : [msg]
|
Description
| Message received for connection: connection : [msg] |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340027
|
Info: Sending message for connection: connection : [msg]
|
Description
| Sending message for connection: connection : [msg] |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340028
|
Warning: Invalid message received: err : msg
|
Description
| Invalid message received: err : msg |
|
Cause
| An invalid message was received |
|
|
BEA-340029
|
Notice: Closing connection: connection
|
Description
| Closing connection: connection |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340030
|
Error: I/O error while sending message for connection: connection
|
Description
| I/O error while sending message for connection: connection |
|
|
BEA-340031
|
Warning: Cannot forward message because relay application was not found
|
Description
| Cannot forward message because relay application was not found |
|
Cause
| A Diameter message with realm-based routing could not be forwarded because a relay application was not configured. |
|
Action
| Check Diameter configuration to make sure that a relay application is defined. |
|
|
BEA-340032
|
Error: I/O error while forwarding message for connection: connection
|
Description
| I/O error while forwarding message for connection: connection |
|
|
BEA-340033
|
Error: Received non-CER as initial request from connection: connection
|
Description
| Received non-CER as initial request from connection: connection |
|
|
BEA-340034
|
Error: Error while processing received message
|
Description
| Error while processing received message |
|
|
BEA-340035
|
Warning: Error while closing connection: connection
|
Description
| Error while closing connection: connection |
|
|
BEA-340036
|
Warning: Capabilities-Exchange-Request rejected because peer "peer" is unknown
|
Description
| Capabilities-Exchange-Request rejected because peer "peer" is unknown |
|
|
BEA-340037
|
Error: Cannot resolve address "addr" for peer "peer"
|
Description
| Cannot resolve address "addr" for peer "peer" |
|
Cause
| The peer configuration contained an address that could not be resolved |
|
Action
| Check Diameter configuration for peer "peer" |
|
|
BEA-340038
|
Notice: Received Disconnect-Peer-Request from peer "peer" with disconnect cause "cause"
|
Description
| Received Disconnect-Peer-Request from peer "peer" with disconnect cause "cause" |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340039
|
Debug: Peer "host" transitioned from watchdog state "fromState" to "toState"
|
Description
| Peer "host" transitioned from watchdog state "fromState" to "toState" |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340040
|
Notice: Closing peer "host" due to watchdog expiration
|
Description
| Closing peer "host" due to watchdog expiration |
|
Cause
| This is an informational message. |
|
Action
| Make sure remote peer supports Device Watchdog Request messages |
|
|
BEA-340041
|
Notice: Scheduled timer task to reconnect to peer "host" in delay seconds
|
Description
| Scheduled timer task to reconnect to peer "host" in delay seconds |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340042
|
Error: Route configuration for realm "realm" invalid: "server" element not supported for LOCAL action type
|
Description
| Route configuration for realm "realm" invalid: "server" element not supported for LOCAL action type |
|
Cause
| The "server" element is not supported for LOCAL route configuration |
|
Action
| Check configuration file for invalid route configuration |
|
|
BEA-340043
|
Error: Route configuration for realm "realm" invalid: "server" element required for PROXY, RELAY, and REDIRECT action types
|
Description
| Route configuration for realm "realm" invalid: "server" element required for PROXY, RELAY, and REDIRECT action types |
|
Cause
| The "server" element is required for PROXY, RELAY, or REDIRECT route configuration |
|
Action
| Check configuration file for invalid route configuration |
|
|
BEA-340044
|
Error: Default route configuration invalid: "server" element not supported for LOCAL action type
|
Description
| Default route configuration invalid: "server" element not supported for LOCAL action type |
|
Cause
| The "server" element is not supported for LOCAL route configurations |
|
Action
| Check configuration file for invalid default route configuration |
|
|
BEA-340045
|
Error: Default route configuration invalid: "server" element required for PROXY, RELAY, and REDIRECT action types
|
Description
| Default route configuration invalid: "server" element required for PROXY, RELAY, and REDIRECT action types |
|
Cause
| The "server" element is required for PROXY, RELAY, or REDIRECT route configurations |
|
Action
| Check configuration file for invalid default route configuration |
|
|
BEA-340046
|
Debug: Received message with unknown application id "id" from peer "host"
|
Description
| Received message with unknown application id "id" from peer "host" |
|
Cause
| Another peer has sent a message with an unknown application id |
|
Action
| Check peer configuration |
|
|
BEA-340047
|
Notice: Failed to connect to peer "host": msg
|
Description
| Failed to connect to peer "host": msg |
|
Cause
| Peer connection failed |
|
Action
| Check peer configuration |
|
|
BEA-340048
|
Notice: Application appName: msg
|
Description
| Application appName: msg |
|
Cause
| The Diameter application logged a message |
|
Action
| This is an informational message, so no action is required |
|
|
BEA-340049
|
Info: Dispatching locally generated answer: [msg]
|
Description
| Dispatching locally generated answer: [msg] |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340050
|
Info: Dispatching locally generated answer to relay application: [msg]
|
Description
| Dispatching locally generated answer to relay application: [msg] |
|
Cause
| This is an informational message. |
|
Action
| No action is required. |
|
|
BEA-340051
|
Error: The Diameter Message FileStreamHandler is unable to open the access logfile for Diameter messages msg due to t.
|
Description
| Failed to create an access log msg for Diameter messages due to t. |
|
Cause
| The filepath specified for the diameter messages access log is invalid or the server process cannot write to the diameter messages access log msg. |
|
Action
| Specify a valid file path for the diameter messages access log. |
|
