BEA Logo BEA Banner

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   WebLogic Server Home   |   Message Catalogs   |  


TX Messages


110000 Warning: Transaction log record class name encoding error [arg0]: t
  Detail  There was an error writing a record to the transaction log.
  Cause  Internal error.
  Action  Contact BEA Customer Support.
110001 Warning: Transaction log record encoding error [arg0]: t
  Detail  There was an error writing a record to the transaction log.
  Cause  Internal error.
  Action  Contact BEA Customer Support.
110002 Warning: Transaction log record checksum calculation error.
  Detail  There was an error writing a record to the transaction log.
  Cause  Internal error.
  Action  Contact BEA Customer Support.
110003 Warning: onError() callback exception: t
  Detail  There was an error writing a record to the transaction log, followed by an exception in the callback handler.
  Cause  Internal error.
  Action  Contact BEA Customer Support.
110004 Warning: Unable to read transaction log record checksum.
  Detail  There was an error reading the transaction log.
  Cause  The transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system re-boot, a crash caused the transaction being logged at that time to be rolled back.
  Action  None needed, recovery is automatic.
110005 Warning: Transaction log record checksum failure [arg0]
  Detail  There was an error reading the transaction log.
  Cause  A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system re-boot, a crash caused the transaction being logged at that time to be rolled back.
  Action  None needed, recovery is automatic.
110007 Error: Log record class instantiation problem [arg0]: t
  Detail  There was an error reading a record from the transaction log.
  Cause  Internal error, or possibly crash recovery processing of a new transaction log file perfomred by an older WebLogic software version.
  Action  Contact BEA Customer Support.
110008 Error: Log record class readExternal problem [arg0]: t
  Detail  There was an error reading a records externalized state information from the transaction log.
  Cause  Internal error, or possibly crash recovery processing of a new transaction log file perfomred by an older WebLogic software version.
  Action  Contact BEA Customer Support.
110009 Critical: Transaction log I/O buffer overflow, arg0 bytes buffered
  Detail  More than arg0 bytes are waiting to be written to the transaction log's disk. The system will not buffer any more log records since it appears the disk cannot keep up. Transactions cannot be committed until the I/O buffer begins to empty out.
  Cause  Either the disk is unavailable, full, or the cannot keep up with the rate of transaction commit calls.
  Action  Verify that the transaction logs disk is available and not full. If this error happens occasionally due to peaks in traffic, consider reconfiguring the sytem to add more/faster hardware.
110010 Warning: onDisk() callback exception: t
  Detail  There was a callback handler exception after writing an object to the transaction log.
  Cause  Internal error.
  Action  Contact BEA Customer Support.
110011 Warning: onRecovery() callback exception: t
  Detail  There was a callback handler exception after recovering an object from the transaction log.
  Cause  Internal error.
  Action  Contact BEA Customer Support.
110012 Critical: Transaction log circular collision, file number arg0
  Detail  Transaction log file number arg0 was open for so long that this file number needed to be reused.
  Cause  Records in this transaction log file were not released for a very long time, preventing the file from being deleted. Much later this file was needed for newer transactions.
  Action  If a resource manager (database or JMS) crashed while in the process of committing transactions, bring the resource back up as quickly as possible so that space in the transaction log can be released during crash recovery processing.
110013 Error: Error writing transaction log file [arg0]: t
  Detail  There was an error writing the transaction log, file [arg0].
  Cause  File system full or permission problems.
  Action  Verify the transaction log file location, and check for file system problems.
110014 Error: Error reading transaction log header file [arg0]: t
  Detail  There was an error reading the transaction log's header file named [arg0].
  Cause  File system damage, possibly caused by crash.
  Action  The system will automatically create an empty transaction log.
110015 Error: Version error reading transaction log header file.
  Detail  The transaction logs header file contains an unrecognized version number.
  Cause  File corruption, or possibly giving a new transaction log file to an older WebLogic software version.
  Action  The system will automatically create an empty transaction log.
