J2CA

J2CA0015E: The Connection Pool Manager could not allocate a Managed Connection from resource {0}.

Explanation

The pool manager could not allocate a managed connection. This might be due to the properties associated with the pool manager (such as, maximum connections were exceeded). A NULL managed connection was returned by the pool manager.

Action

If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .

J2CA0016E: A two phase XA operation, {0}, was invoked within transaction ID {1}. This Resource Adapter from pool {2} does not support two phase processing.

Explanation

This indicates that an attempt was made to use the connection within the context of an XA transaction along with other XA capable resources. This is not a valid operation for this resource adapter.

Action

Modify the logic to separate the resource usage into separate transactions.

J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection: {0}.

Explanation

The pool manager created an exception when attempting to allocate a managed connection. The exception text might provide additional information for determining the problem.

Action

If there are no user controlled indications, the message might be due to an internal error in the connection manager processing. Collect diagnostic data and visit the IBM support site for more information.

J2CA0021E: An exception occurred while trying to get a Connection from the Managed Connection resource {1} : {0}.

Explanation

The resource adapter created an exception when attempting to call the getConnection() method. The exception text might provide additional information for determining the problem.

Action

If there are no user controlled indications, the message might be due to an internal error in connection manager processing. Collect diagnostic data and visit the IBM support site for more information.

J2CA0022I: An exception occurred while trying to cleanup and release the Managed Connection from resource {1} for a failed getConnection from the Managed Connection {0}. This second error was absorbed and the original error re-thrown.

Explanation

There was a problem attempting to clean records from a failed getConnection attempt. This message is informational and should be combined with other related messages for proper problem determination.

Action

Examine the other related messages for explanations and user responses.

J2CA0023E: A two phase XA operation, {0}, was invoked. This Resource Adapter from DataSource {1} does not support two phase processing.

Explanation

There was an attempt made to invoke an XA operation on a resource adapter that only supports local transactions. A local transaction resource adapter might have been included within the context of an XA transaction, along with other XA capable resources.

Action

Modify the business logic to separate the resource usage into separate transactions.

J2CA0024E: Method {0}, within transaction branch ID {1} of resource pool {4}, caught {2} and threw a {3}.

Explanation

There was a problem processing the given method. The interface defines specific exceptions that can be created, so the exception that was caught was mapped to the exception that was created. The processing within the method did not complete successfully.

Action

Check that the business logic of the application is properly catching the exception that was created and that it contains the necessary recovery logic. Also check the log files for earlier errors that caused the exception.

J2CA0026E: Method {0} caught {1} while trying to register the Resource Adapter with the Synchronization Manager for the current transaction, and threw a {2}.

Explanation

Action

Check that the business logic of the application is properly catching the exception that was created and contains the necessary recovery logic. Also check the log files for earlier errors that caused the exception.

J2CA0027E: An exception occurred while invoking {0} on an XA Resource Adapter from DataSource {3}, within transaction ID {1} : {2}.

Explanation

There was a problem processing the given method. The processing within the method did not complete successfully.

Action

J2CA0028E: An exception occurred while invoking {0} on an XA Resource Adapter from DataSource {2} : {1}.

Explanation

There was a problem processing the given method. The processing within the method did not complete successfully.

Action

J2CA0030E: Method {0} caught {1} while trying to enlist resources from DataSource {3} with the Transaction Manager for the current transaction, and threw a {2}.

Explanation

Action

J2CA0031I: Method {0} caught {1} while trying to delist resources from DataSource {3} from the Transaction Manager for the current transaction and threw {2}

Explanation

There was a problem attempting to delist resources from the transaction manager. This message is for informational purposes.

Action

If this message occurs on a regular basis, collect diagnostic information and visit the IBM support site for more information.

J2CA0034E: An unexpected event was received from the Resource Adapter for resource {2}. Expected ConnectionEvent type {0} and received ConnectionEvent type {1}.

Explanation

This is most likely an error with the specific resource adapter.

Action

Contact the resource adapter supplier.

J2CA0040E: No valid transaction context was found on the thread for method {0} with coordinator {1} using resources from DataSource {2}.

Explanation

There was an internal error in the connection manager processing. A valid transaction context is required for the given operation, but it was not found.

Action

J2CA0045E: Connection not available while invoking method {0} for resource {1}. Timed out waiting for {2} millisecond(s) with {3} remaining waiting requests and {4} current total connections used.

Explanation

A connection wait timeout has occurred. A ConnectionWaitTimeoutException was created.

Action

Reconfigure the connection pool. Increase the maximum number of connections or increase the connection wait time to avoid this error.

J2CA0046E: Method {0} caught an exception during creation of the ManagedConnection for resource {3}, throwing {2}. Original exception: {1}

Explanation

An error occurred during creation of a ManagedConnection. Usually this can be resolved by looking at the error messages from the resource adapter.

Action

J2CA0055W: Connection handle not closed at end of the unit of work scope. Handles will be closed by the Connection Manager.

Explanation

Either an activity session, transaction, or local transaction work scope is ending and connection handles are not closed. Support for caching handles outside of the current unit of work scope is not supported for this configuration or release.

Action

Inspect your application and ensure that the connection handles are closed before the associated unit of work ends.

J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource {1}. The exception is: {0}

Explanation

The connection manager has been notified by the resource adapter that an error has occurred on the connection. This informational message is logged so that the user can see the exception that was returned.

Action

The connection manager will remove the failing connection or all the connections from the pool, depending on the configuration. This is normal behavior. If this error appears unexpected, investigate the exception to determine the possible source of the problem.

J2CA0057E: The interactionPending method was unable to find a transaction wrapper class.

Explanation

This is a WebSphere internal error.

Action

J2CA0058E: The ConnectionManager was unable to associate Connection {0} with ManagedConnection {1} for resource {3}. Received exception: {2}

