Skip navigation.

JTA Subsystem Messages

The JTA1.0 catalog contains messages in the range BEA110000 - BEA119999. Messages in this catalog are part of the weblogic.transaction Internationalization package and the weblogic.i18n Localization package.

BEA-110000

Warning: Transaction log record class name encoding error [className]: t

Description

An error occurred while writing a record to the transaction log.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110001

Warning: Transaction log record encoding error [className]: t

Description

An error occurred while writing a record to the transaction log.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110002

Warning: Transaction log record checksum calculation error.

Description

An error occurred while writing a record to the transaction log.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110003

Warning: onError() callback exception: t

Description

An error occurred while writing a record to the transaction log, followed by an exception in the callback handler.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110004

Warning: Unable to read transaction log record checksum.

Description

An error occurred while 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

No action required. Recovery is automatic.

BEA-110005

Warning: Transaction log record checksum failure [failureCode]

Description

An error occurred while 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

No action required. Recovery is automatic.

BEA-110007

Error: Log record class instantiation problem [className]: t

Description

An error occurred while reading a record from the transaction log.

Cause

An internal error occurred. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic software version.

Action

Contact BEA Customer Support.

BEA-110008

Error: Log record class readExternal problem [className]: t

Description

An error occurred while reading externalized state information for a record from the transaction log.

Cause

An internal error occurred. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic software version.

Action

Contact BEA Customer Support.

BEA-110009

Critical: Transaction log I/O buffer overflow, bufferCount bytes buffered.

Description

More than bufferCount bytes are waiting to be written to the transaction log disk. The system will not buffer any more log records, since it appears that the disk cannot keep up. Transactions cannot be committed until the I/O buffer begins to empty out.

Cause

Either the disk is unavailable or full, the system cannot keep up with the rate of transaction commit calls, or the maximum buffer size (250KB) for the transaction log buffer has been reached.

Action

Verify that the transaction log disk is available and not full, and verify that transaction log writes for a transaction do not exceed 250KB. If this error happens occasionally due to peaks in traffic, consider reconfiguring the sytem to add more/faster hardware.

BEA-110010

Warning: onDisk() callback exception: t

Description

A callback handler exception occurred after writing an object to the transaction log.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110011

Warning: onRecovery() callback exception: t

Description

A callback handler exception occurred after recovering an object from the transaction log.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110012

Critical: Transaction log circular collision, file number fileID.

Description

Due to the length of time transaction log file number fileID was open, 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. This file was eventually 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.

BEA-110013

Error: An error occurred while writing transaction log file [fileName]: t.

Description

An error occurred while writing the transaction log, file [fileName].

Cause

The file system is full or permission problems exist.

Action

Verify the transaction log file location, and locate any file system problems.

BEA-110014

Error: An error occurred while reading transaction log header file [headerFileName]: t.

Description

An error occurred while reading the header file named [headerFileName] of the transaction log.

Cause

File system damage, possibly caused by a crash.

Action

The system will automatically create an empty transaction log.

BEA-110015

Error: A version error occurred while reading the transaction log header file.

Description

The transaction log header file contains an unrecognized version number.

Cause

File corruption exists. A new transaction log file may have been given to an older version of WebLogic.

Action

The system will automatically create an empty transaction log.

BEA-110016

Error: A format error occurred while reading transaction log header file: t

Description

The transaction log header file could not be processed due to a format problem.

Cause

File corruption exists. A new transaction log file may have been given to an older version of WebLogic..

Action

The system will automatically recover by writing a new header file, but might lose part of the previous contents of the transaction log.

BEA-110017

Error: An error occurred while writing the transaction log header file [headerFileName]: t

Description

An error occurred while writing the transaction log header file named [headerFileName].

Cause

The file system is full or permission problems exist.

Action

Verify the transaction log file location, and locate any file system problems.

BEA-110018

Error: An error occurred while writing transaction log file [fileName]: t

Description

An error occurred while writing the transaction log, file [fileName].

Cause

The file system is full or permission problems exist.

Action

Verify the transaction log file location, and locate any file system problems.

BEA-110019

Error: An error occurred while deleting transaction log file [fileName]: t

Description

An error occurred while freeing space in the transaction log, file [fileName].

Cause

File system or permission problems exist.

Action

Verify the transaction log file location, and locate any file system problems.

BEA-110020

Error: Error reading transaction log file [fileName]: t

