GlassFish v3 Error Message Reference
\

JTS

This page lists error messages with the JTS prefix.

See How to Contribute for more information about adding to and enhancing the information on this page.

----JTS0001 Test Message. Parameter 1={0} parameter 2={1}

Cause

TBD

Solution

TBD

----JTS0002 Date Message. Parameter 1={0,date} Parameter 2={1,time}

Cause

TBD

Solution

TBD

----JTS0003 Number Message. Parameter 1={0,number,integer}

Cause

TBD

Solution

TBD

----JTS5001 Cannot create control object reference.

Cause

Servant is already active.

Cause

Servant is not active.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5002 Cannot locate -(0) servant.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5003 Cannot destroy -(0) object reference.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5004 Cannot create coordinator object reference

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5005 Wait for resync complete interrupted

Cause

Recovery or resync process got interrupted.

Solution

See the server log for more details.

----JTS5006 Unable to convert object reference to string in recovery.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5007 Cannot initialise log.

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5008 Cannot open log file for server = -(0).

Cause

Make sure, Transaction log directory (transaction-service.tx-log-dir in server configuration file) is proper andhas the read, write permissions for the user of the application server.

Solution

Transaction log directory is not accessible.

----JTS5009 Cannot create CoordinatorResource object reference

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5010 Cannot create CoordinatorSynchronization object reference

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5011 No coordinator available.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5012 Unexpected error occurred when trying to begin a new transaction.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5013 Unable to create a subordinate Coordinator.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5014 Recoverable JTS instance, serverId = -(0)

Cause

TBD

Solution

TBD

----JTS5015 Unexpected error occurred when creating portable object adaptors

Cause

ORB may not be running.

Solution

Make sure that ORB is running.

Solution

If ORB is running, this is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5016 Unexpected error occurred when creating current object

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5017 The ORB daemon, ORBD, is not running.

Cause

TBD

Solution

TBD

----JTS5018 Cannot register -(0) instance with the ORB.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5019 This is a non-persistent servers. Transactions will not be recoverable.

Cause

TBD

Solution

TBD

----JTS5020 Invalid log path. Using -(0).

Cause

Configuration problem while giving the log path.

Solution

Check the Transaction log path in server configuration file (transaction-service.tx-log-dir).

----JTS5021 Invalid default log path. Using current directory.

Cause

TBD

Solution

TBD

----JTS5022 Unexpected exception -(0) from log.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5023 Heuristic exception -(0) cannot be reported to superior in resync.

Cause

TBD

Solution

TBD

----JTS5024 Cannot create RecoveryCoordinator object reference.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5025 Log file exists for transient server -(0).

Cause

TBD

Solution

TBD

----JTS5026 Exception -(0) recovering an in-doubt Coordinator.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5027 Exception -(0) on -(1) operation during resync.

Solution

See the server log for more details.

----JTS5028 XAException occurred during recovery of XAResource objects; XA Error Code : -(0)

Cause

XAResource.recover has thrown an exception during recovery.

Solution

See the exception Stack trace for more details.

----JTS5029 Exception -(0) on -(1) operation during resync.

Solution

See the server log for more details.

----JTS5030 Unable to write restart record.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5031 Exception -(0) on Resource -(1) operation.

Solution

See the server log for more details.

----JTS5032 Retry limit of -(0) -(1) operations exceeded.

Cause

Server could not communicate with the resource manager with in the retry limit.

Solution

Make sure that resource manager is up and running or increase the retry limit (transaction-service.retry-timeout-in-seconds in the server configuration file).

----JTS5033 Exception -(0) on -(1) synchronization operation.

Solution

See the server log for more details.

----JTS5034 Already identified to communications manager.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5035 Unable to identify to communications manager.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5036 Transaction in the wrong state for -(0) operation.

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5037 Cannot create Terminator object reference.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5038 Transaction resynchronization from originator failed,retrying....

Cause

TBD

Solution

TBD