Explanation

This is most likely an application error. An example: A cached connection is enlisted in a transaction, then the connection is closed. Before the transaction completes another request it is sent to the same EJB that originally opened the connection. The cached handle is still associated with the original transaction and cannot be re-associated until that transaction commits.

Action

Inspect the application and ensure that the transaction is committed as soon as possible after connections are closed.

J2CA0060E: PrivilegedActionException calling doPrivileged: {0}

Explanation

This is a security runtime error.

Action

J2CA0067W: Invalid {0} setting of {1}. Defaulting to {2} instead.

Explanation

An internal error occurred. Using the default value.

Action

This is only a warning. If an error occurs later it may help in diagnosing the problem. Otherwise This can be ignored.

J2CA0073E: Unable to delist connection from resource {2} from transaction in method {0} due to exception. Initiating destruction of connection. Exception is: {1}

Explanation

An internal error was received and the connection manager was not able to delist a connection from the transaction in which it was involved. The connection manager will attempt to destroy the connection.

Action

J2CA0074E: Unable to enlist connection from resource {2} with current transaction in method {0} due to exception. Initiating destruction of connection. Exception is: {1}

Explanation

An internal error was received and the connection manager was unable to enlist a connection with the current transaction. The connection manager will attempt to destroy the connection.

Action

J2CA0075W: An active transaction should be present while processing method {0}.

Explanation

Normal connection management processing requires the presence of a transaction in order to run the current method.

Action

Start any transactions that are required to successfully use the connection.

J2CA0077E: An exception was caught while trying to obtain a javax.resource.cci.LocalTransaction from a ManagedConnection for resource {1}. The exception is: {0}

Explanation

The connection manager was unable to obtain a LocalTransaction from the resource adapter. This indicates a problem with the resource adapter.

Action

Look for error messages from the resource adapter to identify the problem.

J2CA0078E: An exception was caught while trying to obtain a javax.transaction.xa.XAResource from a ManagedConnection on DataSource {1}. The exception is: {0}

Explanation

The connection manager was unable to obtain a XAResource from the resource adapter. This indicates a problem with the resource adapter.

Action

Look for error messages from the resource adapter to identify the problem.

J2CA0079E: Method {0} has detected an internal illegal state and is throwing an IllegalStateException. The exception is: {1}

Explanation

The connection manager has detected an internal error.

Action

J2CA0080E: Method {0} has detected an internal illegal argument and is throwing an IllegalArgumentException. The exception is: {1}

Explanation

The connection manager has detected an internal error.

Action

J2CA0081E: Method {0} failed while trying to execute method {1} on ManagedConnection {2} from resource {4}. Caught exception: {3}

Explanation

The connection manager caught an exception while trying to perform an operation on a ManagedConnection.

Action

Since the ManagedConnection is part of the resource adapter, look for messages from the resource adapter to further isolate the problem.

J2CA0086I: Multiple open connection handles cannot share a physical connection to {1} within a local transaction containment boundary, so a different physical connection will be used for each connection handle. In this situation, it is important to ensure that no transactional work remains in progress after connection handle close because if additional sharable connection handles are later requested within the local transaction containment boundary, the physical connection to which they associate will be unpredictable.

Explanation

Multiple open connection handles can only share a single physical connection within the scope of a global transaction. When multiple connection handles are open within a local transaction containment boundary, each handle uses a different physical connection. Having multiple shareable connection handles open at the same time within a local transaction containment boundary can increase the requirement on the connection pool for maximum number of connections and can greatly increase the complexity of connection handle usage with respect to local transactions for applications that follow this pattern.

Action

Ensure the connection pool is sized so that each thread can require multiple physical connections, and review the application code to verify that this usage pattern is desired and that the expected sharing scope is specified.

J2CA0087E: The transaction manager was unable to enlist resource {0} from DataSource {1}.

Explanation

This message indicates a problem enlisting in a transaction. The resource might have already been enrolled in a transaction or the transaction might not have been in the correct state.

Action

Check that the business logic of the application is properly catching the exception created and that it contains the necessary recovery logic. Check log files for previous errors (specifically transaction errors) that might have caused the exception.

J2CA0088W: The ManagedConnection that is being destroyed from resource {1} is in an invalid state {0}. Processing will continue.

Explanation

An internal error has occurred.

Action

J2CA0091E: An InterruptedException occurred on the Garbage Collector thread.

Explanation

An InterruptedException occurred on the thread for the garbage collector. J2C processing will continue, but unused and aged connections will not be collected.

Action

J2CA0098E: A ClassCastException occurred attempting to cast event.getSource to ManagedConnection: {0}

Explanation

The source of the event fired on the listener was not of type ManagedConnection

Action

J2CA0103I: Duplicate connector property not added. {0}

Explanation

An attempt was made to add a duplicate connector property. The property was not added.

Action

A custom property of a connection factory or data source specified a user name or password, but a component-managed authentication alias was also specified. The alias takes precedence over the custom properties. This error might also be the result of a hand-modified resources.xml document.

J2CA0127I: A ConnectionWaitTimeout of 0 has been specified for {0}. The request will wait until a connection can be obtained.

Explanation

A ConnectionWaitTimeout of 0 indicates an infinite wait time. This thread will sleep until a connection is freed.

Action

There is no user action required.

J2CA0132E: Method {0} caught exception {1}.

Explanation

The method caught an exception that is most likely an internal error.

Action

J2CA0148W: A null ConnectionHandle was found in the CONNECTION_CLOSED ConnectionEvent {0}

Explanation

A CONNECTION_CLOSED ConnectionEvent is required by the Java EE Connector Architecture to contain a valid connection handle associated with the ManagedConnection instance.

Action