Description

There was an error reading transaction log file [fileName] 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.

BEA-110021

Error: Format error [code] occurred while reading transaction log file [fileName]

Description

A format error occurred while reading transaction log file [fileName] during crash recovery.

Cause

Possible corruption of the transaction log file.

Action

Contact BEA Customer Support.

BEA-110022

Error: Format error [code] occurred while reading transaction log file [fileName]: t

Description

A format error occurred while reading transaction log file [fileName] during crash recovery.

Cause

Possible corruption of the transaction log file.

Action

Contact BEA Customer Support

BEA-110023

Warning: Transaction log record checksum failure [failureCode]: t

Description

An error occurred while 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

No action required. Recovery is automatic.

BEA-110024

Warning: Transaction log record unabbreviation failure [abbrev code code]: t

Description

An error occurred while 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

No action required. Recovery is automatic.

BEA-110025

Notice: Creating new transaction log file [headerFileName].

Description

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 the crash might not be recovered properly.

Action

No action required. The system looks for a backup copy of the transaction log header file. If not found, a new transaction log is created.

BEA-110026

Error: Missing transaction log file [fileName]

Description

Transaction log file [fileName] could not be opened for reading.

Cause

File system or permission problems exist, or the transaction log might be corrupted. The file might have been manually deleted.

Action

Verify the transaction log file location, and check for file system problems. Crash recovery processing will continue.

BEA-110027

Debug: msg

Description

Uncatalogued debug message - please do not change

Cause

Debugging - please do not change.

Action

No action required.

BEA-110028

Info: The transaction manager did not call XA.forget() for transaction [xid] on resource [resourceName], which reported a heuristic decision during commit.

Description

Due to an explicit setting of the "forgetHeuristics" configuration property, the transaction manager did not call XA.forget() on resource [resourceName] for transaction [xid]. The resource reported a heuristic decision during transaction commit processing.

Cause

See the message details for probably cause.

Action

After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction.

BEA-110029

Info: The transaction manager did not call XA.forget() for transaction [xid] on resource [resourceName], which reported a heuristic decision during rollback.

Description

Due to an explicit setting of the "forgetHeuristics" configuration property, the transaction manager did not call XA.forget() on resource [resourceName] for transaction [xid]. The resource reported a heuristic decision during transaction rollback processing.

Cause

See the message details for the probable cause.

Action

After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction..

BEA-110030

Warning: XA resource [resourceName] has not responded in the last lastResponse second(s).

Description

The XA resource [resourceName] has not responded to XA calls in the last lastResponse seconds.

Cause

The resource is unavailable. Possibly the resource is down, or network problems exist.

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 third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().

BEA-110031

Error: An error occurred while deleting file [headerFileName].

Description

When re-writing the transaction log header file, an error occurred while deleting file [headerFileName].

Cause

File system or permission problems might exist.

Action

Check permissions on this file and the directory in which it resides. The system will attempt to recover automatically.

BEA-110032

Error: Error renaming file [fromFileName] to [toFileName].

Description

When re-writing the transaction log header file, an error occurred while renaming file [fromFileName] to [toFileName].

Cause

File system or permission problems might exist.

Action

Check permissions on these files and the directory in which they reside. The system will attempt to recover automatically.

BEA-110033

Error: Recovered transaction log header file from backup location [headerFileName].

Description

An error occurred while reading the transaction log header file, but a backup copy was found.

Cause

This error is probably caused by a crash that occurs when the the transaction log header file is being re-written.

Action

No action required. Recovery is automatic.

BEA-110101

Info: No license exists for two-phase commit (2PC) processing.

Description

A valid two-phase commit (2PC) license is not present. The server is limited to coordinating transactions with zero or one resources.

Cause

The 2PC license is not present.

Action

Contact sales@bea.com to obtain a 2PC license.

BEA-110102

Warning: A transaction with multiple resources was rolled back due to an invalid two-phase commit (2PC) license.

Description

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.

Cause

The 2PC license is not present.

Action

Contact sales@bea.com to obtain a 2PC license.

BEA-110200

Error: User [principal] is not authorized to invoke startCommit on a transaction branch.

Description

The user with identity [principal] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt was ignored.

Cause

This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action

Verify that the client software is not directly invoking an internal WebLogic system object.

BEA-110201

Error: User [principal] is not authorized to invoke startRollback on a transaction branch.