110016 Error: Format error reading transaction log header file: t
  Detail  The transaction logs header file could not be processed due to an format problem.
  Cause  File corruption, or possibly giving a new transaction log file to an older WebLogic software version.
  Action  The system will automatically recover by writing a new header file, but might lose part of all of the transaction logs previous contents.
110017 Error: Error writing transaction log header file [arg0]: t
  Detail  There was an error writing the transaction log's header file named [arg0].
  Cause  File system full or permission problems.
  Action  Verify the transaction log file location, and check for file system problems.
110018 Error: Error writing transaction log file [arg0]: t
  Detail  There was an error writing the transaction log, file [arg0].
  Cause  File system full or permission problems.
  Action  Verify the transaction log file location, and check for file system problems.
110019 Error: Error deleting transaction log file [arg0]: t
  Detail  There was an error freeing space in the transaction log, file [arg0].
  Cause  File system or permission problems.
  Action  Verify the transaction log file location, and check for file system problems.
110020 Error: Error reading transaction log file [arg0]: t
  Detail  There was an error reading transaction log file [arg0] during crash recovery.
  Cause  File system or permission problems, or possible corruption of the transaction log.
  Action  Verify the transaction log file location, and check for file system problems. Crash recovery processing continues as best it can.
110021 Error: Format error [arg0] reading transaction log file [arg1]
  Detail  There was an error reading transaction log file [arg1] during crash recovery.
  Cause  Possible corruption of the transaction log file.
  Action  Contact BEA Customer Support.
110022 Error: Format error [arg0] reading transaction log file [arg1]: t
  Detail  There was an error reading transaction log file [arg1] during crash recovery.
  Cause  Possible corruption of the transaction log file.
  Action  Contact BEA Customer Support
110023 Warning: Transaction log record checksum failure [arg0]: t
  Detail  There was an error reading the transaction log
  Cause  A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system re-boot, a crash caused the transaction being logged at that time to be rolled back.
  Action  None needed, recovery is automatic
110024 Warning: Transaction log record unabbreviation failure [abbrev code arg0]: t
  Detail  There was an error reading the transaction log.
  Cause  A record in the transaction log file is corrupted, possibly due to a crash or corruption in the header file.
  Action  None needed, recovery is automatic.
110025 Warning: Creating new transaction log file [arg0]
  Detail  The transaction log header file could not be opened for reading, and a new one is being created.
  Cause  The transation log header file is missing. This is normal and expected when a new installation is booted for the first time. Otherwise, perhaps the transaction log was deleted, in which case crash recovery will not run and some committed transactions being processed at the time of crash might not be recovered properly.
  Action  None needed. The system looks for a backup copy of the transaction log header file. If not found, a new transaction log is created.
110026 Error: Missing transaction log file [arg0]
  Detail  Transaction log file [arg0] could not be opened for reading.
  Cause  File system or permission problems, or possible corruption of the transaction log. The file might have been manually deleted.
  Action  Verify the transaction log file location, and check for file system problems. Crash recovery processing continues as best it can.
110027 Debug: Debug: arg0
  Detail  Debugging message.
  Cause  Debugging message.
  Action  None.
110028 Info: Transaction Manager did not call XA.forget() for transaction [arg1] on resource [arg0] that reported a heuristic decision during commit.
  Detail  Due to an explicit setting of the "forgetHeuristics" configuration property, the Transaction Manager did not call XA.forget() on resource [arg0] for transaction [arg1]. The resource reported a heuristic decision during transaction commit processing.
  Cause  See message detail.
  Action  After correcting any data inconsistencies due to the heuristic outcome, use the resource managers administrative commands to inform the resource to forget about the transaction.
110029 Info: Transaction Manager did not call XA.forget() for transaction [arg] on resource [arg0] that reported a heuristic decision during rollback.
  Detail  Due to an explicit setting of the "forgetHeuristics" configuration property, the Transaction Manager did not call XA.forget() on resource [arg0] for transaction [arg]. The resource reported a heuristic decision during transaction rollback processing.
  Cause  See message detail.
  Action  After correcting any data inconsistencies due to the heuristic outcome, use the resource managers administrative commands to inform the resource to forget about the transaction.