The resource adapter must use ConnectionEvent.setConnectionHandle() to supply the connection handle in the CONNECTION_CLOSED ConnectionEvent.

J2CA0159E: Internal error. An attempt has been made to change a set once property that has already been set. The property name is {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

J2CA0169E: Unable to change the property {0} on DataSource or ConnectionFactory {1}.

Explanation

The connection manager was unable to make the requested change to the configuration variable at this time.

Action

Attempt to change the configuration variable again.

J2CA0207W: A resource adapter artifact has property {0} whose value {2} is incompatible with its type {1}.

Explanation

A connection factory, activation spec or admin object has a resource property which is not valid. The value will remain unset.

Action

Correct the resource property so the value is consistent with its data type.

J2CA0216I: The Connection Manager received a fatal connection error from the Resource Adapter for resource {0}. Information may be available in previous messages or exceptions.

Explanation

The connection manager has been notified by the resource adapter that an unrecoverable error has occurred on the connection. No exception was received from the resource adapter.

Action

The connection manager will remove the failing connection, or all the connections (depending on configuration) from the pool. This is normal behavior. If this causes adverse effects, it may be necessary to contact the resource adapter supplier.

J2CA0238E: JavaBean {0} failed Bean Validation due to one or more invalid configuration settings indicated in the following list of constraint violations: {1}

Explanation

The value of one or more configuration properties of the JavaBean instance violates the specified Bean Validation constraints.

Action

Consult the documentation of the Resource Adapter provider to determine valid values for each configuration property indicated by the constraint violations and configure each property accordingly.

J2CA0240I: Ignored unimplemented feature {0} for resource {1}.

Explanation

The feature is not implemented by the application server.

Action

No user action is required.

J2CA0241W: Resource Adapter Bean Archives are not supported.

Explanation

The beans.xml file in the META-INF directory will be ignored, as CDI Managed Bean Archive Resource Adapters are not supported.

Action

Remove the beans.xml file from the META-INF directory, as CDI Managed Bean Archive Resource Adapters are not supported.

J2CA0278W: Could not de-serialize field {0} in class {1}; default value will be used

Explanation

During de-serialization of an object, an expected field was not found. This is most likely due to an object that is being de-serialized by a version of the class that is different than the one that serialized the object.

Action

This warning indicates a potential problem, but no user action is necessary unless further errors occur.

J2CA0285W: Method {0} caught an exception during validating managed connections for resource {3}, throwing {2}. Original exception: {1}

Explanation

A call to the method getInvalidConnections() returned a resource exception.

Action

Visit the support web site for the provider of the resource adapter.

J2CA0292E: The ManagedConnection from resource {0} could not be enlisted with the current transaction.

Explanation

An internal error occurred while processing the lazyEnlist() method.

Action

J2CA0293E: The Connection Manager lazyEnlist() method requires a non-null ManagedConnection parameter for resource {0}.

Explanation

This most likely indicates an error with the implementation of the resource adapter. The resource adapter called the lazyEnlist() method with a null value for the ManagedConnection.

Action

Visit the support web site for the provider of the resource adapter. The resource adapter code has passed a null value to the lazyEnlist() method. See section 7.14.2 of the JCA 1.5 specification for more information on the Lazy Transaction Enlistment optimization.

J2CA0295E: The Connection Manager has detected an attempt to start a Local Transaction within a Global (User) Transaction. Check the application code for correctness.

Explanation

This most likely indicates an error in the application. The application should not start local transactions when it is operating in a global transaction.

Action

Examine the application code to determine where a local transaction is started inside a global transaction. Search the FFDC directory for this message to find a stack trace that may include the line numbers of the code in question - this can help to narrow the search. If the line numbers are not found, if the code has been JIT compiled or it is otherwise obfuscated for example, you might want to instrument the code with System.out.println() statements to help find the problem area. If the problem cannot be found visit the IBM support web site.

J2CA0308W: Duplicate connector property not added. {0}.

Explanation

An attempt was made to add a duplicate connector property. The property was not added.

Action

A custom property of a connection factory or data source was specified, but the property already existed. This could be a symptom of a hand-modified resources.xml document.

J2CA0668E: The WorkManager was unable to populate the execution subject with the caller principal or credentials necessary to establish the security context for this work instance.

Explanation

The JASPIC callback handler of the WorkManager failed to populate the principal or custom credentials of the execution subject because an exception occurred while processing the JASPIC callbacks supplied by the resource adapter.

Action

Check the FFDC and server logs that were emitted immediately prior to message J2CA0672E to determine the cause. If the cause cannot be determined from the prior error messages, collect diagnostic data and visit the IBM support web site for more information.

J2CA0671E: The WorkManager was unable to associate the provided SecurityContext to the Work instance.

Explanation

The WorkManager encountered a problem while establishing and setting up the security context for the inbound Work request.

Action

Check the FFDC and server logs for messages J2CA0668E and J2CA0669E to determine the cause.

J2CA0672E: The JASPIC callback handler of the WorkManager failed with exception {0} while handling the callbacks provided by the security context. The exception message is {1}.

Explanation

The WorkManager encountered an exception while handling the JASPIC callbacks provided by the resource adapter within the transferred security context. The exception can be of the following cases: 1) A CallerPrincipalCallback provided a principal with a user name that does not exist in the user registry. 2) A PasswordValidationCallback provided a invalid user name or password. 3) A CallerPrincipalCallback and a PasswordValidationCallback provided different user names. 4) The resource adapter provided a callback that the application server does not currently support. 5) The resource adapter provided more than one CallerPrincipalCallback. 6) The WorkManager encountered an unexpected error.

Action

If the exception message has an error code then check the user action for that error code. If the exception is an UnsupportedCallbackException then contact the resource adapter vendor because the JASPIC callback handler of the WorkManager does not currently support the provided callback. If the exception is not any of the problems mentioned, collect diagnostic data and refer to the IBM support site for additional information.