Description

The user with identity [principal] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt was ignored.

Cause

This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action

Verify that client software is not directly invoking an internal WebLogic system object.

BEA-110202

Error: User [principal] is not authorized to invoke rollback on a transaction branch.

Description

The user with identity [principal] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt was ignored.

Cause

This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action

Verify that client software is not directly invoking an internal WebLogic system object.

BEA-110203

Error: *** Please ignore the following 3 error messages intentionally triggered by transaction/SecurityTest.java unit test.

Description

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

No action required.

BEA-110204

Warning: XA resource [resourceName] returns XAER_RMFAIL and is unavailable.

Description

XA resource [resourceName] returns XAER_RMFAIL and is unavailable.

Cause

The resource is unavailable. The resource is down, or network problems exist.

Action

Check the resource manager and network conditions. 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 third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().

BEA-110205

Error: User [arg0] is not authorized to invoke startRollback on a transaction.

Description

The user with 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 was ignored.

Cause

This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action

Verify that the client software is not directly invoking an internal WebLogic system object.

BEA-110206

Error: *** Please ignore the database down SQL exceptions immediately following this message. They are intentionally triggered by transaction/JDBCConnPoolTest unit test.

Description

SQL exceptions that immediately follow this exception regarding the database crash are caused by a transaction subsystem unit test.

Cause

This error message should be generated only in a BEA test environment.

Action

No action required.

BEA-110207

Info: A previously unavailable XA resource [resourceName] is now available.

Description

The XA resource [resourceName] was previously unavailable but has just become available again.

Cause

The previously unavailable resource is now available. It is possible that the resource has recovered from earlier failures, or previous network problems are cleared.

Action

No action required.

BEA-110208

Warning: Unregistration of Transaction Recovery Service for server [serverName] failed.

Description

An attempt to unregister the Transaction Recovery Service for server [serverName] from the migratable service framework failed.

Cause

Internal error.

Action

No action required.

BEA-110209

Warning: Registration of Transaction Recovery Service for server [serverName] failed.

Description

An attempt to register the Transaction Recovery Service for server [serverName] from the migratable service framework failed.

Cause

Internal error.

Action

No action required.

BEA-110210

Warning: Fail-back of Transaction Recovery Service for server [serverName] failed.

Description

Transaction recovery actions are performed for the Transaction Recovery Service for server [serverName]. An attempt to fail-back the Transaction Recovery Service failed.

Cause

Internal error.

Action

The administrator should examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [serverName].

BEA-110211

Warning: Fail-back retry of Transaction Recovery Service for server [serverName] failed.

Description

Transaction recovery actions are performed for the Transaction Recovery Service for server [serverName]. Both the first and second attempt to fail-back the Transaction Recovery Service failed. JTA is going to give up implicitly failing back the Transaction Recovery Service for server [serverName].

Cause

Internal error.

Action

The administrator should examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [serverName].

BEA-110212

Warning: An attempt was made to manually migrate the Transaction Recovery Service of the current server away from it while it is still active.

Description

Attempts were made to manually migrate the current server Transaction Recovery Service away from it while it is still active.

Cause

User error.

Action

For controlled migration, the administrator should suspend or shut down the current server first before manually migrating it to a backup server.

BEA-110213

Warning: The activation of Transaction Recovery Service for server [serverName] failed.

Description

The activation of Transaction Recovery Service for server [serverName] failed.

Cause

Internal error.

Action

The administrator should examine the error details, correct the error conditions and perform the necessary manual migration again if possible. If unsuccessful, contact BEA Customer Support.

BEA-110400

Warning: An error occurred while unregistering Resource Runtime MBean: t

Description

A management error was detected while unregistering a Resource Runtime MBean.

Cause

The MBean may have been unregistered previously, or there may be an issue with the JMX admin server.

Action

No action required.

BEA-110401

Warning: Ignoring error in afterCompletion. Object=arg1, Exception=t

Description

An exception was thrown in a Synchronization.afterCompletion() synchronization callback . The exception is ignored by the Transaction Manager.

Cause

The application-defined javax.transaction.Synchronization callback may have thrown an exception.

Action

No action required.

BEA-110402

Warning: Unknown state in getStatus(): arg0

Description

The Transaction.getStatus() method was called and the transaction status is not a valid value.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110403

