WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Messages_SOAC_en_US

This section documents the set of common messages that the ESB and Service Platform components can issue.

SOAC0028E:{0}{1} An unexpected exception occurred. [{2}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the message. {2} is the exception description. An unexpected exception occurred.
User Response:
  • Review the exception description to identify the problem.
  • Review the fault records to identify any errors.
SOAC0029E:{0}{1} An unexpected event occurred [{2}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the message. {2} is the event description. An unexpected event occurred.
User Response:
  • Review the event description to identify the problem.
  • Review the fault records to identify any errors.
SOAC0032W:{0}{1} An unexpected exception occurred. Processing will continue. [{2}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the message. {2} is the exception description. An unexpected exception occurred, however processing will continue.
User Response:
  • Review the exception description to identify the problem.
  • Review the fault records to identify any errors.
SOAC0044I:{0}{1} During SOAContext initialization, received exception {2} with message {3}
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the message. {2} is the class name of the exception. {3} is the localized message from the exception. An exception occurred while trying to initialize the SOAContext.
User Response:
  • Review the exception description to identify the problem.
  • Review the fault records to identify any errors.
WebSphere Telecom Web services Server
SOAC0054I:{0}{1} Fault {2} of severity {3} originated from {4}. Fault message is [{5}]. Fault detail is [{6}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the fault. {2} is the fault code that occurred. {3} is the severity of the fault. {4} is the source of the fault. {5} is the message describing the fault. {6} is additional detail that may help in resolving the fault. The named component recorded a fault via the Faults and Alarms common component.
User Response:
  • See the documentation for the given fault code for more information.
SOAC0055W:{0}{1} Fault {2} of severity {3} originated from {4}. Fault message is [{5}]. Fault detail is [{6}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the fault. {2} is the fault code that occurred. {3} is the severity of the fault. {4} is the source of the fault. {5} is the message describing the fault. {6} is additional detail that may help in resolving the fault. The named component recorded a fault via the Faults and Alarms common component.
User Response:
  • See the documentation for the given fault code for more information.
SOAC0056E:{0}{1} Fault {2} of severity {3} originated from {4}. Fault message is [{5}]. Fault detail is [{6}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the fault. {2} is the fault code that occurred. {3} is the severity of the fault. {4} is the source of the fault. {5} is the message describing the fault. {6} is additional detail that may help in resolving the fault. The named component recorded a fault via the Faults and Alarms common component.
User Response:
  • See the documentation for the given fault code for more information.
SOAC0057I:{0}{1} Alarm {2} of type {3} originated from {4} on host {5}. Alarm message is [{6}]. Alarm detail is [{7}]. Alarm suggested action is [{8}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the alarm. {2} is the alarm code that occurred. {3} is the type of the alarm. {4} is the source of the alarm. {5} is the host where the alarm originated. {6} is the message describing the alarm. {7} is additional detail that may help in resolving the fault. {8} is an action that may resolve the alarm. The named component recorded an alarm via the Faults and Alarms common component.
User Response:
  • See the documentation for the given alarm code for more information.
SOAC0058W:{0}{1} Alarm {2} of type {3} originated from {4} on host {5}. Alarm message is [{6}]. Alarm detail is [{7}]. Alarm suggested action is [{8}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the alarm. {2} is the alarm code that occurred. {3} is the type of the alarm. {4} is the source of the alarm. {5} is the host where the alarm originated. {6} is the message describing the alarm. {7} is additional detail that may help in resolving the fault. {8} is an action that may resolve the alarm. The named component recorded an alarm via the Faults and Alarms common component.
User Response:
  • See the documentation for the given alarm code for more information.
SOAC0059E:{0}{1} Alarm {2} of type {3} originated from {4} on host {5}. Alarm message is [{6}]. Alarm detail is [{7}]. Alarm suggested action is [{8}].
Explanation:
{0} is the transaction ID for the Parlay X Web Service request. {1} is the name of the component that issued the alarm. {2} is the alarm code that occurred. {3} is the type of the alarm. {4} is the source of the alarm. {5} is the host where the alarm originated. {6} is the message describing the alarm. {7} is additional detail that may help in resolving the fault. {8} is an action that may resolve the alarm. The named component recorded an alarm via the Faults and Alarms common component.
User Response:
  • See the documentation for the given alarm code for more information.
SOAC7500I: Located mbean '%(1)s' -> %(2)s
Explanation:
%(name) is the name of the bean. %(bean) is the bean name. The location status of the MBean.
User Response:
  • No action is needed.
SOAC7501W: JMX error: type=%(1)s,exception=%(2)s
Explanation:
%(type) is the type of the MBean. %(ex) is the exception that occurred. The JMX Java Management Extension operation encountered an error.
User Response:
  • Review the configuration data provided to the script.
SOAC7502E: Retry count exceeded: %(1)s
Explanation:
%(cnt) is the retry count. The retry count was exceeded, which means that the expected MBean can not be connected to.
User Response:
  • Review the configuration data provided to the script.
SOAC7503I: Registering service implementation: service=[%(1)s],implementation=[%(2)s],enabled=[%(3)s],description=[%(4)s]
Explanation:
%(svc) is the service. %(impl) is the service implementation. %(en) is the enabled state. %(desc) is the description. The service implementation was registered.
User Response:
  • No action is needed.
SOAC7507I: Service implementation successfully registered.
Explanation:
The service implementation was registered.
User Response:
  • Review the configuration data provided to the script.
SOAC7508E: Service implementation not registered. Either it has already been registered or an error occurred querying existing implementations.
Explanation:
The service implementation failed to register successfully.
User Response:
  • No action is needed.
SOAC7509I: Creating policies in the Service Policy Manager...
Explanation:
The policies are created.
User Response:
  • No action is needed.
SOAC7510I: Received results:
Explanation:
The results are displayed.
User Response:
  • No action is needed.
[%(1)s] -> %(2)s
Explanation:
%(pol) is the policy name. %(res) is the result. The policy value is displayed.
User Response:
  • No action is needed.
SOAC7512E: Error occurred - See server log for details.
Explanation:
An error occurred that was not expected.
User Response:
  • Review the configuration data provided to the script.
Success
Explanation:
The operation was successful.
User Response:
  • No action is needed.
req=%(1)s,svc=%(2)s,op=%(3)s,name=%(4)s,value=%(5)s,type=%(6)s
Explanation:
%(req) is the requester. %(svc) is the service. %(op) is the operation. %(name) is the policy name. %(val) is the value. %(type) is the type. the policy information is displayed.
User Response:
  • No action is needed.
SOAC7515E: Failure: %(1)s %(2)s %(3)s
Explanation:
%(msgid) the message id. The operation failed.
User Response:
  • Review the configuration data provided to the script.
SOAC7516E: Error registering service implementation: [%(1)s]
Explanation:
%(msgid) is the message id. The service implementation was not registered.
User Response:
  • Review the configuration data provided to the script.
SOAC7517I: Registering policy type: type=%(1)s,editable=%(2)s,mask=[%(3)s],encrypted=%(4)s,desc=%(5)s
Explanation:
%(type) is the type. %(edit) is the editable flag. %(mask) is the mask. %(encrypt) is the encrypt. %(desc) is the encrypt. The policy type was registered.
User Response:
  • No action is needed.
SOAC7518E: Error registering policy type: %(1)s
Explanation:
%(msgid) is the message id. The policy type was not registered.
User Response:
  • Review the configuration data provided to the script.
SOAC7519I: Policy type successfully registered.
Explanation:
The policy type was registered successfully.
User Response:
  • No action is needed.
SOAC7520I: Running script for service implementation [%(1)s]...
Explanation:
%(impl) is the implementation name. The implementation script is running.
User Response:
  • No action is needed.
SOAC7521I: Finished script for service implementation [%(1)s].
Explanation:
%(impl) is the implementation name. The implementation script completed.
User Response:
  • No action is needed.
SOAC7522I: Processed script parameters.
Explanation:
The parameters are processed.
User Response:
  • No action is needed.
SOAC7523I: %(1)s=%(2)s
Explanation:
The options are displayed.
User Response:
  • No action is needed.
SOAC7524I: Defining new service: service=[%(1)s],parentGroup=[%(2)s],enabled=%(3)s,description=[%(4)s],type=%(5)s
Explanation:
%(svc) is the service name. %(parent) is the parent name. %(enabled) is the enabled name. %(desc) is the description name. %(type) is the type name. The service is registered.
User Response:
  • No action is needed.
SOAC7525I: Service definition successfully created.
Explanation:
The service is registered successfully.
User Response:
  • No action is needed.
SOAC7526E: Error creating new service definition: [%(1)s]
Explanation:
An error occurred.
User Response:
  • Review the configuration data provided to the script.
SOAC7527I: Defined new operation: service=[%(1)s],operation=%(2)s,enabled=%(3)s,description=[%(4)s]
Explanation:
%(svc) is the service. %(op) is the operation. %(enabled) is the enabled flag. %(desc) is the description. The operation is registered.
User Response:
  • No action is needed.
SOAC7528I: Operation definition successfully created.
Explanation:
the operation is registered successfully.
User Response:
  • No action is needed.
SOAC7529E: Error creating new operation definition: [%(1)s]
Explanation:
An error occurred.
User Response:
  • Review the configuration data provided to the script.
SOAC7530E: Error occurred - See the log for details.
Explanation:
A severe error occurred that was not expected.
User Response:
  • Review the configuration data provided to the script. Study the information provided in the error.
SOAC7531I: Log: %(1)s
Explanation:
The log file is located at the specified location.
User Response:
  • Review the log file for additional information about the execution of the task.
SOAC7532E: Environment variable WAS_HOME is required.
Explanation:
The WAS_HOME environment variable is required.
User Response:
  • Review the log file for additional information about the execution of the task.
SOAC7533I: Processing: %(1)s
Explanation:
The processing message gives status information about how the script is progressing.
User Response:
  • Review the log file for additional information about the execution of the task.
SOAC7534I: Restarting node agent: %(1)s
Explanation:
%(node) is the name of the node on which the node agent is running. This message gives status information when a node agent is restarting.
User Response:
  • Review the log file for additional information about the execution of the task.
SOAC7535I: Node agent [%(1)s] is shut down.
Explanation:
%(node) is the name of the node on which the node agent is running. This message gives status information when a node agent is shut down.
User Response:
  • Review the log file for additional information about the execution of the task.
SOAC7536I: Node agent [%(1)s] is started.
Explanation:
%(node) is the name of the node on which the node agent is running. This message gives status information when a node agent is started.
User Response:
  • Review the log file for additional information about the execution of the task.
SOAC7537I: WAS Configuration Topology Hint:
Explanation:
This message gives a hint as to the application server topology the could be used in the configuration user interface.
User Response:
  • This information is provided as a convenience.
SOAC7538I: Synchronizing node: %(1)s
Explanation:
%(node) is the name of the node that is synchronizing with the deployment manager. This message gives status information when a node is synchronizing with the deployment manager.
User Response:
  • This information is provided as a convenience.
SOAC7539I: Publishing Common Runtime files to node: %(1)s
Explanation:
%(node) is the name of the node that is receiving Common Runtime files. This message gives status information when Common Runtime files are being published to a node.
User Response:
  • This information is provided as a convenience.
SOAC7540I: Publishing AG Runtime files to node: %(1)s
Explanation:
%(node) is the name of the node that is receiving AG Runtime files. This message gives status information when AG Runtime files are being published to a node.
User Response:
  • This information is provided as a convenience.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.