J2CA0673W: The execution subject provided by the WorkManager does not match the subject supplied by the {0}.

Explanation

The instance of the execution subject provided by the WorkManager to establish the security context of the Work instance is not the same instance obtained from the respective callback. The WorkManager ignored the subject obtained from the callback and continued to establish the security context using the instance it provided.

Action

Contact the resource adapter vendor to modify the JASPIC callback's getSubject() method to return the execution subject provided to the SecurityContext instance through the call to method setupSecurityContext.

J2CA0674E: The user name {0} or password provided by the PasswordValidationCallback is invalid.

Explanation

The user name and password do not exist in the user registry of the realm that is configured for the security domain associated with the application.

Action

Configure the resource adapter and enterprise information system to use a valid user name and password.

J2CA0675E: The user name {0}, provided by the PasswordValidationCallback, and the user name {1}, provided by the CallerPrincipalCallback, do not match.

Explanation

User names provided by the PasswordValidationCallback and the CallerPrincipalCallback must match.

Action

Contact the resource adapter vendor and the system administrator to ensure that the resource adapter is designed and configured to return the same user name from the two callbacks.

J2CA0678W: Group {0} does not belong to the domain associated to the application.

Explanation

The security context transferred with the work instance provided a group name that does not exist in the realm (user registry) of the security domain associated to the application. The WorkManager obtained the invalid group name from an instance of a JASPIC GroupPrincipalCallback, whenever an instance is supplied by the resource adapter.

Action

Check if the group is from the same realm by confirming the group existence in the user registry for that realm.If the group is from a different realm, contact the resource adapter vendor because the WorkManager does not support groups from different realms.

J2CA0679W: No groups were found for the user with the uniqueId {0}

Explanation

The security context transferred with the work instance provided a user that does not belong to any of the groups defined in the user registry.

Action

There is no user action required.

J2CA0684E: Unable to validate the user name {0} and password that is provided by the PasswordValidationCallback.

Explanation

The WorkManager was not able to validate the user name and password that is provided by the PasswordValidationCallback because of a CustomRegistryException. This exception is caused by an invalid password or a problem with the user registry for that application realm.

Action

If the cause of the CustomRegistryException is an invalid password, configure the resource adapter or enterprise information system to use a valid user name and password combination. Otherwise resolve the problem with the user registry.

J2CA0695E: Unable to find primary pool manager during failover processing for a resource with a JNDI name of {0}.

Explanation

An internal error occurred during failover processing.

Action

J2CA0695W: A connection request for XA resource {0} was made using SPNEGO authentication, but no recovery auth data alias was configured. The XA resource is not able to participate in automated XA recovery unless a recovery auth data alias is configured.

Explanation

XA recovery is an automated background process, but SPNEGO authentication requires manual user input. As a result, SPNEGO authentication can't be used for automatic XA recovery.

Action

Configure a recovery auth data alias on the XA resource.

J2CA1002E: Invalid MCWrapper {0} from the free pool for resource {1}.

Explanation

The attempt to reserve an MCWrapper failed.

Action

J2CA1003E: Failed to remove MCWrapper {0} from the shared pool.

Explanation

The attempt to remove an MCWrapper failed, causing a potential problem in the shared pool.

Action

J2CA1004I: The Connection Manager received a fatal connection error from the Resource Adapter for the {1} resource. The connections state is: {2}. The exception is: {0}

Explanation

The connection manager was notified by the resource adapter that an error occurred on the connection. This message is logged so that the user can see the exception that was returned.

Action

The connection manager marks the connection as unusable. The connection is removed during the next connection maintenance interval. The purge policy does not apply to this connection. This behavior is normal. If this error appears unexpected, investigate the exception to determine the possible source of the problem.

J2CA1005I: The Connection Manager received a fatal connection error from the Resource Adapter for the {0} resource. The connections state is: {1}. Information might be available in previous messages or exceptions.

Explanation

The connection manager was notified by the resource adapter that an error occurred on the connection. This message is logged so that the user can see the exception that was returned.

Action

J2CA1008E: An exception occurred while Validator {0} was attempting to validate the RAR JavaBean instance {2} : {1}. Bean Validation constraints will not be validated before placing the instance into service.

Explanation

This exception is unexpected and indicates a problem with the Validator implementation. The cause may not be immediately determined.

Action

Check the FFDC and system logs. If the symptom indicates a failure in a Validator implementation other than that supplied by WebSphere Application Server, contact the Bean Validation provider. CMSG0002

J2CA7001I: Resource adapter {0} installed in {1} seconds.

Explanation

The server has installed the resource adapter successfully.

Action

No action is required.

J2CA7002E: An exception occurred while installing the resource adapter {0}. The exception message is: {1}

Explanation

The server could not install the resource adapter.

Action

Read the exception message for information.

J2CA7006E: The server could not create a download location at {0} for the {1} resource adapter.

Explanation

When trying to download a resource adapter to install, the server could not create the download directory.

Action

Ensure that there is enough disk space for the download.

J2CA7009I: The resource adapter {0} has uninstalled successfully.

Explanation

The server has uninstalled the resource adapter successfully.

Action

No action is required.

J2CA7010E: An exception occurred while uninstalling the resource adapter {0}. The exception message is: {1}

Explanation

The server could not uninstall the resource adapter.

Action

Ensure that the resource adapter is in a state where it can be uninstalled.

J2CA7012I: The resource adapter {0} was not installed.

Explanation

The resource adapter could not be installed because of earlier errors.

Action

Check the resource adapter configuration and check the logs for errors during the resource adapter install.

J2CA7013E: It is not possible to install multiple resource adapters or other artifacts called {0}.

Explanation

