Chapter 11. Errors and Exceptions
Errors and Exceptions During Transactional Applications
- NO_MEMORY
- The application has run out of memory, and thrown an
OutOfMemoryErrorexception. JBoss Transactions has attempted to do some garbage collection before re-throwing the exception. This is sometimes a transient problem and retrying the invocation might succeed. - com.arjuna.ats.arjuna.exceptions.FatalError
- The transaction system has encountered a fatal error and must shut down. Prior to this error, the transaction service ensures that all running transactions have rolled back. If caught, the application should tidy up and exit. If further work is attempted, application consistency may be violated.
- com.arjuna.ats.arjuna.exceptions.LicenceError
- An attempt has been made to use the transaction service in a manner inconsistent with the current license. The transaction service will not allow further forward progress for existing or new transactions.
- com.arjuna.ats.arjuna.exceptions.ObjectStoreError
- An error occurred while the transaction service attempted to use the object store. Further forward progress is not possible.
- Object store warnings about access problems on states
- This error may occur during the normal execution of crash recovery, as the result of multiple concurrent attempts to perform recovery on the same transaction. It can be safely ignored.