Warning: An unexpected exception was thrown while processing a transaction during a transaction manager timer event. Exception=t

Description

The transaction manager manages a timer service that periodically checks active transactions for timeouts and performs general housekeeping activities. An exception occurred during this processing and was ignored.

Cause

Refer to the exception information found in the error message.

Action

No action required.

BEA-110404

Warning: Heuristic log record not flushed after 1 second. log=arg0

Description

A heuristic log entry for an imported transaction was not written to disk in a timely manner.

Cause

There may be contention for the file system or a device error.

Action

Verify that the log device is functioning properly.

BEA-110405

Warning: Resource resource was not assigned to any of these servers: servers

Description

During transaction commit or rollback processing, a participating resource could not be assigned to any of the participating servers. The operation was aborted.

Cause

The transaction coordinator maintains information regarding where resources are registered among all the servers that are known to the coordinator. The participating resource may have been unregistered or become unavailable prior to attempting the operation. This condition may also occur if the cache belonging to the coordinator is out of date or has not completed initialization at the time the operation is invoked.

Action

Verify the state of resource managers participating in the transaction and retry the operation.

BEA-110406

Warning: Internal error interpreting heuristic status. Expected=expected, Actual=actual

Description

The heuristic completion status of a transaction is calculated based on the expected and actual completion states of all participants. The logic to determine the heuristic outcome did not account for the combination of the actual and expected completion states.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110407

Warning: Unknown state in getStatus(): state

Description

The Transaction.getStatus() method did not recognize the transaction state as a valid state.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110408

Warning: An attempt to add a duplicate transaction to the transaction manager list was ignored.

Description

The internal transaction table of the server already contains the transaction instance being added. This event is innocuous.

Cause

Internal error.

Action

No action required.

BEA-110409

Error: Unable to advertise resource resourceName: t

Description

An error occurred while trying to advertise the name of the resource being registered with the transaction manager.

Cause

A problem may exist with the JNDI provider, or another object is already bound to this context.

Action

Contact BEA Customer Support.

BEA-110411

Error: Failed to construct local ServerCoordinatorDescriptor: t

Description

During server initialization, information about the local server could not be obtained from the local JNDI context.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110412

Error: tx completed heuristically: heurMsg

Description

The specified transaction completed heuristically. A heuristic completion occurs when a participating resource makes a unilateral decision to commit or rollback its work and that decision differs from the coordinator view of the transaction.

Cause

The resource manager may have failed, timed out or detected locking conflicts that prompted it to commit or rollback work for the transaction branch. If the heuristic error was due to a resource manager failure, the resource may not be able to determine if work for the transaction branch was committed, aborted, or both. In this case, the condition is considered a HAZARD or MIXED heuristic.

Action

The participants of the transaction should be checked for possible data corruption. The resource manager reporting the heuristic may maintain state information related to the updates involved in the heuristic error. If the JTA ForgetHeuristics configuration parameter is set to false, this information may be preserved in the resource manager. This information might be useful in correcting any data inconsistencies.

BEA-110414

Error: Illegal State (expected: Prepared or Committing). tx

Description

While attempting to retry the commit phase of a transaction, it was detected that the state of the transaction is not valid. To be in the commit phase, a transaction can only be in the prepared or committing states.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110415

Error: Illegal state. Proceeding with rollback anyway. tx

Description

While attempting to retry the rollback of a prepared transaction, it was detected that the state of the transaction is not valid.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110416

Error: The JTARuntime MBean for the server could not be created. t

Description

While starting the transaction manager subsystem, the JTARuntime MBean could not be created. This MBean provides transaction runtime statistics, information about active transactions and access to the related transaction name and resource manager runtime MBeans.

Cause

Internal error.

Action

Contact BEA Customer Support.

BEA-110419

Error: An attempt was made to add an incompatible object as transaction property: keys must be String and values must be Serializable.

Description

Transaction properties are Serializable objects that are associated with a transaction and indexed by a String key. These objects become associated with the transaction context, propagate with the transaction, and are stored in the transaction log. The class of the key object must be a String and the class of the value object must be Serializable.

Cause

See message detail.

Action

Change the application to assign the transaction property using a String key and a Serializable value.

BEA-110420

Error: An attempt was made to add an incompatible object as a local transaction property: keys must be String.

Description

Local transaction properties are objects that are associated with a transaction object but do not propagate with the transaction or get stored in the transaction log. The key object must be of the class String.