The resource adapter name must be unique. This might be because multiple resource adapters or other artifacts have been configured to have the same name, or a single resource adapter has been deployed both by configuration in the server.xml file and by putting the resource adapter in the dropins directory.

Action

If multiple resource adapters or other artifacts have the same name, remove or rename one of them. If a single resource adapter has been deployed in two different ways, change the configuration so that only one deployment method is used.

J2CA7014W: The resource adapter {0} could not be installed as it could not be found at location {1}.

Explanation

The server could not find the resource adapter at the specified location (or relative locations if it was a relative path).

Action

Check that the location defined is correct for the resource adapter.

J2CA7018I: Installing resource adapter {0}.

Explanation

The resource adapter is being installed.

Action

No action is required.

J2CA7020I: Resource adapter {0} is not updated.

Explanation

The resource adapter could not be installed because of earlier errors.

Action

Check the resource adapter configuration and check the logs for errors during the resource adapter install.

J2CA7021E: Resource adapter {1} at location {0} is invalid.

Explanation

The archive or directory at the specified location is not valid so the resource adapter cannot be installed.

Action

Ensure the identified archive or directory is valid.

J2CA7022W: Resource adapter {0} has not installed in {1} seconds.

Explanation

The resource adapter did not install in the expected time. This could be because the server is overloaded or the resource adapter is large. If the resource adapter is installing as part of server startup, the server startup will finish without waiting for the resource adapter to install.

Action

If the resource adapter takes a long time to install, then no action is required; otherwise, check the server logs to see if other messages indicate a cause.

J2CA7053E: An exception occurred while trying to uninstall the {0} resource adapter automatically.

Explanation

The installed resource adapter could not be found on the server.

Action

No action is required.

J2CA7056E: An exception occurred while trying to automatically install the {0} resource adapter.

Explanation

The resource adapter could not be installed by the server.

Action

No action is required.

J2CA7059E: The {0} resource adapter installed from {1} was deleted while it is still configured.

Explanation

A resource adapter that is currently configured in the server.xml file was deleted.

Action

If the deletion was intentional, remove the resource adapter configuration from the server.xml file.

J2CA7060W: The application server is unable to monitor the {0} resource adapter.

Explanation

An resource adapter was installed but monitoring was not started on it. If a file is updated within the resource adapter, the change will not be detected by the server.

Action

When updating files in this resource adapter, manually uninstall and re-install the resource adapter into the server.

J2CA7702E: Application {0} encountered a parse error when processing application descriptor {1}: {2}

Explanation

An error occurred while parsing the application descriptor. No modules will be available for the application.

Action

See the exception information for additional details. Review the contents of the application descriptor to ensure that the contents are valid as XML data.

J2CA8001I: The {0} {1} is unavailable.

Explanation

This message is for informational purposes only.

Action

No action is required.

J2CA8006I: The {0} {1} in {2} is unavailable.

Explanation

This message is for informational purposes only.

Action

No action is required.

J2CA8010W: Unrecognized {0} property: {1}

Explanation

A configured property is not recognized.

Action

Correct or remove the configured property.

J2CA8011E: Value {0} is not supported for {1} on {2}

Explanation

A configured value is not supported.

Action

Correct the value or remove the configured property.

J2CA8020E: Unable to load or access files in library {0}

Explanation

Files cannot be loaded from the shared library.

Action

Verify the file permissions and configuration of the shared library.

J2CA8022E: Application {0} does not have any shared libraries that provide {1} for {2} {3}.

Explanation

To use application-defined data sources, the JDBC driver that provides the data source class must be made available as a shared library for the application.

Action

Add the JDBC driver as a shared library for the application.

J2CA8030E: Unable to find {0} {1} for {2} {3}.

Explanation

The specified resource requires another resource which is not available.

Action

Verify that the resource is configured properly.

J2CA8040E: {0} {1} is only permitted to have one {2} element.

Explanation

The resource cannot have more than one element of the specified type.

Action

Update the configuration so that there is only one element of the specified type associated with the resource.

J2CA8050I: An authentication alias should be used instead of defining a user name and password on {0}.

Explanation

It is recommended to use an authentication alias instead configuring a user name and password on a resource.

Action

Configure the user name and password in on authData element instead of directly on the resource.

J2CA8060E: {0} is not a valid parameter for the action {1}.

Explanation

Parameters specified for an action must correspond to parameters valid for the given action.

Action

Specify valid parameters for the action which is being invoked.

J2CA8061E: {0} is not a valid action for the {1} MBean.

Explanation

An attempt was made to invoke an action that was not available for the specified MBean.

Action

Change the action being invoked to a valid method for the specified MBean.

J2CA8062E: The {0} attribute is not valid for the {1} MBean.

Explanation

An attempt was made to get or set an attribute that was not available for the specified MBean.

Action

Change the attribute specified to one of the available attributes for this MBean.

J2CA8070I: A connection that was obtained from {0} was not closed. The following stack identifies the code that obtained the connection: {1}

Explanation

A connection was not closed by the code that obtained it. The stack identifies one area of the code where an unclosed connection occurs, but other instances might exist elsewhere. To avoid cluttering the logs and minimize the impact of collecting stacks, only one occurrence is reported per server start.

Action

Using the stack as a guide, locate the code that requests the connection and update it to close the connection.

J2CA8500E: An error occurred while attempting to configure a property {0} of configuration element {1} on the class {2}: {3}.

Explanation

A property could not be configured on the specified resource due to an error.

Action

Make corrections to the configuration of the specified resource and retry.

J2CA8501E: Property {0} of configuration element {1} cannot be set because it is not found on the class {2}.

Explanation

A property could not be found on the specified resource.

Action

Make corrections to the configuration of the resource.

J2CA8504E: The sub-element {0} is not correct for the configuration element {1}.

Explanation

