Error Code | Description |
3000-3016 | Connection errors between the adapter and the Jolt server. |
302x | Errors from a failed local transaction. These can occur at design time or at run time. |
5000-5011 | Cache look ups in the connection factory errors. These can occur at design time or at run time. |
501x-502x | Errors from the introspection of the Jolt server's repository. This repository contains the names and input/output signatures of all remote Tuxedo services as well as all the associated data type information. During the introspection sequence, a connection is established, a list of all service names and their input/output metadata parameters is captured and placed in a cache in the connection factory object of the connection for access during adapter service creation (design time) or during adapter service execution (run time). 501x - Input Signature Creation Errors 502x - Output Signature Creation Errors |
503x | Errors from executing the adapter services. |
Error Code | Description |
3001 | Can't instantiate JOLT Parameter Object. Check Jolt.jar file. |
Explanation: The jolt.jar file is missing. | |
Action: Verify that the jolt.jar file exists in the WmTuxedoAdapter/code/jars folder. If it does not exist, copy the jolt.jar file from the Jolt_directory\udataobj\jolt\java\lib directory where Jolt_directory is the directory where the Jolt server is running. | |
3002 | Failed to get Tuxedo6SyncConnectionFactory object from parent. |
Explanation: The Tuxedo connection cannot retrieve a reference to the connection factory. | |
Action: Check the error log for connection errors and reload/restart the adapter package. | |
3003 | TuxedoSyncConnection:JoltConnection open() error. |
Explanation: The Tuxedo connection caught an exception from the Jolt API while attempting to connect. | |
Action: Verify that the jolt.jar file exists in the WmTuxedoAdapter/code/jars folder. If it does not exist, copy the jolt.jar file from the Jolt_directory\udataobj\jolt\java\lib directory where Jolt_directory is the directory where the Jolt server is running. | |
3004 | TuxedoSyncConnection:Failed to open() Jolt Connection. |
Explanation: The Tuxedo connection failed to successfully open a Jolt server connection. | |
Action: Check that the connection parameters (hostname, port, login, etc.) are correct for the connection, and verify that the physical connection still exists. | |
3005 | TuxedoSyncConnection:registerResourceDomain() failed. |
Explanation: The Tuxedo connection cannot register the adapter service templates for this connection. | |
Action: Check the error log for connection errors and reload/restart the adapter package. | |
3010 | TuxedoSyncConnection:Failed to get JoltSession object: SessionException received. |
Explanation: The Tuxedo connection was unable to establish a session with the Jolt server. | |
Action: Verify that the jolt.jar file exists in the WmTuxedoAdapter/code/jars folder.If it does not exist, copy the jolt.jar file from the Jolt_directory\udataobj\jolt\java\lib directory where Jolt_directory is the directory where the Jolt server is running. Check that the connection parameters (hostname, port, login, etc) are correct for the connection, and verify that the physical connection still exists. | |
3011 | TuxedoSyncConnection:Failed to close a JoltSession in endSession(). |
Explanation: The Tuxedo connection was unable to end a session with the Jolt server. | |
Action: Check the session timeout definition on the Jolt server. It should be set to infinite. | |
3012 | TuxedoSyncConnection:Failed to Get/Set JoltSessionAttributes in Connection open(). |
Explanation: The Jolt API is unable to return or set connection attributes. | |
Action: Verify that the jolt.jar file exists in the WmTuxedoAdapter/code/jars folder. If it does not exist, copy the jolt.jar file from the Jolt_directory\udataobj\jolt\java\lib directory where Jolt_directory is the directory where the Jolt server is running. Verify that the parameters for the connection are correct. | |
3013 | TuxedoSyncConnection:AdapterCheckValue() Failed. |
Explanation: The connection is unable to get the adapter service object for an adapter service name. | |
Action: Check the adapter service. It may be deleted, corrupted, or renamed. | |
3014 | TuxedoSyncConnection:adapterResourceDomainLookup() Failed. |
Explanation: The connection is unable to get the ResourceDomainValues for an adapter service name. | |
Action: Check the adapter service. It may be deleted, corrupted, or renamed. | |
3015 | TuxedoSyncConnectionFactory:can't get the Repository Object. |
Explanation: The Tuxedo connection factory cannot create a Jolt repository introspection object. | |
Action: Check the error log for details. Verify that the parameters for the connection are correct. | |
3016 | TuxedoSyncConnectionFactory:initRepository() Failed. |
Explanation: The Tuxedo connection factory received an exception from the Jolt interface while attempting to create a Jolt Repository introspection object. | |
Action: Check the error log for details. Verify that the parameters for the connection are correct. | |
3020 | TuxedoLocalTransaction:Failed to begin Jolt Transaction. |
Explanation: The LOCAL TRANSACTION is unable to create a Jolt server transaction object. | |
Action: Check the error log for details. Also verify that the Tuxedo connection status is enabled and that the parameters for this connection are correct. | |
3021 | TuxedoLocalTransaction:Failed to commit Jolt Transaction. |
Explanation: The LOCAL TRANSACTION is unable to commit a Jolt server transaction object. | |
Action: Check the error log for details. Also verify that the Tuxedo connection status is enabled and that the parameters for this connection are correct. | |
3022 | TuxedoLocalTransaction:Failed to rollback Jolt Transaction. |
Explanation: The LOCAL TRANSACTION is unable to rollback a Jolt server transaction object. | |
Action: Check the error log for details. Also verify that the Tuxedo connection status is enabled and that the parameters for this connection are correct. | |
5001 | TuxedoAdapter:MetadataCommon can't find Service Descriptor, Cache Null. |
Explanation: Unable to look up a Tuxedo service in the connection factory. The cache pointer is NULL. | |
Action: Check the error log for details and make sure the Tuxedo connection is enabled and has no connection failures. | |
5002 | TuxedoAdapter:MetadataCommon can't find Service Descriptor in Cache. |
Explanation: Unable to lookup a Tuxedo service in the connection factory. Name is not in the cache. | |
Action: Check the error log for details and make sure the Tuxedo connection is enabled and has no connection failures. | |
5010 | TuxedoAdapter:TuxRepoLookupName can't get factory from connection. |
Explanation: The Tuxedo connection is unable to get the reference to the parent connection factory. | |
Action: Check the error log for details. Reload/restart the Tuxedo Adapter package. | |
5011 | TuxedoAdapter:TuxRepoLookupName can't get Repository Cache from Factory. |
Explanation: The Tuxedo connection factory is unable to return the pointer to the repository cache. | |
Action: Check the connection status and look in the error log for connection errors. | |
5012 | TuxedoAdapter:TuxInputSignature can't get factory from connection. |
Explanation: The Tuxedo connection is unable to get the reference to the parent connection factory. | |
Action: Check the error logs for connection errors. Reload/restart the Tuxedo Adapter package. | |
5013 | TuxedoAdapter:TuxInputSignature can't get Repository Cache from Factory. |
Explanation: The Tuxedo connection factory is unable to return the pointer to the repository cache. | |
Action: Check the connection status and look in the error log for connection errors. | |
5014 | TuxedoAdapter:TuxInputSignature No Service Descriptors in Repository. |
Explanation: The repository cache in the connection factory is empty. | |
Action: Check the connection status and verify that the connection attributes (Application Name, Application Password, User Role, etc.) are correct. | |
5015 | TuxedoAdapter:TuxInputSignature Service Name is NULL. |
Explanation: The service name passed for look ups in the repository cache is NULL. | |
Action: The adapter service is corrupt, deleted, renamed, or out of sync with the repository. | |
5016 | TuxedoAdapter:TuxInputSignature can't Find Service Descriptor in Repository. |
Explanation: The service name passed for look ups in the repository cache cannot be found. | |
Action: The cache in the connection factory is not synchronized with the repository. Reload/restart the adapter. | |
5017 | TuxedoAdapter:TuxInputSignature Input Signature in Descriptor is NULL. |
Explanation: The Tuxedo service descriptor in the repository cache has no input signature. | |
Action: Check the input signature definition on the Jolt server for this service. | |
5018 | TuxedoAdapter:TuxInputSignature No Parameters in Input Signature Descriptor. |
Explanation: The input signature in the repository cache has no parameters. | |
Action: Check the input signature definition on the Jolt server for this service. | |
5022 | TuxedoAdapter:TuxOutputSignature can't get factory from connection. |
Explanation: The Tuxedo connection is unable to get the reference to the parent connection factory. | |
Action: Check the error log for details. Reload/restart the Tuxedo Adapter package. | |
5023 | TuxedoAdapter:TuxOutputSignature can't get Repository Cache from Factory. |
Explanation: The Tuxedo connection factory is unable to return the pointer to the repository cache. | |
Action: Check the connection status and look in the error log for connection errors. | |
5024 | TuxedoAdapter:TuxOutputSignature No Service Descriptors in Repository. |
Explanation: The repository cache in the connection factory is empty. | |
Action: Check the connection status and verify that the connection attributes (Application Name, Application Password, User Role, etc.) are correct. | |
5025 | TuxedoAdapter:TuxOutputSignature Service Name is NULL. |
Explanation: The service name passed for look ups in the repository cache is NULL. | |
Action: The adapter service is corrupt, deleted, renamed, or not synchronized with the repository. | |
5026 | TuxedoAdapter:TuxOutputSignature can't find Service Descriptor in Repository. |
Explanation: The service name passed for look ups in the repository cache cannot be found. | |
Action: The cache in the connection factory is not synchronized with the repository. Reload/restart the adapter. | |
5027 | TuxedoAdapter:TuxOutputSignature Output Signature in Descriptor is NULL. |
Explanation: The Tuxedo service descriptor in the repository cache has no output signature. | |
Action: Check the output signature definition on the Jolt server for this service. | |
5028 | TuxedoAdapter:TuxOutputSignature No Parameters in Output Signature Descriptor. |
Explanation: The output signature in the repository cache has no parameters. | |
Action: Check the output signature definition on the Jolt server for this service. | |
5030 | TuxedoAdapter:Tux Synch Service, execute:Input WmRecord is NULL. |
Explanation: The input signature record passed into the adapter service is NULL. | |
Action: Check the error log for details. Reload/restart the adapter package. | |
5031 | TuxedoAdapter:Tux Synch Service, execute:can't create JoltRemoteService Object. |
Explanation: Unable to create a Jolt service with the name given in the adapter service. Adapter service is not synchronized with the Jolt server repository. | |
Action: Reload or restart the adapter. | |
5032 | TuxedoAdapter:Tux Synch Service, execute:JoltRemoteService.call() failed. |
Explanation: The call() to execute the remote service on the Jolt server failed. Check the error log for details. | |
Action: Check the connection status and the adapter service. Ensure that the adapter service is synchronized with the Tuxedo service. | |
5033 | TuxedoAdapter:Tux Synch Service, execute:Input Field: can't cast from Java-type to Jolt-Type. |
Explanation: The input field data type for Java cannot be translated to a Jolt server data type. | |
Action: Check the data type definitions in the adapter service in Designer. | |
5034 | TuxedoAdapter:Tux Synch Service, execute:Input Fields: No Service Input Values. |
Explanation: There are no input signature values to pass to the Jolt remote service. | |
Action: Check the input signature definition in Designer. | |
5035 | TuxedoAdapter:Tux Synch Service, execute:WmManagedConnection is not Tuxedo6SyncConnection. |
Explanation: The adapter service template does not match the connection type. Check the error log for details. | |
Action: Reload/restart the adapter package. | |
5036 | TuxedoAdapter:Tux Synch Service, execute:Error while adding Values to RemoteService. |
Explanation: The adapter service cannot add the input signature values to the Jolt remote service object. | |
Action: Compare the adapter service signature to the Jolt server repository signature. | |
5037 | TuxedoAdapter:Tux Synch Service, execute:Error reading response data from JoltRemoteService. |
Explanation: Data defined in the adapter service output signature was not returned by the Jolt remote service. | |
Action: Compare the adapter service signature to the Jolt server repository signature. | |
5038 | TuxedoAdapter:Tux Synch Service, execute:can't translate IS datatype for input field to Tuxedo datatype. |
Explanation: A data type in the adapter service input signature cannot be translated to a Jolt remote service data type. | |
Action: Compare the adapter service signature to the Jolt server repository signature. | |
5039 | TuxedoAdapter:Tux Synch Service, execute:can't translate Tux datatype to IS datatype for output field. |
Explanation: The data returned by the Jolt remote service contains a data type that cannot be translated to a Java data type. | |
Action: Compare the adapter service signature to the Jolt server repository signature. |