----JTS5039 Timeout thread stopped

Cause

TBD

Solution

TBD

----JTS5040 Cannot create TransactionFactory object reference.

Cause

ORB may not be running.

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5041 The resource manager is doing work outside a global transaction

Cause

Database driver or Resource Adapter has thrown XAException with the error message "The resource manager is doing work outside a global transaction"

Solution

Check if the application is using the same XA pool outside the transactional context as well as in the transactional context. Some drivers do not allow this scenario. Another scenario to verify is, two separate XA pools pointing to the same backend with the same credentials and the second connection is obtained with in the same transaction, without closing the first connection.

----JTS5042 Unexpected error occurred while getting the status of the transaction

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5043 Unexpected error occurred while creating transaction manager instance

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5044 Unexpected error occurred while getting or creating transaction state

Cause

TBD

Solution

TBD

----JTS5045 Unexpected error occurred in beforeCompletion

Cause

TBD

Solution

TBD

----JTS5046 Transaction is not active

Cause

TBD

Solution

TBD

----JTS5047 Transaction object not available

Cause

TBD

Solution

TBD

----JTS5048 Assert condition not satisfied

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5049 Cannot create XAResource object reference.

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5050 Invalid timeout value. Negative values are illegal.

Cause

TBD

Solution

TBD

----JTS5051 Invalid transaction state change

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5052 Transaction id is already in use.

Cause

TBD

Solution

TBD

----JTS5053 Invalid log record data in section -(0).

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5054 Unexpected error occurred in after completion

Cause

One or more SynchronizationImpls beforeCompletion or afterCompletion methods have thrown unexpected exception.

----JTS5055 Unexpected error occurred in getCORBAReference

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5056 Invalid wait point

Solution

Make sure to call FailureInducer.setWaitPoint() with a valid WaitPoint.

----JTS5057 FailPoint : -(0)

Cause

TBD

Solution

TBD

----JTS5058 Invalid crash point

Solution

Make sure to call FailureInducer.setWaitPoint() with a valid WaitPoint.

----JTS5059 Exception recovering an in-doubt Coordinator

Solution

See the server log for more details.

Solution

This is an Unexpected Internal Error. Please contact Sun with the complete error log message.

----JTS5060 Exception occurred while setting transaction timeout

Cause

TBD

Solution

TBD

----JTS5061 Exception occurred while enabling transaction monitoring

Cause

TBD

Solution

TBD

----JTS5062 Exception occurred while setting XAResource timeout

Solution

See the server log for more details. XAResource.setTransactionTimeout() might not be supported for this XAResource.

----JTS5063 Unexpected error occurred in beforeCompletion, XA Error Code : -(0), Error Message : -(1)

Cause

TBD

Solution

TBD

----JTS5064 Unexpected exception occurred while delisting the resource

Cause

Unexpected exception thrown from XAResource.end.

Solution

See the server log for more details.

----JTS5065 An IO Exception occurred while handling recovery file

Cause

Transaction Log directory path is not valid or proper permissions are not there.

Solution

Make sure that transaction log directory is valid and files in that directory have read write permissions.

----JTS5066 Unexpected error occurred in recovery process. Possible cause is that transaction logs are corrupted. Please clean up the transaction-service.tx-log-dir/tx/* files and restart the server.

Cause

Possible cause is that transaction logs are corrupted.

Solution

Please clean up the transaction-service.tx-log-dir/tx/* files and restart the server.

----JTS5067 Unexpected error occurred in commit

Cause

TBD

Solution

TBD

----JTS5068 Unexpected error occurred in rollback

Cause

TBD

Solution

TBD

----JTS5069 Exception occurred while accessing JDBC resource for transaction log.

Cause

TBD

Solution

TBD

----JTS5070 Exception occurred while obtaining JDBC resource -(0) for transaction log.

Cause

TBD

Solution

TBD

----JTS5071 Unexpected error occurred in registerSynchronization

Cause

TBD

Solution

TBD