The type of configuration properties list is incorrect for the specified configuration element.

Action

Update the configuration to use a configuration properties list that corresponds to the desired type of resource.

J2CA8505E: The destination property cannot be configured on the activation specification because destination {0} is not an instance of the interface that is specified as the destinationType: {1}.

Explanation

A destination type was specified that does not match the destination.

Action

Update the server configuration or the application to specify a destination type that is consistent with the destination.

J2CA8510E: A timer could not be created for resource adapter {0} within {1} milliseconds.

Explanation

It is taking longer than expected to create the timer.

Action

Verify if there is a high load on the system and consider decreasing it.

J2CA8511E: The server checkpoint request failed because the {0} resource adapter created a timer.

Explanation

Liberty does not support resource adapters that create a timer while applications start when a server checkpoint is requested.

Action

Configure the checkpoint to occur before the application starts by using the beforeAppStart server checkpoint option.

J2CA8512E: A timer could not be created for the {0} resource adapter during the server checkpoint request.

Explanation

Liberty does not support the creation of timers by resource adapters while applications start when a server checkpoint is requested.

Action

Configure the checkpoint to occur before the application starts by using the beforeAppStart server checkpoint option.

J2CA8600E: The work {0} submitted by resource adapter {1} did not start within {2} milliseconds.

Explanation

The attempt to start the work has timed out.

Action

Verify if there is a high load on the system and consider decreasing it, or contact the resource adapter vendor to consider if they should increase the work timeout that they use when submitting work to the JCA work manager.

J2CA8601E: The server checkpoint request failed because the {0} resource adapter submitted work {1}.

Explanation

Liberty does not support resource adapters that submit work while applications start when a server checkpoint is requested.

Action

Configure the checkpoint to occur before the application starts by using the beforeAppStart server checkpoint option.

J2CA8602E: The {0} work that was submitted by the {1} resource adapter was rejected during the server checkpoint request.

Explanation

Liberty does not support the submission of work by resource adapters while applications start when a server checkpoint is requested.

Action

Configure the checkpoint to occur before the application starts by using the beforeAppStart server checkpoint option.

J2CA8623E: Resource adapter {0} attempted to submit work with both ExecutionContext and WorkContext. The combination of ExecutionContext and WorkContext is not supported.

Explanation

The resource adapter submitted work that implements WorkContextProvider and also specified an ExecutionContext. It is not valid to do both.

Action

The resource adapter needs to be updated to choose between WorkContextProvider or ExecutionContext.

J2CA8624E: Resource adapter {0} attempted to submit work with multiple copies of the WorkContext type {1}. Only one WorkContext of each type is supported on a single work submission.

Explanation

The resource adapter submitted work with multiple WorkContext instances of the same type.

Action

The resource adapter needs to be updated to eliminate duplicate WorkContext instances from the WorkContextProvider.

J2CA8625E: Resource adapter {0} either attempted to submit work with a work context type {1} that is not supported or the feature is not enabled.

Explanation

The type of work context is either not supported by the application server or the feature that supports it is not enabled.

Action

Verify if the work context type is supported. If so, verify the feature that supports it is enabled.

J2CA8687E: Hint values for {0} must be of type {1}. Resource adapter {2} specified a value {3} of type {4}.

Explanation

The hint value specified by the resource adapter is of the wrong data type.

Action

Contact the resource adapter vendor to correct the data type of the hint.

J2CA8688E: The work manager is unable to run the work item. See the cause exception: {0}.

Explanation

An error occurred while preparing to run the work item.

Action

Refer to the cause exception for more information.

J2CA8800E: More than one XA resource was returned by the resource adapter {0} for the activation specification {1}.

Explanation

The resource adapter should return only one XA resource for the provided activation specification.

Action

Contact the resource adapter vendor to have them correct their implementation of the getXAResources API so that it complies with the JCA specification.

J2CA8801I: The message endpoint for activation specification {0} and message driven bean application {1} is activated.

Explanation

The message endpoint has been activated, and it is ready to handle incoming messages.

Action

No action is required.

J2CA8802E: The message endpoint activation failed for resource adapter {0} due to exception: {1}.

Explanation

The specified exception was generated during message endpoint activation.

Action

Check the specified exception to help in determination of the cause of the error.

J2CA8803E: The message endpoint deactivation failed for resource adapter {0} due to exception: {1}.

Explanation

The specified exception was generated during message endpoint deactivation.

Action

Check the specified exception to help in determination of the cause of the error.

J2CA8804I: The message endpoint for activation specification {0} and message driven bean application {1} is deactivated.

Explanation

The message endpoint has been deactivated, and it will no longer handle incoming messages.

Action

No action is required.

J2CA8807E: The service that provides RRS transactional support is not active. Resource registration is rejected.

Explanation

The service that provides RRS transactional support is not active. Resource registration attempts with the transaction manager are rejected.

Action

Verify that the angel process is active. Verify that MVS user ID of the Liberty process has the appropriate SAF authority to invoke the set of authorized services used for RRS integration. Verify that the feature that provides RRS integration has been configured.

J2CA8809E: Resource {0} from embedded resource adapter {1} is available only to application {2}. An attempt was made to access it from application {3}.

Explanation

An embedded resource adapter, and any of the resources it defines, can be accessed only from the application in which it is embedded.

Action

Ensure that the application only looks up resources that are defined at the server scope or within the same application.

J2CA8810E: The endpoint {0} from embedded resource adapter {1} can be activated only from application {2}. An attempt was made to activate it from application {3}.

Explanation

The endpoint activation failed because it points to an activation specification embedded in another application.

Action

Update the server configuration so that the endpoint uses an activation specification that is either server scoped or embedded in the same application.

J2CA8811E: Resource {0} from embedded resource adapter {1} is available only to application {2}.