Cause

See message detail.

Action

Change the application to add the local property with a String key.

BEA-110421

Error: Internal error (possibly harmless): Timer method was called on committed transaction tx.

Description

The transaction manager invoked a timer method on a transaction that has already completed. The transaction manager periodically checks for transactions that should be aborted due to timeout. This transaction should have been removed from the internal transaction table.

Cause

Internal error. Possibly due to a race condition.

Action

No action required.

BEA-110422

Error: Forcibly aborting a transaction found in an unexpected internal state. Details=tx

Description

While processing a transaction, the transaction manager detected that the transaction is in an illegal state. The only course of action for the coordinator is to attempt to force a rollback of all participants.

Cause

Internal error.

Action

Check for any data inconsistencies among participating resources. Contact BEA Customer Support.

BEA-110423

Error: Abandoning transaction after secs seconds: tx

Description

When a transaction is abandoned, knowledge of the transaction is removed from the transaction manager that was attempting to drive the transaction to completion. The JTA configuration attribute AbandonTimeoutSeconds determines how long the transaction manager should persist in trying to commit or rollback the transaction.

Cause

A resource or participating server may have been unavailable for the duration of the AbandonTimeoutSeconds period.

Action

Check participating resources for heuristic completions and correct any data inconsistencies.

BEA-110424

Error: An unexpected exception was caught during begin: exc

Description

While the transaction manager was creating a new transaction, an unexpected exception was thrown.

Cause

Check the exception detail portion of message.

Action

Correct the condition described in the exception detail portion of the log message.

BEA-110410

Error: Unable to create resource runtime MBean for resource resourceName: t

Description

When a resource manager is registered with the transaction manager, a runtime MBean is created to track transaction statistics that are specific to the resource. This MBean could not be created.

Cause

There may be a problem with the JMX Admin Server, or another MBean with this name is already registered with the Admin Server.

Action

Contact BEA Customer Support.

BEA-110425

Error: Error advertising TransactionManager object: t

Description

The transaction service could not advertise the TransactionManager object in the server JNDI context.

Cause

There may be a problem with the JNDI provider or another object is already bound to this context.

Action

Contact BEA Customer Support.

BEA-110426

Error: An error occurred while advertising UserTransaction object: t

Description

The transaction service could not advertise the UserTransaction object in the server JNDI context.

Cause

There may be a problem with the JNDI provider, or another object is already bound to this context.

Action

Contact BEA Customer Support.

BEA-110427

Error: An error occurred while advertising Coordinator object: t

Description

The transaction service could not advertise the Coordinator object for the server in the JNDI context.

Cause

There may be a problem with the JNDI provider, or another object is already bound to this context.

Action

Contact BEA Customer Support.

BEA-110428

Error: An error occurred while exporting Coordinator object ID: t

Description

The Coordinator remote object is pinned to a specific object ID. During transaction service initialization, the Coordinator object for the server could not be exported under this object ID.

Cause

Another remote object may be bound to this object ID.

Action

Contact BEA Customer Support.

BEA-110429

Error: Error advertising SubCoordinator object: t

Description

The transaction service could not advertise the SubCoordinator RMI object for the server in the JNDI context.

Cause

There may be a problem with the JNDI provider, or another object is already bound to this context.

Action

Contact BEA Customer Support.

BEA-110430

Debug: msg: t

Description

Uncatalogued debug message - please do not change

Cause

Debugging - please do not change.

Action

No action required.

BEA-110431

Warning: Execute queue executeQueue thread count of threadCount is less than the recommended minimum value of recommendedMinimum. Transaction performance may be adversely affected.

Description

The JTA subsystem utilizes a dedicated pool of threads to process asynchronous messages to improve overall performance in a multiple server configuration that is experiencing a heavy application load. The administrator has overriden the default thread count for this execute queue to a value that is less than the recommended minimum.

Cause

See message detail.

Action

Remove or change the offending ExecuteQueue definition in the server configuration.

BEA-110432

Error: Unable to register with the Health Monitoring Service: t

Description

An exception occurred while registering the JTA Runtime MBean with the server Health Monitoring Service.

Cause

Refer to the exception portion of the error message.

Action

Check for related messages in the server error log. Contact BEA Customer Support.

BEA-110433

Error: Unable to obtain ownership of the Transaction Log.

Description

The server is unable to obtain ownership of its own transaction log within the specified time.

