|
| |
| Sun Java System Application Server 8.1 Enterprise Edition 2005Q1 Error Message Reference | |
Chapter 8
JTS Error MessagesThis chapter describes messages for errors with a JTS prefix.
JTS5001Message
Solutions/Workarounds
This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
JTS5005Message
Recovery or resync process got interrupted.
Solutions/Workarounds
See the server log for more details. This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
JTS5008Message
Transaction log directory is not accessible.
Solutions/Workarounds
Make sure that the Transaction log directory (transaction-service.tx-log-dir in server configuration file) is proper and has the read, write permissions for the user of the application server.
JTS5015Message
ORB may not be running.
Solutions/Workarounds
Make sure that ORB is running. If ORB is running, this is an Unexpected Internal Error. Please contact Sun with the complete error log message.
JTS5020Message
Configuration problem while giving the log path.
Solutions/Workarounds
Check the Transaction log path in server configuration file (transaction-service.tx-log-dir).
JTS5028Message
XAResource.recover has thrown an exception during recovery.
Solutions/Workarounds
See the exception Stack trace for more details.
JTS5032Message
Server could not communicate with the resource manager with in the retry limit.
Solutions/Workarounds
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).
JTS5040Message
ORB may not be running.
Solutions/Workarounds
See the server log for more details. This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
JTS5041Message
Database driver or Resource Adapter has thrown XAException with the error message The resource manager is doing work outside a global transaction
Solutions/Workarounds
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.
JTS5064Message
Unexpected exception thrown from XAResource.end.
Solutions/Workarounds
See the server log for more details.
JTS5065Message
Transaction Log directory path is not valid or proper permissions are not there.
Solutions/Workarounds
Make sure that transaction log directory is valid and files in that directory have read write permissions.
JTS5066Message
Possible cause is that transaction logs are corrupted.
Solutions/Workarounds
Please clean up the transaction-service.tx-log-dir/tx/* files and restart the server.