Explanation

An embedded resource adapter, and any of the resources it defines, can be accessed only from the application in which it is embedded.

Action

Modify your application or service to look up resources defined at the server scope.

J2CA8812E: The endpoint {0} from embedded resource adapter {1} can be activated only from application {2}.

Explanation

The endpoint activation failed because it points to an activation specification embedded in another application.

Action

Update the server configuration so that the endpoint uses an activation specification that is defined at the server scope.

J2CA8813E: Required property {0} is missing for activation specification {1} of resource adapter {2}.

Explanation

The resource adapter marks certain activation specification properties as required, and the value was not supplied. These properties can be set from two different places: (1) when you create an activation specification configuration object under the installed resource adapter, and (2) from the application itself as an <activation-config-property>.

Action

Supply the required value on the activation specification in the server configuration or in an activation-config-property entry within the application.

J2CA8814E: The id attribute of the resourceAdapter element for resource adapter module {0} contains unsupported characters.

Explanation

The id attribute of the resourceAdapter element can only contain the '.', '-' and '_' characters in addition to alphanumeric characters. The id specified in the configuration or derived from the module name contains unsupported characters.

Action

Provide a valid value for the id attribute of the resourceAdapter element in the server configuration.

J2CA8815E: Multiple resource adapters cannot have the same unique identifier {0}.

Explanation

Multiple resource adapters are configured with or implicitly end up with the same unique identifier (id).

Action

Assign unique identifiers to one or more of the resource adapters so that there is no longer a conflict.

J2CA8816E: The id attribute of the resourceAdapter element for {0} resource adapter module cannot be one of the reserved identifiers {1}.

Explanation

The id specified in the configuration or derived from the module name is a reserved identifier. Reserved identifiers are for internal use only.

Action

Provide an unreserved value for the id attribute of the resourceAdapter element or for the module name in the server configuration.

J2CA8817E: The {0} resource adapter encountered a parse error when it processed the deployment descriptor in the {1} path: {2}

Explanation

An error occurred while the resource adapter parsed the deployment descriptor. The resource adapter will not be available.

Action

See the exception information for additional details. Review the contents of the deployment descriptor to ensure that the contents are valid as XML data. If necessary, work with the resource adapter vendor to resolve the invalid XML data.

J2CA9902E: The resource adapter class {0} annotated with {1} does not implement the {2} interface.

Explanation

The annotated resource adapter class does not implement the required interface.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9903E: The resource adapter class {0} does not implement the {1} interface.

Explanation

The resource adapter class specified in the deployment descriptor does not implement the required interface.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9904E: The resource adapter class {0} is specified; however, the class could not be found in resource adapter {1}.

Explanation

The resource adapter class that is specified in <resourceadapter-class> in the ra.xml file or in a class with the @Connector annotation could not be found in the resource adapter.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9905W: The configuration property {0} is required, however a property definition could not be found in the resource adapter {1}.

Explanation

A property definition could not be found for a required configuration property in the resource adapter.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9906E: The property type {0} specified for configuration property {1} is not valid.

Explanation

A configuration property type must be one of the following: String, Long, Double, Float, Integer, Byte, Character, Boolean, or Short.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9908E: The configuration property {0} was found multiple times within the same scope in resource adapter {1}. Duplicate properties are ignored.

Explanation

A configuration property was defined multiple times within a given scope, such as within an activation specification.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9909E: The configuration property {0} is specified in the wlp-ra.xml file, but a corresponding ConfigProperty annotation, deployment descriptor entry, or Java Bean property is not found in resource adapter {1}.

Explanation

A configuration property was used in the wlp-ra.xml file, but a definition for the property was not found in the resource adapter.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9910E: An <adminobject> element with the interface {0} and class {1} is specified in the wlp-ra.xml file, but a corresponding AdministeredObject annotation or deployment descriptor entry is not found in resource adapter {2}.

Explanation

An <adminobject> element was used in the wlp-ra.xml file, but a definition for it could not be found in the resource adapter.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9911E: A {0} element for type {1} is specified in the wlp-ra.xml file, but a corresponding {2} annotation or deployment descriptor entry is not found in the resource adapter {3}.

Explanation

A <connection-definition> or <messagelistener> element was used in the wlp-ra.xml file, but a corresponding definition for it could not be found in the resource adapter.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9912E: There is no <connection-definition> or class annotated with @ConnectionDefinition although transaction support, authentication mechanisms, or reauthentication support was specified.

Explanation

Transaction support, authentication mechanisms, or reauthentication support can not be specified unless there is at least one <connection-definition> in the ra.xml or there is at least one class annotated with @ConnectionDefinition.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9916W: Translatable messages file {0} for resource adapter {1} defines multiple messages for the same key: {2}.

Explanation

While processing the translation file, a single NLS key was found that is used for multiple messages.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9917W: Translatable messages file {0} for resource adapter {1} does not have a translation message for a key {2} that is specified in the wlp-ra.xml file.

Explanation

No translation message was found for the specified key.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9918W: Resource adapter {1} defines duplicate configuration properties named {0} within the same scope. The duplicates are ignored.

Explanation

A resource adapter, activation specification, administered object, or connection factory definition specifies duplicate configuration properties with the same name.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9919W: The class loader for resource adapter {1} is unable to load {0}. Check if the resource adapter requires a feature that is not enabled or a library that is not accessible to it.

Explanation

The specified class could not be loaded, possibly because the class or a class it depends on is provided by a feature that is not enabled or a library that is not available to the resource adapter.

Action

Enable any features required by the resource adapter, and configure the resource adapter to have access to any libraries that it requires.

J2CA9920W: A duplicate type {0} was specified in {1} and in another entry in the ra.xml file or in one or more classes annotated with {2}.

Explanation