Cause

The Transaction Recovery Service associated with the current server is currently owned by other servers.

Action

Migrate the Transaction Recovery Migratable Service back to the current server before restarting it.

BEA-110434

Warning: Unable to unregister from the Health Monitoring Service: t

Description

An exception occurred while unregistering the JTA Runtime MBean from the server Health Monitoring Service.

Cause

Refer to the exception portion of the error message.

Action

Check for related messages in the server error log. Contact BEA Customer Support.

BEA-110440

Alert: The transaction logger is unable to load the native file driver to support the "oldPolicy" synchronous write policy. The transaction logger will use the Java file driver and the "newPolicy" policy instead, without any loss of reliability. It may be that WebLogic does not support native file I/O on this operating system. For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.

Description

The transaction logger is unable to load the native file driver to support the "oldPolicy" synchronous write policy. The transaction logger will use the Java file driver and the "newPolicy" policy instead, without any loss of reliability. It may be that WebLogic does not support native file I/O on this operating system. For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.

Cause

The native file I/O may not be supported on this platform.

Action

Contact BEA Customer Support.

BEA-110441

Info: Opening transaction log with driver version "driverVersion" and synchronous write policy "policy". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.

Description

Opening transaction log with driver version "driverVersion" and synchronous write policy "policy". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.

Cause

Informational message.

Action

None required.

BEA-110442

Info: An administrative request was made to locally rollback the transaction associated with Xid xid

Description

An administrative client, such as the WebLogic Admin Console, issued a force local rollback operation for the specified transaction.

Cause

The force local rollback was initiated by an administrative application.

Action

No action required.

BEA-110443

Info: An administrative request was made to locally commit the transaction associated with Xid xid

Description

An administrative client, such as the WebLogic Admin Console, issued a force local commit operation for the specified transaction.

Cause

The force local commit was initiated by an administrative application.

Action

No action required.

BEA-110444

Info: An administrative request was made to globally commit the transaction associated with Xid xid.

Description

An administrative client, such as the WebLogic Admin Console, issued a force global rollback operation for the specified transaction.

Cause

A force global rollback was initiated by an administrative application.

Action

No action required.

BEA-110445

Info: An administrative request was made to globally commit the transaction associated with Xid xid.

Description

An administrative client, such as the WebLogic Admin Console, issued a force global commit operation for the specified transaction.

Cause

A force global commit was initiated by an administrative application.

Action

No action required.

BEA-110446

Error: The administrative request to locally rollback the transaction associated with Xid xid failed, because the transaction does not exist

Description

An administrative client, such as the WebLogic Admin Console, issued a force local rollback operation for the specified transaction, and that transaction does not exist on the server.

Cause

The transaction may have completed before the administrative request was made.

Action

No action required.

BEA-110447

Error: The administrative request to locally commit the transaction associated with Xid xid failed because the transaction does not exist.

Description

An administrative client, such as the WebLogic Admin Console, issued a force local commit operation for the specified transaction, and that transaction does not exist on the server.

Cause

The transaction may have completed before the administrative request was made.

Action

No action required.

BEA-110448

Error: The administrative request to globally rollback the transaction associated with Xid xid failed because the transaction does not exist

Description

An administrative client, such as the WebLogic Admin Console, issued a force global rollback operation for the specified transaction, and that transaction does not exist on the server.

Cause

The transaction may have completed before the administrative request was made.

Action

No action required.

BEA-110449

Error: The administrative request to globally commit the transaction associated with Xid xid failed because the transaction does not exist

Description

An administrative client, such as the WebLogic Admin Console, issued a force global commit operation for the specified transaction, and that transaction does not exist on the server.

Cause

The transaction may have completed before the administrative request was made.

Action

No action required.

BEA-110450

Error: The administrative request to locally rollback the transaction xid encountered an error t.

Description

An administrative client, such as the WebLogic Admin Console, issued a force local rollback operation for the specified transaction. An error was encountered while processing the request.

Cause

Refer to the exception information in the error message.

Action

Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact BEA Customer Support.

BEA-110451

Error: The administrative request to globally rollback the transaction xid encountered an error t.

Description

An administrative client, such as the WebLogic Admin Console, issued a force global rollback operation for the specified transaction. An error was encountered while processing the request.

Cause

Refer to the exception information in the error message.

Action

