The WLSS.Trace1.0 catalog contains messages in the range
BEA331800 - BEA331999. Messages in this catalog are part of the
com.bea.wcp.sip.i18n
Internationalization package and the com.bea.wcp.sip.i18n Localization package.
|
BEA-331801
|
Info: SIP Tracer: tracerName Message: null
|
Description
| Tracer tracerName matched. |
|
Cause
| A tracer defined to trap SIP messages triggered generation of this message. |
|
|
BEA-331802
|
Info: SIP Tracer: tracerName Message: msgDescription
|
Description
| Tracer tracerName matched for SIP message msgDescription |
|
Cause
| A tracer defined to trap SIP messages triggered generation of this message. |
|
|
BEA-331803
|
Info: SIP Tracer: tracerName Message: msgDescription
|
Description
| Tracer tracerName matched for SIP message. Detailed message data : msgDescription |
|
Cause
| A tracer defined to trap SIP messages triggered generation of this message. |
|
|
BEA-331820
|
Warning: Message tracing default queue name not found name
|
Description
| The default queue name used by managed server message tracing subsystem was not found name |
|
Cause
| This is the queue name to be used by the message handler for message tracing. If the queue is not found, the server uses the default server execute queue instead. |
|
Action
| Add the execute queue definition to the config.xml file. |
|
|
BEA-331821
|
Warning: Dropped howMany messages due to queue queue overload
|
Description
| The message tracing subsystem dropped howMany messages due to queue queue overload |
|
Cause
| This is caused either by a high volume of messages, or an incorrect message tracer setup that allows too many messages to be logged. |
|
Action
| Modify the execute queue queue definition in the config.xml file or modify the tracer configuration to limit the number of matching messages. |
|
|
BEA-331822
|
Warning: Unable to locate localizer class class. Failed to localize message.
|
Description
| Failed to localize message of type class . Please make sure your classpath is correct. |
|
Cause
| This is caused by invalid CLASSPATH settings. |
|
Action
| Please ensure that the WebLogic SIP Server CLASSPATH is correct. |
|
|
BEA-331823
|
Error: Could not recognize token token. Allowed values are : allowed
|
Description
| Could not recognize token token. Allowed values are : allowed |
|
Cause
| WebLogic SIP Server could not parse the specified token sequence. Please ensure that the token values are correct. |
|
Action
| Check and correct the syntax of the token. |
|
|
BEA-331824
|
Warning: Unsupported charset parameter [encoding] in content-type header. Refer charset(s) supported by Java Platform.
|
Description
| Unsupported charset parameter [encoding] in content-type header. Refer charset(s) supported by Java Platform. |
|
Cause
| This is caused by using unsupported charset as a parameter in content-type header. |
|
Action
| Please ensure that supported charset parameter is used in content-type header. |
|
|
BEA-331825
|
Error: The SIP Message FileStreamHandler is unable to open the access logfile for SIP messages logFileName due to t.
|
Description
| Failed to create an access log logFileName for SIP messages due to t. |
|
Cause
| The filepath specified for the sip messages access log is invalid or the server process cannot write to the sip messages access log logFileName. |
|
Action
| Specify a valid file path for the sip messages access log. |
|