A resource adapter, activation specification, administered object, or connection factory definition has been specified more than once with the same type.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9922E: The resource adapter {0} has multiple classes annotated with @Connector, but does not specify which to use via a deployment descriptor.

Explanation

While multiple @Connector annotated classes are permitted, the class to use for the resource adapter must be explicitly specified in the deployment descriptor.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9924E: The message listener defined in the ra.xml file with type {0} should override the @Activation annotated class {1} but the listener does not contain an activation specification.

Explanation

The ra.xml file contains a message listener type and there is an annotated class for the type, but the ra.xml file does not have a matching activation specification entry.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9925E: Administered object interfaces were not defined via @AdministeredObject annotation and the class {0} did not implement any interfaces.

Explanation

The annotated class must either provide the interfaces in the annotation or implement the interfaces.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9926E: Administered object interfaces were not defined via @AdministeredObject so the interfaces defined on the class will be used; however, there are multiple interfaces on class {0}.

Explanation

The interfaces must be defined in the annotation.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9927E: The annotation @ConfigProperty can only be used on setter methods but was found on {0}.

Explanation

The annotation @ConfigProperty was specified on a method that's name does not start with set.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9930W: The value {0} is less than the minimum of {1} for attribute {2}

Explanation

The configured value does not meet the minimum size constraint for the attribute.

Action

Choose a value equal to or larger than the minimum.

J2CA9931W: The value {0} exceeds the maximum of {1} for attribute {2}

Explanation

The configured value exceeds the maximum size constraint for the attribute.

Action

Choose a value equal to or smaller than the maximum.

J2CA9932W: The value {0} is less than the minimum length {1} for attribute {2}

Explanation

The configured value does not meet the minimum length constraint for the attribute.

Action

Choose a value equal in length or longer than the minimum.

J2CA9933W: The value {0} exceeds the maximum length of {1} for attribute {2}

Explanation

The configured value exceeds the maximum length constraint for the attribute.

Action

Choose a value equal in length or shorter than the maximum.

J2CA9934E: The value {0} is not a valid option for attribute {1}. Valid options are {2}

Explanation

The configured value falls outside the range of valid options for the attribute.

Action

Choose a value from the list of valid options.

J2CA9936W: The default value for the property {0} could not be obtained from an instance of class {1} in resource adapter {2} because an error occurred: {3}

Explanation

An error occurred while attempting to access the default value of a resource adapter JavaBean property.

Action

Review the error and adjust the resource adapter as necessary.

J2CA9937E: The {0} JavaBean {1} configuration property annotated with @ConfigProperty has a getter method return type of {2} that does not match the {3} configuration property type.

Explanation

A configuration property annotated with @ConfigProperty must have a getter method with a return type that matches the configuration property type.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9938E: The {0} JavaBean {1} configuration property annotated with @ConfigProperty does not have a getter method with a return type of {2}.

Explanation

A configuration property annotated with @ConfigProperty must have a getter method with a return type that matches the configuration property type.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9939E: The {0} JavaBean {1} configuration property annotated with @ConfigProperty does not have a setter method with a single parameter of type {2}.

Explanation

A configuration property annotated with @ConfigProperty must have a setter method with a single parameter of a type that matches the configuration property type.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9940E: The {0} JavaBean {1} configuration property annotated with @ConfigProperty has the {2} type set in the annotation that does not match the {3} type of the field.

Explanation

The type set in the @ConfigProperty annotation must match the type of the field it is used on.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9941E: The {0} JavaBean {1} configuration property annotated with @ConfigProperty has the {2} type set in the annotation that does not match the {4} type of the parameter in the setter method.

Explanation

The type set in the @ConfigProperty annotation must match the type of the parameter in the setter it is used on.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9942E: The annotation @ConfigProperty can only be used on a setter method with one parameter but was found on {0} with the following parameters: {1}.

Explanation

The annotation @ConfigProperty must be specified on a setter method that has only one parameter.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9943E: The resource adapter {0} is invalid. It should contain either a deployment descriptor or a JavaBeans class annotated with one of the resource adapter annotations.

Explanation

A valid resource adapter must have either a deployment descriptor or a JavaBeans class that is annotated with one of the following annotations: @Connector, @AdministeredObject, @ConnectionDefinition, @ConnectionDefinitions, or @Activation.

Action

Investigate the vendor documentation and problem determination processes for the resource adapter.

J2CA9944E: The {0} resource adapter can contain either a deployment descriptor or a JavaBeans class that is annotated with one of the resource adapter annotations from the Jakarta Connectors specification. If the resource adapter uses classes from the Java EE Connector Architecture 1.7 or lower version specification (javax.resource.spi package), use the jca-1.7 or lower version feature rather than Jakarta EE features.

Explanation

The resource adapter must have either a deployment descriptor or a JavaBeans class that is annotated with one of the following annotations from the jakarta.resource.spi package: @Connector, @AdministeredObject, @ConnectionDefinition, @ConnectionDefinitions, or @Activation.

Action

Use the jca-1.7 or lower version feature with a resource adapter that implements the Java EE Connector Architecture specification.

J2CA9945E: The {0} resource adapter must have either a deployment descriptor or a JavaBeans class that is annotated with one of the resource adapter annotations from the Java EE Connector Architecture specification. If the resource adapter uses classes from the Jakarta Connectors 2.0 or higher version specification (jakarta.resource.spi package), use the connectors-2.0 or higher version feature rather than Java EE features.

Explanation

The resource adapter must have either a deployment descriptor or a JavaBeans class that is annotated with one of the following annotations from the javax.resource.spi package: @Connector, @AdministeredObject, @ConnectionDefinition, @ConnectionDefinitions, or @Activation.

Action

Use the connectors-2.0 or higher version feature with a resource adapter that implements the Jakarta Connectors 2.0 or higher version specification.