GlassFish v3 Error Message Reference
\

DTX

This page lists error messages with the DTX prefix.

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

----DTX5001 Exception in enlistComponentResources.

Cause

Exception occurred while enlisting the resource.

Solution

Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.

----DTX5002 Exception in delistComponentResources.

Cause

Exception occurred while delisting the resource.

Solution

Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.

----DTX5003 RollbackException in registerSynchronization.

Cause

Trying to register the sync object while transaction is marked for rollback.

Solution

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

----DTX5004 RemoteException in UserTx.begin().

Cause

Exception occurred while enlisting the component resource.

Solution

Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.

----DTX5005 RemoteException in UserTx.commit().

Cause

Exception occurred while delisting the component resources.

Solution

Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.

----DTX5006 RemoteException in UserTx.rollback().

Cause

Exception occurred while delisting the component resources.

Solution

Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.

----DTX5007 Exception :

Cause

TBD

Solution

TBD

----DTX5008 Pooling Exception:

Cause

Exception occurred while closing the connection.

Solution

Check if DB is up and running.

----DTX5009 Reconfiguration of transaction timeout failed

Cause

Invalid integer passed to set the timeout.

Solution

Check the timeout that is being given in the server configuration file.

----DTX5010 An exception occurred while JTAStats monitoring registration

Cause

Could not register the JTA statistics for monitoring due to configuration problem.

Solution

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

----DTX5011 Error occurred while getting monitor attribute

Cause

Requested attribute is not monitorable.

Solution

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

----DTX5012 ClassNotFoundException occurred while creating JTAStats

Cause

JTAStats implementation class is not found.

Solution

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

----DTX5013 Attribute is not part of transaction monitoring

Cause

TBD

Solution

TBD

----DTX5014 Caught exception in beforeCompletion() callback:

Cause

Exception occurred while calling beforeCompletion() method of the registered synchronization

Solution

Check exception message for the exact cause of the exception

----DTX5015 Caught exception in afterCompletion() callback:

Cause

Exception occurred while calling afterCompletion() method of the registered synchronization

Solution

Check exception message for the exact cause of the exception

----DTX5016 Error in XA recovery. See logs for more details

Cause

Exceptions while trying to close connections of handlers.

Solution

Individual resource handlers would have logged exceptions if any, check server.log for more details.

----DTX5017 Cannot construct the probe. Transaction Manager is NULL!

Cause

Transaction Manager is not set in the StatsProvider.

Solution

This error shouldn't happen. Please file a bug with details about the setup.

----DTX5018 TBEAN IS NULL FOR:

Cause

TransactionAdminBean was not constructed properly

Solution

This error shouldn't happen. Please file a bug with details about the setup.