This chapter describes messages for errors with a DTX prefix.
DTX5001 |
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 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 |
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 |
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 |
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 |
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 |
Exception occurred while closing the connection.
Solution:Check if database is up and running.
DTX5009 |
Invalid integer passed to set the timeout.
Solution:Check the timeout that is being given in the server configuration file.
DTX5010 |
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 |
Requested attribute is not monitorable.
Solution:This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
DTX5012 |
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