JTA Messages 0-99
|
|
2
ERROR: Cannot enlist XA resource - reason: res
Description
An attempt to enlist the XA resource failed; the reason for the enlistment failure is specified in res.
Action
This could be due to various errors related to the resource manager. Check for any other XA error messages output to ULOG, and the resource manager vendor's trace file, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support.
3
ERROR: Cannot delist XA resource - reason: res
Description
An attempt to delist the XA resource failed; the reason for the delistment failure is specified in res.
Action
any other XA error messages output to ULOG, and the resource manager vendor's trace file, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support.
4
ERROR: Cannot enlist XA resources - reason: res
Description
An attempt to enlist the XA resource(s) failed; the reason for the enlistment failure is specified in res.
Action
This could be due to various errors related to the resource manager. Check for any other XA error messages output to ULOG, and the resource manager vendor's trace file, if any. If applicable, correct any resource manager problems. If problem persists, contact BEA Customer Support.
5
ERROR: Cannot delist XA resources - reason: res
Description
An attempt to delist the XA resource(s) failed; the reason for the delistment failure is specified in res.
Action
This could be due to various errors related to the resource manager. Check for any other XA error messages output to ULOG, and the resource manager vendor's trace file, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support.
6
ERROR: Cannot start inproc
Description
An attempt to enlist or delist the XA resource(s) failed while starting an inprocess method invocation.
Action
This could be due to various errors related to the resource manager. Check for any other XA error messages output to ULOG, and the resource manager vendor's trace file, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support.
7
ERROR: Cannot end inproc
Description
An attempt to enlist or delist the XA resource(s) failed while ending an inprocess method invocation.
Action
This could be due to various errors related to the resource manager. Check for any other XA error messages output to ULOG, and the resource manager vendor's trace file, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support.
8
ERROR: Cannot initialize JDBC connection pool: pool_name
Description
An attempt to initialize the JDBC connection pool with the name specified in pool_name failed.
Action
This could be caused by an invalid JDBC driver class name or other JDBC connection pool attributes, as specified in the UBBCONFIG file, or resource manager problems. Take appropriate corrective measures. If the problem persists, contact BEA Customer Support.
9
WARN: Cannot create minimum number of JDBC connections for the JDBC connection pool: pool_name. Total created: num.
Description
An attempt to create the minumum number of JDBC connections for JDBC connection pool, with the name specified in pool_name, failed. The total number of JDBC connections created is specified in num.
Action
This could be caused by invalid JDBC connection pool attributes, as specified in the UBBCONFIG file, or resource manager problems. Take appropriate corrective measures. If the problem persists, contact BEA Customer Support.
10
INFO: JDBC connection replaced during test connection on reserve for JDBC connection pool: pool_name
Description
This is an informational message. It indicates that the JDBC connection of the JDBC connection pool, with the name specified in pool_name, is replaced when the JDBC connection pool tests for its validity when an application attempts to obtain a JDBC connection.
Action
None.
11
INFO: JDBC connection closed during test connection on release for JDBC connection pool: pool_name
Description
This is an informational message indicating that the JDBC connection of the JDBC connection pool, with the name specified in pool_name, is replaced when the JDBC connection pool tests for its validity upon an application's release of the JDBC connection.
Action
None.
12
INFO: Cannot get DataSource property: prop for the JDBC connection pool: pool_name
Description
The DataSource property specified in prop cannot be obtained from the JDBC connection pool pool_name.
Action
None. This may result in a more serious error, in which case a corresponding error message will be written to the ULOG.
13
WARN: Cannot set DataSource property: prop for JDBC connection pool: pool_name
Description
The DataSource property specified in prop cannot be set for the JDBC connection pool with the name specified in pool_name.
Action
None. This may result in a more serious error, in which case a corresponding error message will be written to the ULOG.
17
ERROR: Required to set DataSource property "wle.jdbc.testTable" for JDBC connection pool: val
Description
The DataSource property wle.jdbc.testTable (that is, the JDBC connection pool admin attribute TESTTABLE) must be specified in the UBBCONFIG file if either the DataSource property wle.jdbc.testConnOnReserve (i.e., the JDBC connection pool admin attribute TESTONRESERVE) or wle.jdbc.testConnOnRelease (i.e., the JDBC connection pool admin attribute TESTONRELEASE) is specified to be true.
Action
Set the JDBC connection pool admin attribute TESTTABLE to a valid
database test table value in the UBBCONFIG file. Run tmloadcf
again, and then boot the application again. If the problem persists, contact BEA Customer Support.
18
WARN: XA mode not supported for JDBC driver: driver. JDBC connection pool pool_name defaulted to non-XA mode.
Description
WLE does not support the JDBC driver, with class name driver, in XA mode. This is an informational message. It indicates that the corresponding JDBC conection pool, with the name pool_name, is defaulted to operate in local transaction mode.
Action
None.
19
INFO: number JDBC connection(s) created for JDBC connection pool: pool_name
Description
This is an informational message. It indicates the number of new JDBC connections that are being created for the JDBC connection pool whose name is specified in pool_name. For non-XA connection pools, the connection to the underlying database is made at the same time as the JDBC connection is made. For XA connection pools, the connection to the underlying database is made after this message is placed in the user log file when xa_open is called.
Action
None.
20
INFO: ConnectionPoolDataSource created for JDBC driver: driver
Description
This is an informational message. It indicates that the ConnectionPoolDataSource is created for the JDBC driver whose class name is specified in driver.
Action
None.
21
ERROR: Cannot create ConnectionPoolDataSource for JDBC driver: driver
Description
An attempt to create the JDBC connection pool data source failed. The driver class name is specified in driver.
Action
Make sure that the driver class name specified in the UBBCONFIG is valid. If the problem persists, contact BEA Customer Support.
22
INFO: num JDBC connection(s) closed during shrinking of JDBC connection pool: pool_name
Description
This is an informational message. It indicates that JDBC connection(s) are closed during the shrinking of the JDBC connection pool whose name is specified in pool_name. The number num indicates the actual number of JDBC connection(s) that are being closed.
Action
None.
23
INFO: num JDBC connection(s) replaced during auto refresh of JDBC connection pool
Description
This is an informational message. It indicates that JDBC connection(s) are closed during the auto refresh of the JDBC connection pool whose name is specified in pool_name. The number num indicates the actual number of JDBC connection(s) that are being closed.
Action
None.
24
ERROR: Cannot get JDBCCONNPOOL properties from TMIB
Description
An attempt to read the JDBC connection pool admin attributes from TMIB on JavaServer startup failed.
Action
Contact BEA Customer Support.
25
ERROR: Cannot get JDBCCONNPOOL properties
Description
An attempt to obtain the JDBC connection pool admin attributes on JavaServer startup failed.
Action
Contact BEA Customer Support.
26
ERROR: Duplicate Registration of JDBC Connection Pool ManagedObject
Description
An attempt was made to register JDBC Connection Pool ManagedObject more than once with the WLE admin infrastructure.
Action
Contact BEA Customer Support.
27
ERROR: Cannot rebind JDBC connection pool: pool_name
Description
An attempt to rebind a dynamic JDBC connection pool with name pool_name after the connection pool is created failed.
Action
Contact BEA Customer Support.
28
WARN: num JDBC connections were closed
Description
This is a warning message to indicate that the WLE infrastructure implicitly closed JDBC connections on behalf of the application. Refer to the BEA WebLogic Enterprise online documentation to see under what conditions this will occur. The number num indicates the actual number of JDBC connections that were closed.
Action
Notify the programmer.
28
WARN: num JDBC connections were closed
Description
This is a warning message to indicate that the WLE infrastructure implicitly closed JDBC connections on behalf of the application. Refer to the BEA WebLogic Enterprise online documentation to see under what conditions this will occur. The number num indicates the actual number of JDBC connections that were closed.
Action
Notify the programmer.
29
ERROR: Unable to enlist XA resources - reason: res.
Description
An attempt to enlist XA resources failed. The reason for the enlist failure is specified in res.
Action
Contact BEA Customer Support.
30
ERROR: Unable to delist XA resources - reason: res.
Description
An attempt to delist XA resources failed. The reason for the delist failure is specified in res.
Action
Contact BEA Customer Support.
 |
 |
 |