Express (Distributed operating systems), v8.0 > Reference > Messages
CWWWS
CWWWS8001E: The following exception occurred: {0}
Explanation An internal error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8002E: The following error occurred while attempting to register Endpoint Manager MBean for the {0} Application, {1} Module : {2}
Explanation An internal error occurred when attempting to register Endpoint Manager MBean with MBean server. MBean will not be retrievable through MBean server, but this will not affect the functionality of the application. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8003E: The following error occurred while attempting to unregister Endpoint Manager MBean for the {0} Application, {1} Module : {2}
Explanation An internal error occurred when attempting to unregister the Endpoint Manager MBean from the MBean server. The MBean is not retrievable through the MBean server, but this does not affect the functionality of the application. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8004E: The following error occurred while attempting to send notification for Endpoint Manager MBean: {0}
Explanation Notifications failed to broadcast to all registered listeners of the Endpoint Manager MBean. Notifications are sent whenever an endpoint that belongs to the Endpoint Manager changes state. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8005E: The system could not locate the endpoint with the {0} key.
Explanation The key that was passed in was not valid. Therefore, the key does not have a corresponding endpoint. The keys are the service's partial URL pattern, the JMS target service, or the corresponding wsdl:service and wsdl:port values. Action Ensure the key is valid and contains valid service and port names within the module.
CWWWS8006E: The system could not locate any endpoints pertaining to the {0} service.
Explanation The value for the wsdl:service name was not recognized and its corresponding endpoints could not be found. Action Ensure that the wsdl:service name that is registered with the service's WSDL file is valid.
CWWWS8007E: The endpoint corresponding to the {0} key is already started.
Explanation The endpoint being started is already in the start state. Action There is no need to start an already started endpoint.
CWWWS8008E: The endpoint corresponding to the {0} key is already stopped.
Explanation The endpoint being stopped is already in the stop state. Action There is no need to stop an already stopped endpoint.
CWWWS8009E: The system could not read the {0} class file correctly.
Explanation The class is not processed for annotation metadata. Action Ensure that the class file is valid and not corrupted.
CWWWS8010E: The system could not determine the programming model type for the {0} service reference because the {1} service interface class did not load correctly.
Explanation The service reference does not have an assigned type. This does not affect the capability of the service reference. Action Ensure that the service interface class file is valid and not corrupted.
CWWWS8011E: The {0} cache file cannot be processed correctly because of the following error: {1}
Explanation A Web services cache is not available to the application. This will not affect the functionality of the application. Action No action is required.
CWWWS8012E: Module does not have a context-root associated with it.
Explanation Module may not be web enabled to require a context-root. Action Make sure module is web enabled. Otherwise, context-root cannot be retrieved for this module.
CWWWS8013E: The system could not determine the type of the Web service with the {0} Service Endpoint Interface.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWWS8014W: The {0} file could not be copied to the new location {1} because of the following error: {2}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWWS8015E: All requested endpoints are already in the started state.
Explanation The endpoints being started are already in the started state. Action There is no need to start endpoints that are already started.
CWWWS8016E: All requested endpoints are already in the stopped state.
Explanation The endpoints being stopped are already in the stopped state. Action There is no need to stop endpoints that are already stopped.
CWWWS8017E: The service corresponding to the {0} key is already started.
Explanation The service being started is already in the started state. Action There is no need to start a service that is already started.
CWWWS8018E: The service corresponding to the {0} key is already stopped.
Explanation The service being stopped is already in the stopped state. Action There is no need to stop a service that is already stopped.
CWWWS8019E: The following error occurred trying to run the {0} WSDLPostProcessorPlugin class: {1}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8020E: An error occurred trying to register the Performance Monitoring Infrastructure (PMI) service for {0} module: {1}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8021E: An error occurred trying to unregister the Performance Monitoring Infrastructure (PMI) service for {0} module: {1}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8022E: An error occurred trying to create the service Performance Monitoring Infrastructure (PMI) group for {0} module: {1}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8023E: An error occurred trying to register the Performance Monitoring Infrastructure (PMI) service for {0} module, {1} service: {2}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8024E: An error occurred trying to unregister the Performance Monitoring Infrastructure (PMI) service for {0} module, {1} service: {2}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8025E: An error occurred trying to create the endpoint Performance Monitoring Infrastructure (PMI) group for {0} module, {1} service: {2}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8026E: An error occurred trying to register the Performance Monitoring Infrastructure (PMI) service for {0} module, {1} service, {2} port: {3}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8027E: An error occurred trying to unregister the Performance Monitoring Infrastructure (PMI) service for {0} module, {1} service, {2} port: {3}
Explanation An internal system error occurred. Action Consult the logs in your <profile_home>/logs directory for more information.
CWWWS8028E: Access is denied for resource {0}, monitor authority is required.
Explanation The current user does not have the required authority to invoke the Endpoint Manager MBean operation. Action Log in as a user that has at least the monitor level of authority to invoke the Endpoint Manager MBean operation.
CWWWS8029E: Access is denied for resource {0}, operator or deployer authority is required.
Explanation The current user does not have the required authority to invoke the Endpoint Manager MBean operation. Action Log in as a user that has at least the operator or deployer level of authority to invoke the Endpoint Manager MBean operation.