The following table lists each logging code generated by the XSLT Service Engine and describes the cause of the log message along with the recommended action for you to take.
Logging Code |
Severity |
Message Text, Cause, and Action |
---|---|---|
XSLTSE-4003 |
Config |
Starting XsltSE with transformation engine: {0}. Cause: XsltSE supports either Xslt 1.0 or 2.0. Action: None required. |
XSLTSE-5001 |
Info |
Initialized XSLT service engine successfully! Cause: The component initialized. Action: None. |
XSLTSE-5002 |
Info |
Started XSLT service engine successfully! Cause: The component started. Action: None. |
XSLTSE-5003 |
Info |
Stopped XSLT service engine successfully! Cause: The component stopped. Action: None. |
XSLTSE-5004 |
Info |
Shut down XSLT service engine successfully! Cause: The component shut down. Action: None. |
XSLTSE-6001 |
Warning |
Failed to load Xslt Engine {0}: {1}. Cause: The configuration is invalid. Action: Verify the configuration value is either "XSLT_1_0" or "XSLT_2_0" and review the server log for more information as to the cause of the error. |
XSLTSE-6002 |
Warning |
Failed to load Xslt Engine {0} as the class {1} could not be loaded! Cause: The underlying XSLT processor class could not be loaded (occurs more often with Xslt 2.0 support). Action: Review the Xslt 2.0 Support wiki and the server log for more information as to the cause of the error. |
XSLTSE-6003 |
Warning |
XsltSEBootstrap installation MBean failed to initialize: {0}. Cause: The XSLT Service Engine configuration MBean failed to initialize, possibly due to invalid configuration values. Action: Review the server log for more information as to the cause of the error. |
XSLTSE-6004 |
Warning |
Invalid Transform Engine value: {0}. Cause: The configuration is invalid. Action: Verify the configuration value is either "XSLT_1_0" or "XSLT_2_0" and review the server log for more information as to the cause of the error. |
The following table lists each logging code generated by the Transform Shared Library, a framework used by the XSLT Service Engine. Log descriptions and causes, along with the recommended action for you to take, are also provided.
Logging Code |
Severity |
Message Text, Cause, and Action |
---|---|---|
TRANSL-5001 |
Info |
The process definition for operation {0} has been overwritten! Cause: Multiple operations with the same name were defined, only the last will be activated. Action: Rename one or more operations in the transformmap file and the corresponding WSDL document. |
TRANSL-5002 |
Info |
{0} cannot run completed process srvc={1},op={2} Cause: Component attempted to execute a transformation process that has already completed. Action: None, execution will abort. Review the server log for more information as to why process was re-executed. |
TRANSL-5003 |
Info |
Please define a transformation process for operation "{0}". Cause: Action: None. |
TRANSL-5004 |
Info |
Please review logs for cause of propagated fault. Cause: A received fault was propagated as an error. Action: Review the server log for fault content. |
TRANSL-6001 |
Warning |
Failed to parse transformmap descriptor: {0} Cause: Component encountered error parsing transformmap configuration file. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6002 |
Warning |
Failed to import WSDL({0}) from: {1} Cause: An error occurred importing WSDL document. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6003 |
Warning |
Failed to parse literal param content: {0} Cause: An error occurred parsing literal xml content in transformmap. Action: Review and correct the parameter definition in transformmap.xml. |
TRANSL-6004 |
Warning |
Must specify transformation input part for multi-part message in operation {0} Cause: The 'source' attribute did not specify a message part. Action: Add the message part name to the 'source' attribute to indicate the part to transform. |
TRANSL-6005 |
Warning |
Must specify transformation output part in operation {0} Cause: The 'result' attribute did not specify a message part. Action: Add the message part name to the 'result' attribute to indicate the part to which transformation output is assigned. |
TRANSL-6006 |
Warning |
Missing required param type for stylesheet: {0} Cause: Param element in transformmap is missing required attribute 'type'. Action: Configure the type of the parameter. |
TRANSL-6007 |
Warning |
Transform param content file "{0}" not found in {1}: {2} Cause: Parameter content file could not be located. Action: Verify parameter content is at specified location and redeploy. |
TRANSL-6008 |
Warning |
Failed to parse XML content in file "{0}" in {1}: {2} Cause: An error occurred reading xml parameter content from a file. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6009 |
Warning |
Imported WSDL document does not exist at: {0} Cause: The WSDL could not be located at the specified location. Action: Verify location of WSDL and correct Import element as needed. |
TRANSL-6010 |
Warning |
Imported WSDL namespace conflict, document namespace must match configured namespace! Cause: An imported WSDL has a different namespace than configured in the Import element. Action: Change the namespace in the WSDL or the Import element. |
TRANSL-6011 |
Warning |
Imported WSDL namespace conflicts with previously imported WSDL: {0} Cause: Two or more imported wsdls share the same namespace. Action: Modify namespaces to eliminate duplication. |
TRANSL-6012 |
Warning |
Undefined portType: {0} Cause: The specified PortType is not defined in any imported wsdls. Action: Verify PortType definitions and that correct wsdls are imported. |
TRANSL-6013 |
Warning |
Failed to locate WSDL with targetNamespace: {0} Cause: PortType definition could not be resolved because WSDL could not be located. Action: Review the server log for more information as to the cause of the error and verify correctness of Import elements. |
TRANSL-6014 |
Warning |
Failed to distinguish between multiple operations "{0}" in portType: {1} Cause: Two or more operations have same input and/or output types and component cannot determine which should process message exchange. Action: Review the wsdls and correct the input/output for uniqueness across operations. |
TRANSL-6015 |
Warning |
Undefined operation "{0}" in portType: {1} Cause: The PortType definition could not be located in imported wsdls. Action: Review imported wsdls and configured PortType. |
TRANSL-6016 |
Warning |
{0} is a required attribute for Import element! Cause: Import element is missing a required attribute. Action: Add the missing attribute to the Import element in transformmap. |
TRANSL-6017 |
Warning |
Transform descriptor is invalid - missing required 'targetNamespace' attribute! Cause: Transformmap configuration file is missing the required 'targetNamespace' attribute. Action: Add a 'targetNamespace' to transformmap configuration file. |
TRANSL-6018 |
Warning |
Transform descriptor is invalid - missing required 'name' attribute in element: {0} Cause: Transformmap activity is missing the required 'name' attribute. Action: Verify 'name' attribute is defined on all activities in transformmap configuration file. |
TRANSL-6019 |
Warning |
Misconfigured Transform descriptor - unqualified QName: {0} Cause: A QName attribute was not configured with a namespace. Action: Correct the misconfigured attribute in transformmap. |
TRANSL-6020 |
Warning |
Cannot locate XSL stylesheet: {0} Cause: Component failed to locate XSL stylesheet at specified location. Action: Review the transformmap and verify stylesheet paths and names. |
TRANSL-6021 |
Warning |
Failed to create exchange - unsupported pattern: {0} Cause: Transformation process aborted due to unsupported exchange pattern. Action: Review the server log for more information as to the cause of the error and only use supported patterns InOut and InOnly. |
TRANSL-6022 |
Warning |
Cannot locate transformation descriptor file: {0} Cause: Component failed to locate transformmap configuration file. Action: Verify the correctness of the deployed service unit and redeploy. |
TRANSL-6023 |
Warning |
Illegal arguments passed to InvokeFunction.{0}(Object, String{1}): {2}, {3}, {4} Cause: Usage of the 'invoke' function in stylesheet is misconfigured. Action: Review the Invoke function wiki and correct the function invocation. |
TRANSL-6024 |
Warning |
Engine context parameter is the wrong type: {0} Cause: Usage of the 'invoke' function in stylesheet is misconfigured. Action: Review the Invoke function wiki and correct the function invocation. |
TRANSL-6025 |
Warning |
Missing invoke configuration: {0} Cause: Usage of the 'invoke' function requires Invoke activity definitions, which are absent. Action: Review the Invoke function wiki and correct the transformmap configuration file. |
TRANSL-6026 |
Warning |
A processing error occurred in {0}: {1} Cause: Transformation process encountered an error during processing. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6027 |
Warning |
An unexpected error occurred in {0}: {1} Cause: Transformation process encountered an unexpected error. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6028 |
Warning |
{0} failed to register invocation variables: {1} Cause: Transformation process failed to resolve input and/or output variables for an activity. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6029 |
Warning |
An {0} message exchange (id={1}) is missing normalized content! Cause: Component accepted message exchange with no payload content. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6030 |
Warning |
Unable to create invokable exchange: {0} Cause: Transformation process failed to create a message to send. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6031 |
Warning |
Invocation failed: {0} Cause: Transformation process encountered error while invoking a service. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6032 |
Warning |
An unexpected error occurred during invoke: {0} Cause: Transformation process encountered unexpected error while executing Invoke activity. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6033 |
Warning |
Unsupported exchange pattern: {0} Cause: Transformation process attempted to reply with an unsupported message exchange pattern. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6034 |
Warning |
{0} failed to reply to ME (id={1}): {2} Cause: Invoked message exchange could not be completed by sending DONE status. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6035 |
Warning |
{0} failed to send ERROR status on ME (id={1}): {2} Cause: Invoked message exchange could not be completed by sending ERROR status. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6036 |
Warning |
Failed to identify ME pattern for operation: {0} Cause: Component could not determine message exchange pattern for an operation. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6037 |
Warning |
{0} skipped processing non-XSLT transform activity: {1} Cause: A non-Transform activity was processed as a Transform activity. Action: Review the server log for more information as to the cause of the error and file a defect against the component. |
TRANSL-6038 |
Warning |
Xslt transformation failed: {0} Cause: An XSL transformation failed. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6039 |
Warning |
An error occurred processing transform activity: {0} Cause: Transformation process encountered error executing Transform activity. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6040 |
Warning |
The requested operation "{0}" is not provisioned on EndpointPlugin insertion failed: Could not find plugin 1 Cause: The operation is not defined in the transformmap configuration file. Action: Define an Operation in the transformmap. |
TRANSL-6041 |
Warning |
A processing error occurred provisioning a {0} service: {1} Cause: Transformation process encountered an error during execution. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6042 |
Warning |
Failed to load transformation engine: {0} Cause: Component encountered error loading pluggable Xslt support module. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6043 |
Warning |
Exchange({0}) terminated with ERROR status by {1}. Service: {2}, Endpoint: {3}, Operation: {4} Cause: {5} - {6} Actor: {7}, Detail: {8} Cause: A message exchange could not be successfully processed and has been aborted. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6044 |
Warning |
Propagating fault as ERROR, received from service "{0}-{1}" Cause: Transformation process received a fault from invoked service and is propagating it as a fault. Action: Review the server log for more information on the received fault and consider adding fault handling to the transformation process. |
TRANSL-6045 |
Warning |
{0} failed reply to complete process, ME (id={1}): {2} Cause: An error occurred sending a reply message exchange. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6046 |
Warning |
Must specify 'source' and 'result' for fault handler transform activities! Cause: A fault-handling Transform activity was defined without 'source' and/or 'result' attribute(s). Action: Define the missing attribute(s) in the Transform activity. |
TRANSL-6047 |
Warning |
Failed to compile stylesheet - {0}: {1} Cause: The XSL stylesheet is invalid and failed compilation. Action: Review the server log for more information as to the cause of the error, fix the stylesheet, and redeploy. |
TRANSL-6048 |
Warning |
InvokeFunction.{0} failed: {1} Cause: An error occurred executing function. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6049 |
Warning |
Failed to create new Transformer: {0} Cause: Component was unable to create an instance of javax.xml.Transformer. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6050 |
Warning |
Compilation not supported by this activity! Cause: Component failed to load pluggable Xslt support module. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6051 |
Warning |
newTransformer not supported by this activity! Cause: Component failed to load pluggable Xslt support module. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6052 |
Warning |
{0} endpoint creation failed, no descriptor found for service unit: {1} Cause: Component could not locate a transformation process definition for the specified endpoint. Action: Review the server log for more information as to the cause of the error, fix the transformmap, and redeploy. |
TRANSL-6053 |
Warning |
{0} {1} is missing from descriptor in service unit: {2} Cause: An endpoint definition in the transformmap was absent in the service unit descriptor. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6054 |
Warning |
Failed to initialize {0} service unit {1} - targetNamespace conflict: {2} Cause: A transformation process namespace conflicts with a previously deployed transformation process. Action: Change the 'targetNamespace' attribute of the transformmap being deployed. |
TRANSL-6055 |
Warning |
{0} Service unit "{1}" init failed: {2} Cause: An error occurred during service unit initialization. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6056 |
Warning |
Send failed for {0}, exchange id: {1} Cause: The synchronous send executed by 'invoke' function failed. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6057 |
Warning |
{0} failed retry attempt for {1}-{2}: {3} Cause: Component encountered error while attempting redelivery. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6058 |
Warning |
Received ERROR status from ServiceEndpointPlugin insertion failed: Could not find plugin 0 Cause: Transformation process received a fault from invoked service. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6060 |
Warning |
Failed to handle fault for message exchange {0}: {1} Cause: Transformation process encountered error handling fault. Action: Review the server log for more information as to the cause of the error. |
TRANSL-6061 |
Warning |
Failed to extract fault parts during propagation for {0}: {1} Cause: Transformation process was unable to parse fault message. Action: Review the server log for more information as to the cause of the error. |
TRANSL-7001 |
Severe |
{0} does not support {1} exchange pattern. Cause: Component accepted a message exchange with an unsupported pattern. Action: Only InOnly and InOut message exchange patterns are supported, update WSDL operations accordingly. |
TRANSL-7002 |
Severe |
Failed to complete exchange({0}) for endpoint({1}-{2}): {3} Cause: Component encountered an unrecoverable error while executing transformation process. Action: Review the server log for more information as to the cause of the error. |
TRANSL-7003 |
Severe |
Failure to respond to invoke error, transformation process aborted: {0} Cause: Component was unable to send ERROR response. Action: Review the server log for more information as to the cause of the error. |
TRAPI-6001 |
Warning |
Failed to create {0} instance: {1} Cause: Component could not create instance for Xslt 2.0 support. Action: Review the server log for more information as to the cause of the error. |