This section documents the set of messages that the ESB component can issue.
- SOAC4001E:{0}{1} {2} not available from System.getProperty
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the custom property that was not found defined for the Application Server.
- User Response:
-
- Ensure that the custom property is added to the Application Server's JMV process environement.
- SOAC4002E:{0}{1} Could not reach {2} Sub-system: {3}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the Sub-system that cannot be reached.
{3} is the message from the exception.
An exception occured while attempting to send a request to the specified Sub-system.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4003E:{0}{1} Invalid URL set for {2} Sub-system: {3}
- Explanation:
- {0} is the transaction ID for the pxnotify common component request.
{1} is the name of the component that issued the message.
{2} is the name of the Sub-system that cannot be reached.
{3} is the value of the URL that was used to reach the specified Sub-system.
An invalid URL was set for the specified Sub-system.
- User Response:
-
- Verify the URL value for the specified Sub-system.
- SOAC4004E:{0}{1} IOException when parsing SMO: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the message from the io exception.
An IO exception occurred while parsing the Service Message Object.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4005E:{0}{1} ParserConfigurationException when parsing SMO: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the message from the parser configuration exception.
An parser configuration exception occurred while parsing the Service Message Object.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4006E:{0}{1} SAXException when parsing SMO: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the message from the SAX parser exception.
An SAX parser exception occurred while parsing the Service Message Object.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4007E:{0}{1} Policy Exception when retrieving policies: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the message from the policy exception.
An policy exception occurred while retrieving policy data.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4008E:{0}{1} Service Exception when retrieving policies: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the message from the service exception.
An service exception occurred while retrieving policy data.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4009E:{0}{1} Exception: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the message from the exception.
An exception occurred.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4010E:{0}{1} SOAP header twssHeader was not found in SMO
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The twssHeader soap header was not found in the Service Message Object.
- User Response:
-
- None: possibly a programming error.
- SOAC4011E:{0}{1} SOAP element policies was not found in twssHeader
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The policies element was not found in the twssHeader soap header.
- User Response:
-
- None: possibly a programming error.
- SOAC4012E:{0}{1} GlobalTransactionID was not set in twssHeader
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The GlobalTransactionID element was not found in the twssHeader soap header.
- User Response:
-
- None: possibly a programming error.
- SOAC4013E:{0}{1} Unable to send CEI event due to error: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the exception message issued.
An exception occurred attempting to send a CEI event.
- User Response:
-
- None. Review the exception message for possible causes.
- SOAC4014E:{0}{1} Unable to get Initial Context due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the exception message issued.
An exception occurred attempting to get the intial context data.
- User Response:
-
- None: possibly a programming error.
- SOAC4015E:{0}{1} Unable to get emitter due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the exception message issued.
An exception occurred attempting to get cei emitter.
- User Response:
-
- None: possibly a programming error.
- SOAC4016E:{0}{1} Unable to get Event Factory due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the exception message issued.
An exception occurred attempting to get Event Factory.
- User Response:
-
- None: possibly a programming error.
- SOAC4017E:{0}{1} Unable to complete event due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the exception message issued.
An exception occurred attempting to send cei event.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4018E:{0}{1} Unable to get component location due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the exception message issued.
An exception occurred attempting to get component location.
- User Response:
-
- None: review exception message for possible causes.
- SOAC4019E:{0}{1} Could not form URI from address string: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the address string that could not be formed into a URI.
An error occurred attempting to form URI from address string provided.
- User Response:
-
- None: review address string and validate content.
- SOAC4020E:{0}{1} Unable to obtain Group proxy
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
An error occurred attempting to get Group proxcy.
- User Response:
-
- None: possibly a programming error.
- SOAC4021E:{0}{1} Unable to access work area partition manager: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the work area partition manager.
An error occurred attempting to access the Application Server work area partition manager.
- User Response:
-
- None: possibly a programming error.
- SOAC4022E:{0}{1} work area partition not found: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the work area partition.
An error occurred attempting to access the Application Server work area partition.
- User Response:
-
- None: possibly a programming error.
- SOAC4023E:{0}{1} No value was specified for the {2} element in TWSSheaders
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the soap element in the TWSSheaders soap header that contained no value
The named soap element was present in the TWSSheaders soap header but had no value specified.
- User Response:
-
- None: possibly a programming error.
- SOAC4024E:{0}{1} Unable to obtain database connection for: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the datasource attempting to obtain connection for
An error occurred attempting to obtain a database connection for the specified datasource.
- User Response:
-
- Verify the datasource name is correct and is properly configured.
- SOAC4025E:{0}{1} Insert into the {2} table failed. See trace log.
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the database table attempting to insert data into
An error occurred inserting data into the specified table.
- User Response:
-
- None: review JVM log messages for possible causes.
- SOAC4026W:{0}{1} Could not close database connection due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the warning message issued.
An warning occurred attempting to close the database.
- User Response:
-
- None: possibly a programming error.
- SOAC4027E:{0}{1} Could not access datasource {2} due to: {3}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the datasource attempting to access.
{3} is the exception message issued.
An exception occurred attempting to access the specified datasource.
- User Response:
-
- None: review JVM log messages for possible causes.
- SOAC4028E:{0}{1} Could not get connection to datasource {2} due to: {3}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the datasource attempting to get connection for.
{3} is the exception message issued.
An exception occurred attempting to get connection for the specified datasource.
- User Response:
-
- None: review JVM log messages for possible causes.
- SOAC4029E:{0}{1} Failed writing to the repository due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the exception message issued.
An error occurred writing to the database.
- User Response:
-
- None: review JVM log messages for possible causes.
- SOAC4030E:{0}{1} SQL statements not loaded, could not locate properties file: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the properties file containing the SQL statements.
An error occurred while attempting to locate the specified properities file.
- User Response:
-
- None. possibly a programming error.
- SOAC4031E:{0}{1} Could not find {2} SQL statement: {3}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the database type (DB2, Oracle, ...etc.)
{3} is the name of the SQL statement trying to load
An error occurred while attempting to locate the SQL statement for the
specified database type.
- User Response:
-
- None. possibly a programming error.
- SOAC4032E:{0}{1} Default database value used, could not get the type due to: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the error message issued
An error occurred while attempting to set the database type, default DB2
will be used.
- User Response:
-
- None. possibly a programming error.
- SOAC4033E:{0}{1} requesterID was not set in twssHeader
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The requesterID soap element was not present in the TWSSheaders soap header.
- User Response:
-
- None. possibly a programming error.
- SOAC4034E:{0}{1} Anonymous Access not authorized
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The request was received with no requesteriD specified in the TWSSheaders
soap header or the value was set to "Anonymous".
- User Response:
-
- Specify a different requesterID or set policies to allow for Anonymous access.
- SOAC4035E:{0}{1} Requester was not authorized to access service
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The requesterID specified in the request was not authorized to access the
specified service.
- User Response:
-
- None. Access is granted by setting up policies for the requesterID and the
requested service.
- SOAC4036E:{0}{1} Requester was not authorized to access service operation
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The requesterID specified in the request was not authorized to access the
specified service operation.
- User Response:
-
- None. Access is granted by setting up policies for the requesterID and the
requested service operation.
- SOAC4037E:{0}{1} SOAP headers was missing from SMO
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The Service Message Object contained no SOAP headers.
- User Response:
-
- None. possibly a programming error.
- SOAC4038E:{0}{1} No Service Endpoint present in SOAP header policies
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The policy data present in the TWSS SOAP header did not contain the service endpoint policy: service.Endpoint.
- User Response:
-
- Add the service.Endpoint policy to the set of policies in the Service Policy Manager and retry the transaction. For detailed instructions on creating this service policy, see the InfoCenter under Service Policy AdministrationThe following example shows the required parameters for creating this policy where the user named user1 is given permission to invoke an implementation of the web service Third Party Call, operation makeCall:
Requester: user1
Service: http://www.csapi.org/wsdl/parlayx/third_party_call/v2_3/interface (found in the service .wsdl file)
Operation: makeCall
Name: service.Endpoint
Value: http://ibm.com:9080/soa/parlayx21/ThirdPartyCall/IMS/services/ThirdPartyCall
(Note: the service.Endpoint value is for the back-end web service, not the published ESB mediation flow endpoint. This value can be found in the Administrative Console of the server where the web service is installed.)
- SOAC4039W:{0}{1} Unable to find handler data object in work area: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the Application Server partition work area.
The partition work area did not contain the required handler data object.
- User Response:
-
- None. possibly a programming error.
- SOAC4040E:{0}{1} Limit exceeded for service operation: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the service operation.
Processing the request would cause the defined Service Level Agreement (SLA) to be exceeded
for the service operation.
- User Response:
-
- None. Retry the request. If problem persist, try increasing the SLA limit that was exceeded.
- SOAC4041E:{0}{1} Limit exceeded for service: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the service.
Processing the request would cause the defined Service Level Agreement (SLA) to be exceeded
for the service.
- User Response:
-
- None. Retry the request. If problem persist, try increasing the SLA limit that was exceeded.
- SOAC4042E:{0}{1} Limit exceeded for requester: {2}
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
{2} is the name of the requester.
Processing the request would cause the defined Service Level Agreement (SLA) to be exceeded
for the requester.
- User Response:
-
- None. Retry the request. If problem persist, try increasing the SLA limit that was exceeded.
- SOAC4043E:{0}{1} Incomplete parameters, cannot retrieve policies
- Explanation:
- {0} is the transaction ID for the request.
{1} is the name of the component that issued the message.
The request did not contain enough information to be able to retrieve the required policy data.
- User Response:
-
- Ensure the request contains the requester, service, and service operation data.
- SOAC4044E:{0}{1} Attempted to set invalid interval: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the invalid interval value
Attempted to set invalid interval.
- User Response:
-
- None. possibly a programming error.
- SOAC4045E:{0}{1} Attempted to set invalid max entries: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the invalid max entries value
Attempted to set invalid max entries.
- User Response:
-
- None. possibly a programming error.
- SOAC4046E:{0}{1} Attempted to set limit on (null) bucket hierarchy
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
Attempted to set limit on null bucket hierarchy.
- User Response:
-
- None. possibly a programming error.
- SOAC4047E:{0}{1} Attempted to set invalid limit: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the invalid max entries value
Attempted to set invalid limit.
- User Response:
-
- None. possibly a programming error.
- SOAC4048E:{0}{1} Attempted to get limit on (null) bucket hierarchy
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
Attempted to get limit on null bucket hierarchy.
- User Response:
-
- None. possibly a programming error.
- SOAC4049E:{0}{1} Attempted to traverse path with (null) hierarchy levels
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
Attempted to traverse path with null hierarchy levels
- User Response:
-
- None. possibly a programming error.
- SOAC4050E:{0}{1} (null) {2} element in hierarchy.
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the index value into the levelNames String array
The levelNames entry in the String array at the specified index was null
- User Response:
-
- None. possibly a programming error.
- SOAC4051E:{0}{1} Error accessing SOA HA SLA reservation singleton instance: (null)
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
Error accessing SOA HA SLA reservation singleton instance. The instance was null.
- User Response:
-
- None. possibly a programming error.
- SOAC4052E:{0}{1} Attempted to get usage estimator for (null) requester
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
Attempted to get usage estimator but the requester was null.
- User Response:
-
- None. possibly a programming error.
- SOAC4053E:{0}{1} Attempted to verify {2} SLA for (null) requester
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the controller type (local,cluster)
Attempted to verify SLA but the requester was null.
- User Response:
-
- None. possibly a programming error.
- SOAC4054E:{0}{1} Attempted to verify {2} SLA for (null) service
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the controller type (local,cluster)
Attempted to verify SLA but the service was null.
- User Response:
-
- None. possibly a programming error.
- SOAC4055E:{0}{1} Attempted to verify {2} SLA for (null) operation
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the controller type (local,cluster)
Attempted to verify SLA but the operation was null.
- User Response:
-
- None. possibly a programming error.
- SOAC4056E:{0}{1} Attempted to verify SLA for invalid requester limit: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the requester limit value
Attempted to verify SLA but the requester limit was invalid.
- User Response:
-
- None. possibly a programming error.
- SOAC4057E:{0}{1} Attempted to verify SLA for invalid service limit: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the service limit value
Attempted to verify SLA but the service limit was invalid.
- User Response:
-
- None. possibly a programming error.
- SOAC4058E:{0}{1} Attempted to verify SLA for invalid operation limit: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the operation limit value
Attempted to verify SLA but the operation limit was invalid.
- User Response:
-
- None. possibly a programming error.
- SOAC4059E:{0}{1} Attempted to verify SLA for invalid request amount: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the request amount value
Attempted to verify SLA but the request amount was invalid.
- User Response:
-
- None. possibly a programming error.
- SOAC4060E:{0}{1} Attempted to set invalid keep alive interval: {2}
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
{2} is the keep alive value
Attempted to set invalid keep alive interval.
- User Response:
-
- None. possibly a programming error.
- SOAC4061E:{0}{1} Message body missing from SMO
- Explanation:
- {0} n/a
{1} is the name of the component that issued the message.
Message body missing from SMO.
- User Response:
-
- None. possibly a programming error.