110030 Warning: XA resource [arg0] has not responded in the last arg1 second(s).
  Detail  The XA resource [arg0] has not responded to XA calls in the last arg1 seconds.
  Cause  The resource is unavailable. Possibly the resource is down, or there is network problems.
  Action  Check the resource manager and network condition. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto refresh feature of the connection pool to do this automatically. For other 3rd party XA resources, the resource provider should re-register the resource via calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
110031 Error: Error deleting file [arg0].
  Detail  When re-writing the transaction log header file, there was an error deleting file [arg0].
  Cause  There might be file system problems or permission problems.
  Action  Check permissions on this file and the directory it resides in. The system will attempt to recover automatically.
110032 Error: Error renaming file [arg0] to [arg1].
  Detail  When re-writing the transaction log header file, there was an error renaming file [arg0] to [arg1].
  Cause  There might be file system problems or permission problems.
  Action  Check permissions on these files and the directory they reside in. The system will attempt to recover automatically.
110033 Error: Recovered transaction log header file from backup location [arg0].
  Detail  There was an error reading the transaction log header file, but a backup copy was found.
  Cause  This error is probably caused by a crash right when the the transaction log header file is being re-written.
  Action  None needed, recovery is automatic.
110101 Info: No license for two-phase commit (2PC) processing.
  Detail  A valid two-phase commit (2PC) license is not present. The server is limited to coordinating transactions with zero or one resources.
  Action  Contact sales@bea.com to obtain a 2PC license.
110102 Warning: Transaction with multiple resources rolled back due to invalid two-phase commit (2PC) license.
  Detail  An attempt was made to commit a transaction with multiple resources, but the two-phase commit (2PC) feature is not licensed. The server is limited to coordinating transactions with zero or one resources.
  Action  Contact sales@bea.com to obtain a 2PC license.
110200 Error: User [arg0] is not authorized to invoke startCommit on a transaction branch.
  Detail  User identity [arg0] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt ignored.
  Cause  This might be a symptom of a potential security attack, or alternately a problem with the servers "system" security identity.
  Action  Verify that client software is not directly invoking an internal weblogic system object.
110201 Error: User [arg0] is not authorized to invoke startRollback on a transaction branch.
  Detail  User identity [arg0] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt ignored.
  Cause  This might be a symptom of a potential security attack, or alternately a problem with the servers "system" security identity.
  Action  Verify that client software is not directly invoking an internal weblogic system object.
110202 Error: User [arg0] is not authorized to invoke rollback on a transaction branch.
  Detail  User identity [arg0] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt ignored.
  Cause  This might be a symptom of a potential security attack, or alternately a problem with the servers "system" security identity.
  Action  Verify that client software is not directly invoking an internal weblogic system object.
110203 Error: *** Please ignore the following 3 error messages intentionally triggered by transaction/SecurityTest.java unit test.
  Detail  Error messages immediately following this one regarding transaction branch authorization are caused by a unit test of transaction subsystem security.
  Cause  This error message should be generated only in a BEA test environment.
  Action  None required.
110204 Warning: XA resource [arg0] returns XAER_RMFAIL and is unavailable.
  Detail  XA resource [arg0] returns XAER_RMFAIL and is unavailable.
  Cause  The resource is unavailable. Possibly the resource is down, or there is network problems.
  Action  Check the resource manager and network condition. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto refresh feature of the connection pool to do this automatically. For other 3rd party XA resources, the resource provider should re-register the resource via calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
110205 Error: User [arg0] is not authorized to invoke startRollback on a transaction.
  Detail  User identity [arg0] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt ignored.
  Cause  This might be a symptom of a potential security attack, or alternately a problem with the servers "system" security identity.
  Action  Verify that client software is not directly invoking an internal weblogic system object.