Contents Previous Next

JTS Messages

----JTS5001
Servant is already active.

Servant is not active.

Solution:

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

----JTS5005
Recovery or resync process got interrupted.

Solution:

See the server log for more details. This is an Unexpected Internal Error.
Please contact Sun with the complete error log message.

----JTS5008
Transaction log directory is not accessible.

Solution:

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.

----JTS5015
ORB may not be running.

Solution:

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.

----JTS5020
Configuration problem while giving the log path.

Solution:

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

----JTS5028
XAResource.recover has thrown an exception during recovery.

Solution:

See the exception Stack trace for more details.

----JTS5032
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).

----JTS5040
ORB may not be running.

Solution:

See the server log for more details. This is an Unexpected Internal Error.
Please contact Sun with the complete error log message.

----JTS5041
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.

----JTS5064
Unexpected exception thrown from XAResource.end.

Solution:

See the server log for more details.

----JTS5065
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
Possible cause is that transaction logs are corrupted.

Solution:

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

Contents Previous Next