The WLSS.Setup1.0 catalog contains messages in the range
BEA331200 - BEA331399. 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-331200
|
Error: Failed to load resource uri
|
Description
| Failed to load resource uri |
|
Cause
| This is a packaging error. |
|
Action
| Please ensure that the resource uri is available to the application. |
|
|
BEA-331201
|
Emergency: Failed to parse xml file
|
Description
| Failed to parse xml file |
|
Cause
| This is a packaging error. |
|
Action
| Please ensure that sipserver.xml conforms to the XML schema. |
|
|
BEA-331202
|
Error: Role or role-link "name" for security-role is not declared as security-role
|
Description
| Role or role-link "name" for security-role is not declared as security-role |
|
Cause
| There security configuration is not valid. |
|
Action
| Please correct the security configuration and redeploy the application. |
|
|
BEA-331203
|
Error: Invalid run-as "name" defined in security-role
|
Description
| Invalid run-as "name" defined in security-role |
|
Cause
| The security configuration is not valid. |
|
Action
| Please fix the security configuration and redeploy the application. |
|
|
BEA-331204
|
Error: Invalid role-name "name" for auth-constraint in security-role
|
Description
| Invalid role-name "name" for auth-constraint in security-role |
|
Cause
| The security configuration is not valid. |
|
Action
| Please fix security configuration and redeploy the application. |
|
|
BEA-331205
|
Alert: Encountered an unexpected exception while deploying "name" Sip application.
|
Description
| Encountered an unexpected exception while deploying "name" Sip application. |
|
Cause
| This is an application packaging problem. |
|
Action
| Please contact support and provide the stack trace for further analysis. |
|
|
BEA-331206
|
Error: Failed to located sip container appName in the server.
|
Description
| Failed to located sip container appName in the server. |
|
Cause
| This is a configuration error. |
|
Action
| Please ensure that the SIP container application is available to all servers in the domain. If the problem still exists, please contact BEA technical support. |
|
|
BEA-331207
|
Error: MaxApplicationSessionLifetime must be equal or greater than the default session length of every deployed application. Proposed value (newValue minutes) conflicts with application conflictAppName (conflictAppValue minutes).
|
Description
| MaxApplicationSessionLifetime must be equal or greater than the default session length of every deployed application. Proposed value (newValue minutes) conflicts with application conflictAppName (conflictAppValue minutes). |
|
Cause
| This is a configuration error. |
|
Action
| This error should be issued only when changing the MaxApplicationSessionLifetime value from the console. Press Release Configuration to undo the update. |
|
|
BEA-331208
|
Info: Start parsing sip related annotations of "appName"
|
Description
| Start parsing sip related annotations of "appName" |
|
Cause
| This message is generated when container starts parsing sip related annotations |
|
Action
| This is an informational message |
|
|
BEA-331209
|
Info: Complete parsing sip related annotations of "appName"
|
Description
| Complete parsing sip related annotations of "appName" |
|
Cause
| This message is generated when container completes parsing sip related annotations |
|
Action
| This is an informational message |
|
|
BEA-331210
|
Error: Skip SIP related logic, because error occurs when parsing sip related annotations of "appName"
|
Description
| Error occurs when parsing sip related annotations of "appName" |
|
Cause
| This is a parsing error. |
|
Action
| Please ensure that the annotations contained in the sip application is fully compliant with specification. |
|
|
BEA-331211
|
Info: Skip processing annotations for v1.0 SIP application
|
Description
| Skip processing annotations for v1.0 SIP application |
|
Cause
| This message is generated when container skip processing annotations for v1.0 SIP application |
|
Action
| This is an informational message |
|
|
BEA-331212
|
Info: A new SIP application "appName" is created by a SIP servlet "servletName"
|
Description
| A new SIP application is created by a SIP servlet |
|
Cause
| This message is generated when a new SIP application is created by a SIP servlet |
|
Action
| This is an informational message |
|
|
BEA-331213
|
Warning: "annInfo" is located in common directory and may be shared by multiple SIP modules
|
Description
| An annotation is located in common directory and may be shared by multiple SIP modules |
|
Cause
| This message is generated when an annotation is located in common directory and may be shared by multiple SIP modules |
|
Action
| Please check the deployment package to make sure this annotation is located in the right place |
|
|
BEA-331214
|
Info: "objName" is ignored because it belongs to another SIP application "appName"
|
Description
| An annotation is ignored because it belongs to another SIP application |
|
Cause
| This message is generated when an annotation belongs to another SIP application and is ignored |
|
Action
| Please check the deployment package to make sure this annotation has proper "applicationname" attribute |
|
|
BEA-331215
|
Warning: Class "clzName" declared in sip.xml as listener can not be found or does not implement appropriate SIP listener interface. Please note that such a class will not receive any callbacks.
|
Description
| A Class declared in sip.xml as the listener can not be found or does not implement appropriate SIP listener interface. Please note that such a class will not receive any callbacks. |
|
Cause
| A Class declared in sip.xml as the listener can not be found or does not implement appropriate SIP listener interface. |
|
Action
| Please check sip.xml and make sure the class declared in sip.xml as listener is valid and implement appropriate SIP listener interface. |
|
|
BEA-331216
|
Warning: The class of servlet "servletName" declared in sip.xml can not be found or does not extend the abstract class javax.servlet.sip.SipServlet. Please note that this class cannot be loaded as a SipServlet to handle SIP messages.
|
Description
| The class of a servlet declared in sip.xml can not be found or does not extend the abstract class javax.servlet.sip.SipServlet. Please note that this class cannot be loaded as a SipServlet to handle SIP messages. |
|
Cause
| The class of a servlet declared in sip.xml can not be found or does not extend the abstract class javax.servlet.sip.SipServlet. |
|
Action
| Please check sip.xml and make sure the class declared in sip.xml as servlet is valid and extends the abstract class javax.servlet.sip.SipServlet. |
|
|
BEA-331217
|
Warning: The servlet name "servletName" declared as servlet-mapping in sip.xml can not be found in servlet declarations. Please note that the mapping will be ineffective when dispatching sip message.
|
Description
| The servlet name declared as servlet-mapping in sip.xml can not be found in servlet declarations. Please note that the mapping will be ineffective when dispatching sip message. |
|
Cause
| The servlet name declared as servlet-mapping in sip.xml can not be found. |
|
Action
| Please check sip.xml and make sure the servlet name declared in sip.xml as servlet-mapping can be found in servlet declarations. |
|
|
BEA-331218
|
Warning: The servlet name "servletName" declared in security-constraint in sip.xml can not be found in servlet declarations.
|
Description
| The servlet name "servletName" declared in security-constraint in sip.xml can not be found in servlet declarations. |
|
Cause
| The servlet name declared as servlet-name in security-constraint in sip.xml can not be found. |
|
Action
| Please check sip.xml and make sure the servlet name declared in sip.xml as servlet-name in security-constraint can be found in servlet declarations. |
|
|
BEA-331219
|
Warning: The security realm name "servletName" specified in sip.xml is invalid(e.g. corresponding security realm is not configured in domain).
|
Description
| The security realm name "servletName" specified in sip.xml is invalid(e.g. corresponding security realm is not configured in domain). |
|
Cause
| The security realm name declared in sip.xml is invalid. |
|
Action
| Please check sip.xml and make sure the security realm name declared is valid. |
|
|
BEA-331220
|
Warning: The servlet "servletName" has already declared a run-as role, the @RunAs("runasRole") will be ignored.
|
Description
| The servlet "servletName" has already declared a run-as role, the @RunAs("runasRole") will be ignored. |
|
Cause
| The servlet "servletName" has already declared a run-as role, the @RunAs("runasRole") will be ignored. |
|
Action
| Please check sip.xml and servlet annotation to be consistent. |
|