Check to see if the transaction still exists, the operation may have resolved the transaction. If the problem persists, contact BEA Customer Support.

BEA-110452

Error: The administrative request to locally commit the transaction xid encountered an error t.

Description

An administrative client, such as the WebLogic Admin Console, issued a force local commit operation for the specified transaction. An error was encountered while processing the request.

Cause

Refer to the exception information in the error message.

Action

Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact BEA Customer Support.

BEA-110453

Error: The administrative request to globally commit the transaction xid encountered an error t.

Description

An administrative client, such as the WebLogic Admin Console, issued a force global commit operation for the specified transaction. An error was encountered while processing the request.

Cause

Refer to the exception information in the error message.

Action

Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact BEA Customer Support.

BEA-110454

Error: The administrative request to locally rollback the transaction xid failed because the transaction is in an invalid state. tx

Description

An administrative client, such as the WebLogic Admin Console, issued a force local rollback operation for the specified transaction. However, the transaction is in an invalid state and cannot be rolled back.

Cause

The administrative request is invalid.

Action

Issue a force commit operation instead to resolve the transaction.

BEA-110455

Error: The administrative request to globally rollback the transaction xid failed because the transaction is in an invalid state. tx

Description

An administrative client, such as the WebLogic Admin Console, issued a force global rollback operation for the specified transaction. However, the transaction is in an invalid state and cannot be rolled back.

Cause

The administrative request is invalid.

Action

Issue a force commit operation instead to resolve the transaction.

BEA-110456

Error: The administrative request to locally commit the transaction xid failed because the transaction is in an invalid state. tx

Description

An administrative client, such as the WebLogic Admin Console, issued a force local commit operation for the specified transaction. However, the transaction is in an invalid state and cannot be committed.

Cause

The administrative request is invalid.

Action

Issue a force rollback operation instead to resolve the transaction.

BEA-110457

Error: The administrative request to globally commit the transaction xid failed because the transaction is in an invalid state. tx

Description

An administrative client, such as the WebLogic Admin Console, issued a force global commit operation for the specified transaction. However, the transaction is in an invalid state and cannot be committed.

Cause

The administrative request is invalid.

Action

Issue a force rollback operation instead to resolve the transaction.

BEA-110458

Error: The administrative request to globally rollback the transaction xid failed, because the coordinator url could not be contacted. t

Description

An administrative client, such as the WebLogic Administration Console, issued a force global rollback operation and the coordinator for the transaction could not be contacted. Global operations require the coordinating server to be available to process the request among all participating servers for the transaction.

Cause

The server that has been chosen, since the coordinator for the transaction is either not running or is unreachable.

Action

Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.

BEA-110459

Error: The administrative request to globally commit the transaction xid failed, because the coordinator at url could not be contacted. t

Description

An administrative client, such as the WebLogic Administration Console, issued a force global commit operation and the coordinator for the transaction could not be contacted. Global operations require the coordinating server to be available to process the request among all participating servers for the transaction.

Cause

The server that has been chosen as the coordinator for the transaction is either not running or is unreachable.

Action

Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.

BEA-110460

Error: The administrative request to globally rollback the transaction xid failed, because the coordinator does not support manual transaction resolution.

Description

An administrative client, such as the WebLogic Administration Console, issued a force global rollback operation, and the coordinator for the transaction does not support manual transaction resolution.

Cause

The coordinating server is an older version of WebLogic Server that does not support manual transaction resolution.

Action

Perform local commit operations on all participants that support manual transaction resolution.

BEA-110461

Error: The administrative request to globally commit the transaction xid failed, because the coordinator does not support manual transaction resolution.

Description

An administrative client, such as the WebLogic Administration Console, issued a force global commit operation, and the coordinator for the transaction does not support manual transaction resolution.

Cause

The coordinating server is an older version of WebLogic Server that does not support manual transaction resolution.

Action

Perform local commit operations on all participants that support manual transaction resolution.

BEA-110462

Error: The administrative request to locally commit the transaction xid failed, because the transaction has been marked for rollback

Description

An administrative client, such as the WebLogic Administration Console, issued a force local commit operation. However, the transaction has been marked for rollback only. The commit operation can not complete.

Cause

The transaction has been marked for rollback by an application component.

Action

Attempt to resolve the transaction by using a forced rollback operation instead.

BEA-110463

Error: The administrative request to globally commit the transaction xid failed, because the transaction has been marked for rollback.

Description

An administrative client, such as the WebLogic Administration Console, issued a force global commit operation. However, the transaction has been marked for rollback only. The commit operation can not complete.

Cause

The transaction has been marked for rollback by an application component.

Action

Attempt to resolve the transaction by using a forced rollback operation instead.

BEA-110464

Error: The forced commit operation for transaction xid on resource resource was not performed, because the resource is busy.

Description

An administrative client, such as the WebLogic Administration Console, issued a forced commit operation. However, the resource is busy with another operation for this transaction.

Cause

There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.

Action

Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.

BEA-110465

Error: The forced rollback operation for transaction xid on resource resource was not performed, because the resource is busy

Description

An administrative client, such as the WebLogic Administration Console, issued a forced rollback operation. However, the resource is busy with another operation for this transaction.

Cause

There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.

Action

Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.

BEA-110466

Info: The forced commit operation for transaction xid on resource resource was not performed, because the resource has already been committed.

Description

An administrative client, such as the WebLogic Administration Console, issued a forced commit operation. However the transaction has already been committed.

Cause

The transaction may have completed before the administrative client invoked the commit operation.

Action

No action required. The transaction has been resolved.

BEA-110467

Info: The forced rollback operation for transaction xid on resource resource was not performed, because the resource has already been rolled back.

Description

An administrative client, such as the WebLogic Administration Console, issued a forced rollback operation. However, the transaction has already been rolled back.

Cause

The transaction may have completed before the administrative client invoked the rollback operation.

Action

No action required. The transaction has been resolved.

BEA-110468

Error: The forced commit operation for transaction xid on resource resource encountered an error. t

Description

An administrative client, such as the WebLogic Administration Console, issued a forced commit operation and a participating resource responded to the rollback operation with an error.

Cause

Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action

Determine if administrative operations are required in the resource to resolve the transaction branch.

BEA-110469

Error: The forced rollback operation for transaction xid on resource resource encountered an error. t

Description

An administrative client, such as the WebLogic Administration Console, issued a forced rollback operation and a participating resource responded to the rollback operation with an error.

Cause

Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action

Determine if administrative operations are required in the resource to resolve the transaction branch.

BEA-110470

Error: User [principal] is not authorized to invoke a forced global rollback.

Description

The administrative request to rollback the transaction failed because the user is not authorized to perform the operation.

Cause

The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.

Action

Authenticate using an identity with adequate privileges prior to invoking the operation.

BEA-110471

Error: User [principal] is not authorized to invoke a forced global commit.

Description

The administrative request to commit the transaction failed because the user is not authorized to perform the operation.

Cause

The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.

Action

Authenticate using an identity with adequate privileges prior to invoking the operation.

BEA-110472

Error: User [principal] is not authorized to invoke a forced local rollback.

Description

The administrative request to rollback the transaction failed because the user is not authorized to perform the operation.

Cause

The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.

Action

Authenticate using an identity with adequate privileges prior to invoking the operation.

BEA-110473

Error: User [principal] is not authorized to invoke a forced local commit.

Description

The administrative request to commit the transaction failed because the user is not authorized to perform the operation.

Cause

The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.

Action

Authenticate using an identity with adequate privileges prior to invoking the operation.

BEA-110474

Error: Unable to advertise non-XA resource resourceName: t

Description

An error occurred while trying to advertise the name of the resource being registered with the transaction manager.

Cause

There may be a problem with the JNDI provider, or another object is already bound to this context.

Action

Contact BEA Customer Support.

BEA-110475

Error: User [principal] is not authorized to invoke commit on a non-XA resource transaction branch.

Description

User identity [principal] should not be attempting to directly invoke internal methods on the SubCoordinator object. This might subvert transactional integrity. Permission was denied, and the attempt was ignored.

Cause

This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action

Verify that client software is not directly invoking an internal WebLogic system object.

BEA-110476

Notice: The server has detected pending transactions during graceful shutdown. The server will wait for the pending transactions to complete before suspending the RMI service. A force shutdown command can be issued to shutdown the server immediately.

Description

The server has detected pending transactions during graceful shutdown. The server will wait for the pending transactions to complete before suspending the RMI service. A force shutdown command can be issued to shutdown the server immediately.

Cause

The server has detected pending transactions during graceful shutdown

Action

No action required. Use force shutdown command to ignore inflight work and shutdown the server immediately.