COMPONENT_ALIAS_NOT_SPECIFIED_J2CA0107=J2CA0107I: Component-managed authentication alias not specified for ConnectionFactory or DataSource {0}. The component is accessing the connection factory or data source with res-auth=Application, but no user name or password is available. This might result in an allocateConnection failure. If a valid user name and password in the ConnectionSpec is passed on the getConnection method, or if the backend resource does not require authentication, this error can be ignored. If you are experiencing problems logging in to the backend resource, use the administrative console to specify a component-managed authentication alias for the specified ConnectionFactory or DataSource. FAILED_GETTING_SUBJECT_J2CA0044=J2CA0044E: The Connection Manager failed to get a Subject from the security service associated with ConnectionFactory {0}. Received exception {1} An internal error occurred when getting a Subject. A container-managed authentication alias might not have been selected on the connection factory or data source. Check that a valid container-managed authentication alias is specified on the connection factory or data source. MISSING_TRANSACTION_CONTEXT_J2CA0075=J2CA0075W: An active transaction should be present while processing method {0}. Normal connection management processing requires the presence of a transaction in order to run the current method. Start any transactions that are required to successfully use the connection. CREATE_CONNECTION_FACTORY_EXCP_J2CA0168=J2CA0168E: An exception occurred while trying to instantiate a ConnectionFactory class used by resource {0} : {2}. This indicates a problem while attempting to create a connection factory instance because it caught an Exception from the ManagedConnectionFactory. Check the exception and contact support for the resource adapter which is throwing the exception. POOL_MANAGER_NOT_FOUND_J2CA0695=J2CA0695E: Unable to find primary pool manager during failover processing for a resource with a JNDI name of {0}. An internal error occurred during failover processing. 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/ . IGNORE_FEATURE_J2CA0240=J2CA0240I: Ignored unimplemented feature {0} for resource {1}. The feature is not implemented by the application server. No user action is required. NULL_TRAN_WRAPPER_J2CA0057=J2CA0057E: The interactionPending method was unable to find a transaction wrapper class. This is a WebSphere internal error. 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/ . DESERIALIZATION_FIELD_NOT_FOUND_J2CA0278=J2CA0278W: Could not de-serialize field {0} in class {1}; default value will be used 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. This warning indicates a potential problem, but no user action is necessary unless further errors occur. AUTHENTICATED_SUBJECT_AND_CALLBACK_NOT_SUPPORTED_J2CA0677=J2CA0677E: An authenticated JAAS subject and one or more JASPIC callbacks were passed to the application server by the resource adapter. The resource adapter provided an authenticated JAAS subject to the application server along with one or more JASPIC callbacks. The application server supports the in-flow of authenticated JAAS subjects but only individually and not in combination with the JASPIC callbacks. Modify the resource adapter configuration or source code to pass in either an authenticated JAAS subject or a valid combination of the JASPIC callbacks and not a combination of both. GET_CONTEXT_CLASSLOADER_ERROR_J2CA0226=J2CA0226E: An exception {0} occured when getting or setting the context classloader. Instance ID: {1} This exception is unexpected. The cause is not immediately known. 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/ . NO_ADMIN_OBJECT_EXCP_J2CA0246=J2CA0246E: There is no administered object in the Reference object for method {0}. There is a problem with the Reference object that was initially stored in the JNDI name space. 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/ . MULTIPLE_RESOURCE_ADAPTERS_INCOMPATIBLE_J2CA0636=J2CA0636I: One or more resource adapters entered were not compatible. One or more of the resource adapters had differing deployment descriptors. They cannot all be updated using the same RAR file. Check the resource adapters entered and make sure that their deployment descriptor are alike, or update each resource adapter individually. CONFIG_FAILURE_J2CA0242=J2CA0242W: An error was found in the configuration of a resource. The configuration is {0}. The error is {1}. An error occurred while processing the configuration. Correct the configuration error. NO_SET_METHOD_J2CA0008=J2CA0008W: Class {0} used by resource {2} did not contain method set{1}. Processing continued. There is a missing method on a deployed object. The names of these methods are determined by the name/value pairs contained in the properties of the JavaBean. These are based on the contents of the resource adapter's ra.xml file and class annotations. Processing will continue because the default values for this property might be sufficient, or this particular property might not be required by the specified deployed object. This error could indicate a mismatch between the resource adapter's XML definition or class annotations and the java class provided for implementation of the JavaBean. Examine the attributes supplied by the resource adapter. It might be necessary to provide this failure notification to the provider of the resource adapter. GET_SOURCE_CLASS_CAST_EXCP_J2CA0098=J2CA0098E: A ClassCastException occurred attempting to cast event.getSource to ManagedConnection: {0} The source of the event fired on the listener was not of type ManagedConnection 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/ . CREATE_DATASOURCE_PROPERTIES_EXCP_J2CA0037=J2CA0037E: An exception occurred when trying to read the Data Source Properties for {0} from the namespace: {1}. An internal error has occurred when reading properties from the namespace. 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/ . FAILED_TO_ASSOCIATE_CONNECTION_J2CA0292=J2CA0292E: The ManagedConnection from resource {0} could not be enlisted with the current transaction. An internal error occurred while processing the lazyEnlist() method. 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/ . NON_TRANSACTIONAL_DS_SHARING_J2CA0657=J2CA0657I: Non-transactional datasource {0} cannot have sharable connections. Switching from shareable to unshareable. The data source was configured as non-transactional. Connection sharing applies only to connections within a transaction. To avoid this message, modify the res-sharing-scope on resource references to the non-transactional datasource to unshareable. RA_CONNECTION_ERROR_J2CA0056=J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource {1}. The exception is: {0} 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. 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. SUGGEST_ENABLE_DCU_J2CA0206=J2CA0206W: A connection error occurred. To help determine the problem, enable the Diagnose Connection Usage option on the Connection Factory or Data Source. This is the multithreaded access detection option. Alternatively check that the Database or MessageProvider is available. When the multithreaded access detection option is enabled, the connection manager will detect and indicate whether the usage of a connection handle violates the JCA programming model. Specifically, the connection manager attempts to detect when a handle is used concurrently on multiple threads, and when a handle is shared within a component instance that is different from the component instance that first created the connection. Multithreaded access detection option is only available for DataSource. Enable the multithreaded access detection option on the connection factory or data source which created the failing connection handle, restart the application, and recreate the problem. If the server logs or Runtime Messages facility indicates JCA programming model violations, modify the application to not make the connection handle available to any component instance that did not invoke method getConnection(), nor to any code executing on a thread that did not invoke method getConnection(). IGNORE_PROPERTY_J2CA0241=J2CA0241I: Ignored property {0} because property {1} is configured on resource {2}. The property is ignored because another property has higher precedence. No user action is required. RAR_NEW_VERSION_J2CA0638=J2CA0638I: The version of the new Resource Adapter you are updating to is {0} The version of the Resource Adapter you are updating to is specified in the message. This is an informational message only. None ACTIVATIONSPEC_IMPLEMENTATION_REMOVED_J2CA0642=J2CA0642I: The new RAR file is not compatible with the Resource Adapter. An ActivationSpec class {2} was removed, and there is a configured ActivationSpec that uses the removed type. ActivationSpec name: {0}, JNDI Name: {1}. The new RAR file has removed an ActivationSpec implementation, and the Resource Adapter currently has at least one configured ActivationSpec that makes use of the removed implementation. This makes the Resource Adapter and RAR incompatible for update. Delete the Activation Specifications that use the implementation class that was removed. The configuration for these objects will be lost. ERROR_HANDLING_CALLBACK_J2CA0672=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}. 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. 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. INFINITE_CONNECTION_WAIT_TIMEOUT_J2CA0127=J2CA0127I: A ConnectionWaitTimeout of 0 has been specified for {0}. The request will wait until a connection can be obtained. A ConnectionWaitTimeout of 0 indicates an infinite wait time. This thread will sleep until a connection is freed. There is no user action required. NO_ALIAS_J2CA0114=J2CA0114W: No container-managed authentication alias found for ConnectionFactory or DataSource {0}. The component did not specify a login configuration on the resource-reference to the connection factory or data source, and no container-managed authentication alias was specified on the connection factory or data source. A Subject with empty user/pw is constructed. In some cases, this error may be ignored. If you are experiencing problems logging in to the back end resource, define a login configuration on the resource-reference using a deployment tool. Alternatively, use the Integrated Solutions Console or scripting tools to create the connection factory or data source with the proper container-managed authentication alias. Alternatively, if component-managed authentication is desired, change the resource-ref for the component to res-auth=application. BAD_RAKEY_J2CA0029=J2CA0029E: Unable to obtain a ResourceAdapter key while trying to start a ResourceAdapter. The ResourceAdapter configuration information which makes up the key is either missing or corrupted. The following Exception was caught: {0} This might be a symptom of an incorrectly hand-modified resources.xml document. Alternatively, if you are using an application with an embedded resource adapter, this might be a symptom of an incorrectly hand-modified deployment.xml document. If you have hand-modified either a resources.xml or a deployment.xml file, check the files for any errors. If you have not edited these files, this could be an internal application server error. NO_CONNECTOR_POOL_PROPERTIES_J2CA0006=J2CA0006W: There are no Connection Pooling Properties available for {0}. There is a problem with the Systems Management configuration of the connection factory. The properties for connection pooling do not exist for this connection factory. 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/ . HA_ERROR_J2CA0301=J2CA0301E: ResourceAdapter {0} is not configured properly for High Availability. HA is disabled. Configured HA properties were isEnableHASupport = {1}, and HACapability = {2}. There was a mismatch between isEnableHASupport and the HACapability settings that are configured. Processing continued with high availability disabled. Check that the resource adapter is configured correctly, that it implements the getHACapability() method, and it has the isEnabledHASupport property. DEST_TYPE_INCOMPATABLE_J2CA0160=J2CA0160W: The type of the destination property on ActivationSpec {0} is {1}. You have supplied a destination JNDI name which requires that the destination type be javax.jms.Destination. These are not compatible. The destination supplied by the destination JNDI name will be ignored. The type of the destination property on the activation specification must be javax.jms.Destination if the destination JNDI name is in use. The type on the activation specification is not compatible with this. The JNDI name will be ignored. Take appropriate action based on the exception text. CREATE_ADMIN_OBJECT_EXCP_J2CA0247=J2CA0247E: An exception occurred when trying to read the administered object from the namespace: {1}. An internal error has occurred when reading the administered object from the namespace. 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/ . DELIST_RESOURCE_EXCP_J2CA0031=J2CA0031I: Method {0} caught {1} while trying to delist resources from DataSource {3} from the Transaction Manager for the current transaction and threw {2} There was a problem attempting to delist resources from the transaction manager. This message is for informational purposes. If this message occurs on a regular basis, collect diagnostic information and visit the IBM support site for more information. CFMBEAN_OPERATION_COMPLETED_J2CA0690=J2CA0690I: The {0} operation issued for the resource with a JNDI name of {1} completed successfully. The specified operation completed with no errors. No action is required. ERROR_REGISTERING_MBEAN_J2CA0121=J2CA0121W: An Exception occurred when trying to register an MBean for {0} : {1}. An internal error occurred and the connection manager was unable to create an MBean. The connection factory or the data source will still function, however statistics cannot be accessed through an MBean. This also effects the PMI data that is linked to the MBean. 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/ . SET_METHOD_EXCP_J2CA0036=J2CA0036E: An exception occurred while invoking method set{0} on {1} used by resource {3} : {2}. Processing halted. The set method could not be run. The resource adapter requires this method in order to function correctly. The class files for this ManagedConnectionFactory may be out of date, or there may have been an error communicating between WebSphere systems management and the J2C Runtime. Check that the class files for this resource adapter are up to date. ALERT_HUNG_MODE_J2CA0514=J2CA0514W: Hung Connection Mode Alert for ConnectionFactory or DataSource {0}. Hung connection blocking has ended. Data sources and connection factories can be configured to decide if operations to the backend are not responding in a timely manner (they are hung) based on the configuration thresholds. When hung mode has been entered the connection manager will block all requests for new connections until it detects that the requests to the backend are responding reasonably. If the hang detection has been configured and this alert is enabled, this message indicates that you have exited the hung connection blocking state, and the creation of new connections is now allowed. If your connection factory or data source is spending excessive time in a blocked state you might want to verify the configuration parameters or determine if there are other underlying problems with the backend data source. UNSUPPORTED_UPDATE_DIFFERENT_JCA_VERSIONS_J2CA0659=J2CA0659E: Cannot Update a Resource Adapter and RAR of different JCA versions. Resource Adapter JCA version: {0}. RAR File JCA Version: {1}. Updating to a RAR file that is of a different JCA spec version than the Resource Adapter is not supported. Choose a resource adapter and RAR file which are compatible for update. CONNECTION_POOL_NOT_AVAILABLE_J2CA0165=J2CA0165I: The connection pool is not available. The connection pool is created at first JNDI lookup of a Data Source or Connection Factory. The internal data structures have not been initialized for this connection factory. Some MBean operations are not possible in this state. Attempt the intended operation after the connection factory has been accessed. RA_STOP_FAILED_J2CA0051=J2CA0051E: The attempt to stop ResourceAdapter {0} failed due to the following exception: {1} An exception occurred while attempting to stop a resource adapter. Take appropriate action based on the exception text. ILLEGAL_USE_OF_LOCAL_TRANSACTION_J2CA0295=J2CA0295E: The Connection Manager has detected an attempt to start a Local Transaction within a Global (User) Transaction. Check the application code for correctness. This most likely indicates an error in the application. The application should not start local transactions when it is operating in a global transaction. 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. ALERT_HUNG_MODE_J2CA0504=J2CA0504W: Hung Connection Mode Alert for ConnectionFactory or DataSource {0}. Hung connection blocking has started. Data sources and connection factories can be configured to decide if operations to the backend are not responding in a timely manner (they are hung) based on the configuration thresholds. When hung mode has been entered, the connection manager will block all requests for new connections until it detects that the requests to the backend are responding reasonably. If the hang detection has been configured and this alert is enabled, this message indicates that you have entered the hung connection blocking state, and the creation of new connections is not allowed. If your connection factory or data source is spending excessive time in a blocked state, verify the configuration parameters or investigate for other underlying problems with the backend with which you are trying to communicate. ACTIVATION_STATE_INACTIVE_J2CA0524=J2CA0524I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} is deactivated. The message endpoint exists, and it is disabled from handling incoming messages. There is no user action required. MULTI_THREADED_HANDLE_USE_J2CA0167=J2CA0167W: An attempt to concurrently use the same connection handle by multiple threads has been detected. The connection handle is: {0}. It is a programming model violation to concurrently access a connection handle from multiple threads. Do not share a connection handle by multiple threads. A common cause for this error is the storage of the connection in a Static variable. Additionally, since all servlet instance variable behave the same as static variables, another common cause is the storage of a connection in a servlet instance variable. INVALID_PROPERTY_TYPE_J2CA0047=J2CA0047E: Property {0} for class {1} has an invalid type of {2}. Properties for specified class are only allowed to be primitives, or one the following types: java.lang.Character, java.lang.String, java.lang.Boolean, java.lang.Byte, java.lang.Integer, java.lang.Long, java.lang.Float, java.lang.Double. Ensure the class has implemented the appropriate property type. NO_RA_KEY_EXCP_J2CA0244=J2CA0244E: There is no provider id in the Reference object for method {0}. There is a problem with the Reference object that was initially stored in the JNDI name space. 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/ . AS_LOOKUP_FAILED_J2CA0052=J2CA0052E: The lookup of the Activation Specification with JNDI Name {0} failed due to the following exception: {1} The JNDI lookup of the activation specification failed. This could be caused by one of the following conditions: 1) the activation specification referred to by the specified JNDI name has not been configured, 2) the JNDI Name is incorrect, or 3) some other problem exists as indicated by the exception. Check that the activation specification is configured for the correct resource adapter. Verify that the JNDI Name specified when deploying your MDB matches the name that was specified when creating the ActivationSpec on the resource adapter. BEAN_VALIDATION_VALIDATOR_UNAVAILABLE_J2CA1007=J2CA1007E: An exception occurred while ValidatorFactory {0} was attempting to provide a Validator : {1}. This exception is unexpected and indicates a problem with the ValidationFactory implementation. The cause may not be immediately determined. Check the FFDC logs. If the symptom indicates a failure in a ValidatorFactory implementation other than that supplied by WebSphere Application Server, contact the Bean Validation provider. CMSG0002 POOL_MANAGER_EXCP_CCF2_0002_J2CA0046=J2CA0046E: Method {0} caught an exception during creation of the ManagedConnection for resource {3}, throwing {2}. Original exception: {1} An error occurred during creation of a ManagedConnection. Usually this can be resolved by looking at the error messages from the resource adapter. 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/ . XA_OP_NOT_SUPPORTED_J2CA0016=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. 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. Modify the logic to separate the resource usage into separate transactions. MULTIPLE_RESOURCE_ADAPTERS_COMPATIBLE_J2CA0635=J2CA0635I: The Resource Adapters entered are all compatible. All of the resource adapters compared have compatible deployment descriptors, so they can all be updated using the same new RAR file. None NO_ACTIVATION_CONFIG_PROP_J2CA0306=J2CA0306I: Application {0} has provided no [activation-config-property] for the ActivationSpec class {1} of ResourceAdapter {2}. This may have undesirable effects. No value was supplied for the [activation-config-property]. This may be normal. If a value is required, then not having a value could cause a failure. Supply a [activation-config-property] if one is required. DESTJNDI_TYPE_WRONG_REQUIRED_J2CA0163=J2CA0163E: The type of the object referred to by the supplied destination JNDI name is wrong. The object must implement javax.jms.destination. Destination is a required property for this Activation Specification. The destination JNDI name was: {0}. The supplied object class was {1}. The type of the destination property on the activation specification must be javax.jms.Destination if the destination JNDI name is in use. The type on the activation specification is not compatible with this. The JNDI name will be ignored. Supply a destination JNDI name that refers to an adminstered object class that implements the javax.jms.Destination interface. INVALID_CUSTOM_PROP_VALUE_DEFAULT_USED_J2CA0693=J2CA0693W: A value of {0} was specified for the {1} custom property defined for the resource with JNDI name of {2}. The value is not valid. The default value of {3} is being used. A value that is not valid was provided for the custom property being defined. The default value is being used. Verify that the value for the custom property being defined is valid. XA_RESOURCE_ADAPTER_OPERATION_ID_EXCP_J2CA0027=J2CA0027E: An exception occurred while invoking {0} on an XA Resource Adapter from DataSource {3}, within transaction ID {1} : {2}. There was a problem processing the given method. The processing within the method did not complete successfully. 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 CONNECTION_CLOSED_NULL_HANDLE_J2CA0148=J2CA0148W: A null ConnectionHandle was found in the CONNECTION_CLOSED ConnectionEvent {0} A CONNECTION_CLOSED ConnectionEvent is required by the Java EE Connector Architecture to contain a valid connection handle associated with the ManagedConnection instance. The resource adapter must use ConnectionEvent.setConnectionHandle() to supply the connection handle in the CONNECTION_CLOSED ConnectionEvent. SET_METHOD_EXCP_J2CA0007=J2CA0007W: An exception occurred while invoking method set{0} on {1} used by resource {3} : {2}. Processing continued. There was a problem invoking a method on a deployed object. The names of these methods are determined by the name/value pairs contained in the properties of the JavaBean. These are based on the contents of the resource adapter's ra.xml file and class annotations. Processing will continue because the default values for this property might be sufficient, or this particular property might not be required by the specified deployed object. This error could indicate a mismatch between the resource adapter's XML definition or class annotations and the java class provided for implementation of the JavaBean. Examine the attributes supplied by the resource adapter. It might be necessary to provide this failure notification to the provider of the resource adapter. MULTIPLE_CONNECTION_DEFINITIONS_J2CA0287=J2CA0287E: {0} does not have a single ConnectionDefinition. The program will attempt to continue using the first ConnectionDefinition. There is no connection definition that is defined, or there is more than one connection definition that is defined. There could be an internal XML formatting error. Ensure that there is only a single connection definition defined. ATTEMPT_TO_SHARE_LTC_CONNECTION_J2CA0086=J2CA0086W: Shareable connection {0} from resource {1} was used within a local transaction containment boundary. Shareable connections are not allowed within a boundary for local transaction containment. The connection was made non-shareable. This might have adverse effects. ERROR_FINDING_CACHED_PMIDATA_J2CA0111=J2CA0111W: An Error occurred when trying to find a cached instance of J2CPerf. An internal error occurred when trying to obtain a cached instance of J2CPerf. 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/ . WRONG_CLASSLOADER_J2CA0142=J2CA0142E: Classloader is not an instance of CompoundClassLoader. This exception is unexpected. The cause is not immediately known. 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/ . RESOURCEADAPTER_IMPLEMENTATION_CHANGE_J2CA0639=J2CA0639I: The new RAR file is not compatible with the Resource Adapter. The ResourceAdapter implementation class has changed. The new RAR file has a different ResourceAdapter implementation class. This makes the Resource Adapter and RAR incompatible for update. None MCWRAPPER_GETINSTANCE_ERROR_J2CA0096=J2CA0096E: NullPointerException on setManagedConnection on MCWrapper {0} The attempt to create a new MCWrapper failed, causing a NullPointerException on use. 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/ . FILETRANSFER_ERROR_OCCURRED_J2CA0649=J2CA0649E: An exception occurred while attempting to transfer the RAR file. exception: {0} An error occurred during the file transfer process, and the RAR file could not be sent. The update process cannot continue. Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. NULL_CONNECTOR_NAME_EXCP_J2CA0012=J2CA0012E: The connector name is null in the Reference object for method {0}. There is a problem with the Reference object that was initially stored in the JNDI name space. 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/ . CREATE_CONNECTOR_REFERENCE_EXCP_J2CA0014=J2CA0014I: An exception occurred while building the Reference for JNDI deployment of {0} : {1}. This error was absorbed and a null returned from the method. A problem occured creating the Reference object to be stored in the JNDI name space for the named resource. This problem will be detected and logged as an error later in the processing. Refer to the additional information that is provided to find related error messages and information from the log file. NULL_OBJECTNAMES_J2CA0112=J2CA0112W: Factory or provider name for {0} was null. The ObjectNames factory : {1} provider : {2} cannot be used by PMI to link the PMI statistics with the MBeans. An internal error has occurred. The MBeans should be created when binding the referenceable object into JNDI and during a JNDI lookup. Both ObjectNames will be set to null and the PMI Data will be created, but will not link with the MBeans. If attempting to look up resources on one server that reside on another, this may be normal behavior. Depending on timing the target server may not have created connection factory MBeans by the time the source server does the JNDI lookup of the connection factory in question. If the MBeans had been created, the PMI data will be created. If the MBeans had not been created, the PMI data will not be created, and the informational message J2CA0112W results. If attempting to look up resources on one server that reside on another, ensure that the target server is running before doing a JNDI lookup of a connection factory or data source. ENLIST_FAILED_J2CA0074=J2CA0074E: Unable to enlist connection from resource {2} with current transaction in method {0} due to exception. Initiating destruction of connection. Exception is: {1} 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. 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/ . CREATE_METHOD_FAILED_J2CA0068=J2CA0068E: Method {0} could not create {1} instance. An internal error occurred. This message is due to an error in the internal connection manager processing. Collect diagnostic data and visit the IBM support site for more information. ENLIST_RESOURCE_EXCP_J2CA0030=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}. 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. 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. CFMBEAN_OPERATION_EXECUTION_FAILURE_J2CA0688=J2CA0688W: The {0} operation issued for the resource with a JNDI name of {1} failed. Cause: {2} Read the problem description provided as part of the message. Verify that the operation is for the correct resource. HA_EXCEPTION_RETRIEVING_CAPABILITY_J2CA0309=J2CA0309W: An exception occurred while invoking method returnHACapability() on resource adapter {0}. The configured high availability capability {1} will be used. The high availability capability that is supported by the resource adapter could not be obtained because an unexpected exception occurred when method returnHACapability() was invoked for the specified resource adapter. The connection manager will use the high availability setting that is already configured. This is an exception within the resource adapter. See the support Web site for the resource adapter provider for more information. REQUIRED_PROPERTY_MISSING_J2CA0282=J2CA0282W: Required property {0} was missing from the Activation Specification. The required property was missing from the activation specification. Supply a correct property in the activation specification ERROR_READING_DS_MBEAN_PROPS_J2CA0119=J2CA0119W: An Exception occurred when reading properties for a Data Source MBean {0}. Usually this means an internal error has occurred. The MBean for the data source will not have all the information that you might expect (some operations will return bad values). The data source instance managed by the MBean is still useable, and this warning will not adversely effect any applications. 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/ . CREATE_ACTIVATION_SPEC_FAILED_J2CA0129=J2CA0129E: An exception occurred while trying to instantiate the ActivationSpec class {0} used by ResourceAdapter {1} : {2}. There was a problem attempting to create the ActivationSpec JavaBean instance. There are several possible reasons for this problem. The most common reason is that the connection manager could not find the class for the activation specification using the context class loader. This error could also be related to a resource adapter XML definition which is not valid. 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/ . HANDLE_NOT_CLOSED_J2CA0055=J2CA0055W: Connection handle not closed at end of the unit of work scope. Handles will be closed by the Connection Manager. 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. Inspect your application and ensure that the connection handles are closed before the associated unit of work ends. FIND_OTHER_RAS_NONNODE_TARGET_J2CA0655=J2CA0655E: The findOtherRAsToUpdate command can only be called specifying a node scoped resource adapter. Resource adapters in other scopes are only copies of node scoped resource adapters. Specify a node scoped resource adapter on the command to find copies that need to be updated. DEST_DOES_NOT_EXIST_J2CA0162=J2CA0162W: You have supplied a destination JNDI name for ActivationSpec {0}. This ActivationSpec class lacks the setDestination() method. The destination JNDI Name will be ignored. You do not need to supply a destination JNDI name. Do not supply a destination JNDI name. EXECUTION_CALLBACK_SUBJECT_MISMATCH_J2CA0673=J2CA0673W: The execution subject provided by the WorkManager does not match the subject supplied by the {0}. 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. 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. SYSTEM_PROPERTY_NOT_FOUND_J2CA0228=J2CA0228E: System property {0} not found. The expected system property cannot be found. This may cause subsequent failures. 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/ . PATH_EXPAND_FAILED_J2CA0042=J2CA0042E: An Exception occurred while trying to expand part of a path. The failing piece is {0}. The exception is: {1} Check the path string that failed and verify that any non-expanded variables are valid (including their case). Fix any variables which are not valid. SECURITY_CONTEXT_NOT_ASSOCIATED_J2CA0671=J2CA0671E: The WorkManager was unable to associate the provided SecurityContext to the Work instance. The WorkManager encountered a problem while establishing and setting up the security context for the inbound Work request. Check the FFDC and server logs for messages J2CA0668E and J2CA0669E to determine the cause. NO_RA_EXCEPTION_J2CA0216=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. 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. 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. BAD_CFKEY_J2CA0072=J2CA0072E: Unable to obtain a Connection Factory or Data Source configuration ID while trying to start a ResourceAdapter. The Connection Factory or Data Source configuration information which makes up the ID is either missing or corrupted. The following Exception was caught: {0} This might be a error associated with a hand-modified resources.xml document. Alternatively, if you are using an application with an embedded resource adapter, this might be a error associated with a hand-modified deployment.xml document. If the resources.xml or a deployment.xml file has been modified by hand, verify that there are no errors. If you have not edited these files, this could be an internal error. CLASS_CAST_EXCEPTION_J2CA0065=J2CA0065E: ClassCastException tried to cast : {0} to {1}. {2} This is an internal error. 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/ . CREATE_MCF_PROPERTIES_EXCP_J2CA0038=J2CA0038E: An exception occurred when trying to read the ManagedConnectionFactory Properties for {0} from the namespace: {1}. An internal error has occurred when reading properties from the namespace. 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/ . USING_DEFAULT_THREAD_POOL_J2CA0290=J2CA0290W: Thread pool {0} will be used. The thread pool that was specified for the resource adapter has not been configured. Configure the missing thread pool. BEAN_VALIDATION_SERVICE_UNAVAILABLE_J2CA1004=J2CA1004E: RAR Bean Validation has been disabled, because the BeanValidationService is unavailable. Validation constraints of RAR JavaBean instances will not be validated before the instances are placed into service. This indicates an unexpected problem with the BeanValidationService. The cause may not be immediately determined. 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/ . NULL_RA_KEY_EXCP_J2CA0245=J2CA0245E: The provider id is null in the Reference object for method {0}. There is a problem with the Reference object that was initially stored in the JNDI name space. 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/ . WAS40_DS_ISOLATION_UNSUPPORTED_J2CA0218=J2CA0218E: Version 4 data sources are not supported for isolated JDBC providers. The data source name is: {0} You cannot configure a Version 4 data source under this JDBC provider because the provider is configured to be isolated. Set this JDBC provider to not be isolated, or configure this Version 4 data source under a JDBC provider that is not configured to be isolated. CREATE_DETAILS_FAILED_J2CA0019=J2CA0019W: No Managed Connection Factory Properties data could be assembled for {0}. Processing continued. The properties for the ManagedConnectionFactory could not be assembled because of other logged errors. This might cause problems at runtime, depending on the default values of the various properties that are provided by the resource adapter. Check for other related messages that could further explain the specific problems with the property data. If your connections appear to work, you may ignore this message. Otherwise, attempt to follow the "User Response" sections in the other error messages. ERROR_CLEANUP_MC_J2CA0062=J2CA0062W: Encountered an error while cleaning up the ManagedConnection {0} : {1} The cleanup operation on a managed connection failed. The connection could not be cleaned up after recovery. 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/ . GET_CONFIGPROPERTY_FAILED_J2CA0066=J2CA0066E: Failed calling get method {0} on the ManagedConnectionFactory {1} used by resource {4} with the value {2}. Exception is {3}. The resource adapter does not support the getter method as documented. Visit the support site for the developer of the resource adapter. CALLBACK_SECURITY_NAME_MISMATCH_J2CA0675=J2CA0675E: The user name {0}, provided by the PasswordValidationCallback, and the user name {1}, provided by the CallerPrincipalCallback, do not match. User names provided by the PasswordValidationCallback and the CallerPrincipalCallback must match. 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. EXCEPTION_DURING_COMPARISON_J2CA0644=J2CA0644E: An exception occurred while retrieving class changes for the comparison. The Resource Adapter comparison was unable to complete. Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. POOL_MANAGER_EXCP_CCF2_0001_J2CA0045=J2CA0045E: Connection not available while invoking method {0} for resource {1}. A connection wait timeout has occurred. A ConnectionWaitTimeoutException was created. Reconfigure the connection pool. Increase the maximum number of connections or increase the connection wait time to avoid this error. NULL_LOCAL_TRAN_J2CA0097=J2CA0097E: The call to ContainerComponentMetaData.getLocalTran returned null: {0}. An unexpected null value was returned from ContainerComponentMetaData.getLocalTran(). 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/ . ATTEMPT_TO_DESTORY_CONNECTION_IN_USE_J2CA0088=J2CA0088W: The ManagedConnection that is being destroyed from resource {1} is in an invalid state {0}. Processing will continue. An internal error has occurred. 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/ . FORCEFULLY_DEACTIVING_ENDPOINTS_J2CA0049=J2CA0049W: ResourceAdapter {0} is being stopped with message endpoints still activated. These enpoints will be forcefully deactivated. Resource adapters should be stopped only after all message endpoints have been deactivated. Message endpoints are deactivated when the application that is supplying the message endpoint is stopped. Currently, only MDB can be a message endpoint. Stop any applications that contain message endpoints that are associated with a particular resource adapter before you stop that resource adapter. NODE_AGENT_NOT_RUNNING_J2CA0696=J2CA0696E: The node-scoped resource adapter {0} could not be updated, because the node agent on node {1} of cell {2} is not running. The node agent for the selected node must be running in order to update a node-scoped resource adapter using the deployment manager. Start the node agent, and retry the update operation. PROPERTY_TYPE_MISMATCH_J2CA0281=J2CA0281W: When merging user-defined property {0}, its type, {1}, did not match the type of the merged config and introspected properties, {2}. Keeping the merged config and introspected type. User-defined properties of a resource adapter or an activation specification will override their corresponding introspected and configuration properties unless the type does not match. Check the type of the user-defined configuration property. XML_FORMAT_ERROR_J2CA0126=J2CA0126W: Invalid format for value of element {0} in node {1} of XML document {2}. Returning {3}. The XML document is not formed correctly. See the XML document for possible errors. PROPERTY_TYPE_MISMATCH_J2CA0280=J2CA0280W: When merging config property {0}, its type, {1}, did not match the introspected type, {2}. Keeping the introspected type. Configuration properties of a resource adapter or activation specification override their corresponding introspected properties, unless the type does not match. Check the type of the configuration property. FREEPOOL_GETFREECONNECTION_ERROR_J2CA1002=J2CA1002E: Invalid MCWrapper {0} from the free pool for resource {1}. The attempt to reserve an MCWrapper failed. 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/ . ACTIVATION_HA_INBOUND_DISABLED_J2CA0526=J2CA0526I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} cannot be activated nor deactivated because inbound messaging on ResourceAdapter {2} is currently disabled by the High_Availability (HA) Manager. The HA Manager controls the activation of inbound messaging for resource adapters that have enabled HA capability. Message endpoints can be paused and resumed after the HA manager activates inbound messaging on the resource adapter. Avoid pausing or resuming message endpoints that are not yet activated by the HA manager. TRAN_RECOVERY_SETUP_FAILURE_J2CA0048=J2CA0048E: The setup of XA Transaction recovery for inbound message support did not complete for ResourceAdapter {0}. The following exception was caught: {1} The server could not enable transaction recovery for this resource adapter. The possible causes include: errors in the archive, class, or native paths; internal server errors. Validate your archive, class, and native paths on the connection factory. REACTIVATION_FAILED_J2CA0156=J2CA0156E: The Message Endpoint re-activation failed during a resume operation on a ResourceAdapter. The ActivationSpec was {0}, the MDB Application was {1}, and the exception was: {2} This exception is unexpected. The cause is not immediately known. See the exception and other log entries for more details. AS_ALIAS_LOOKUP_FAILED_J2CA0155=J2CA0155W: The lookup of the AuthenticationAlias {0}, assigned to the ActivationSpec {1} by application {2} has failed. The activation specification in use by the given MDB had an authentication alias which failed to return a valid credential object. Check that the authentication alias has been properly configured and assigned to the activation specification configuration, or specified as part of the MDB deployment step. UNEXPECTED_UPDATE_EXCEPTION_J2CA0646=J2CA0646E: An unexpected exception occurred in the Update service, exception: {0} An unexpected exception occurred in the Update service. Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. TRANSACTION_SYNCHRONIZATION_REGISTRY_UNAVAILABLE_J2CA0316=J2CA0316E: The application server is unable to make an instance of the TransactionSynchronizationRegistry available to the BootstrapContext for provider id {0}. The BootstrapContext was unable to return a TransactionSynchronizationRegistry to the resource adapter due to an internal problem. The resource adapter cannot directly interact with the Transaction Manager until the problem is resolved. Please review the FFDC log files for potential actions to resolve this problem. ERROR_EXTRACTING_ARCHIVE_J2CA0651=J2CA0651E: An exception occurred while attempting to extract the archive {0} to {1}. Exception: {2} An exception occurred while attempting to extract the rar file to the destination location. The exception information may relate to a remote node if the update was being performed on a remote Resource Adapter. Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for the local machine. If attempting to update a resource adapter on a remote node, check the logs on that node as well. HA_WARNING_J2CA0303=J2CA0303E: Attempting to {0} ResourceAdapter {1} while under HA control. This indicates a suspend/resume operation was attempted while high availability is enabled. Only outbound portions of the resource adapter will be suspended or resumed. 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/ . NO_RESOURCE_ADAPTER_DD_J2CA0002=J2CA0002W: There is no Resource Adapter Deployment Descriptor available for {0}. There is a problem with the Systems Management configuration for the resource adapter. A deployment descriptor does not exist for this resource adapter. Check that file resources.xml exists and that it contains a [resourceProviders xmi:type="resources.j2c:J2CResourceAdapter" . . .] element. If the file does not exist, or if the file appears to be incorrect, delete it and re-create the resource adapter through the Integrated Solutions Console. INVALID_ACTIVATION_CONFIG_PROP_J2CA0131=J2CA0131E: Application {0} has an [activation-config-property], {1}, which is not valid for the ActivationSpec class {2} of ResourceAdapter {3} and cannot be set. This may have undesirable effects. A set method does not exist for listed [activation-config-property] on the ActivationSpec JavaBean class of the given resource adapter. This could be caused by: (1) the application's MDB was mapped to the wrong ActivationSpec class or MessageListenerType, (2) there is a case mismatch between the [activation-config-property] name and the actual method, or (3) the application assembler entered a non-existing property. Redeploy the application and correct any mapping errors, or reassemble the application with valid [activation-config-property] values. ATTEMPT_TO_USE_PRETEST_CONNECTION_J2CA0286=J2CA0286W: Connection {0} from resource {1} cannot be used with pretest connection configured. Turning off pretest connection support for this Resource Adapter. This connection's resource adapter does not support the pretest connection function. Reconfigure pretest connection to false for this resource adapter. ERROR_CREATE_PMIDATA_J2CA0279=J2CA0279W: An Error occurred when trying to create pmi data. This exception is unexpected. The cause is not immediately known. 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/ . CREATE_RA_CONNECTION_FACTORY_EXCP_J2CA0018=J2CA0018E: An exception occurred while trying to create Resource Adapter ConnectionFactory {0} : {1}. There was a problem with the resource adapter creating the desired connection factory. The exception text provides additional details on the actual problem. If the exception text does not indicate a situation that is user controlled, collect diagnostic data and refer to the IBM support site for additional information. NONEXISTENT_ACTIVATION_CONFIG_PROP_J2CA0291=J2CA0291I: Application {0} has an <activation-config-property>, {1}, for which there is no corresponding property on the ActivationSpec class {2} of ResourceAdapter {3}. This property will be ignored. This may have undesirable effects. The application EAR file has supplied an [activation-config-property] that does not exist. Fix the application descriptor. FAILED_TO_ASSOCIATE_CONNECTION_J2CA0058=J2CA0058E: The ConnectionManager was unable to associate Connection {0} with ManagedConnection {1} for resource {3}. Received exception: {2} 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. Inspect the application and ensure that the transaction is committed as soon as possible after connections are closed. PROPERTY_NOT_FOUND_J2CA0284=J2CA0284W: Resource property {0} is skipped. The property was not found through introspection on the underlying bean. Compare this property in the ra.xml file and the JavaBean. UNABLE_TO_INITIALIZE_WM_J2CA0135=J2CA0135E: Unable to initialize a WorkManager for provider id: {1} with the following thread pool: {0}, due to an exception. The exception will not be re-thrown. The exception is: {2}. The BootstrapContext was unable to return a WorkManager to the resource adapter due to a problem configuring the WorkManager. See the exception and previous log entries for more details. ALERT_SERIAL_REUSE_VIOLATION_J2CA0511=J2CA0511W: Serial Reuse Violation Alert for ConnectionFactory or DataSource {0}. An attempt to concurrently share a connection within an Local Transaction Containment boundary has been detected. This is a violation of the Serial Reuse Alert checking. If callstack capture is enabled the callstack at the time the connection was requested will be provided in the alert contents. When applications manage interactions with the backend data source, two connections that are mapped to a single managed connection can cause data integrity problems, because there is no owner that is in charge of the commit or rollback calls. If this is attempted, the second managed connection will be returned. If this is unexpected it might cause data integrity problems, and it might cause the use of additional connections. This alert can help detect such situations and provide information that might help determine the problem. For more information consult the documentation on the rules for sharing connection with local transaction containment. PROPERTY_NAME_NOT_FOUND_J2CA0665=J2CA0665E: The connection factory does not have a property with the name {0}. The connection factory does not have a property with the specified name. Possible reasons for the error are the property name is misspelled or incorrectly capitalized, or the specified property does not apply to the connection factory being configured. Verify the property name for the connection factory. Correct any errors in spelling or capitalization. CWTE_RESERVE_POOL_J2CA1011=J2CA1011E: Connection not available; timed out waiting for {0} seconds. Enabling a reserve pool could decrease the number of connection wait timeout exceptions. This occurrs when a connection can not be obtained to a data source. By enabling a reserve pool, the number of connection wait timeout exceptions could decrease, thus increasing performance. No user action required. INVALID_EJB_COMPONENT_J2CA0102=J2CA0102E: Invalid EJB component: Cannot use an EJB module with version {0} using {1}. An attempt to run an EJB component that is incompatible with the application server. Evaluate the EJB version supported by the EJB component, correct any errors that might be present, and redeploy the component. CONFIG_PROPERTY_CHANGED_J2CA0288=J2CA0288I: Configuration property {0} changed from {1} to {2} for pool {3} A pool properties value has changed. There is no user action required. DESTJNDI_TYPE_WRONG_J2CA0161=J2CA0161W: The type of the object referred to by the supplied destination JNDI name is wrong. The object must implement javax.jms.destination. The destination JNDI name was: {0}. The supplied object class was: {1} The type of the destination property on the activation specification must be javax.jms.Destination if the destination JNDI name is in use. The type on the activation specification is not compatible with this. The JNDI name will be ignored. Take appropriate action based on the exception text. INVALID_ACTIVATION_CONFIG_PROP2_J2CA0315=J2CA0315W: The Message Endpoint for ActivationSpec {0} and MDB Application {1} has given an invalid value for the custom property WAS_EndpointInitialState. The value provided for the custom property WAS_EndpointInitialState is not valid. Hence this property will be ignored. Use the administrative console or the wsadmin tool to provide a valid value for the custom property [ACTIVE or INACTIVE]. DELIST_FAILED_J2CA0073=J2CA0073E: Unable to delist connection from resource {2} from transaction in method {0} due to exception. Initiating destruction of connection. Exception is: {1} 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. 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/ . NULL_REQUIRED_OBJECT_J2CA0109=J2CA0109E: Method {0} obtained a NULL {1} where a required object was expected. Throwing exception {2}. This exception is unexpected. The cause is not immediately known. 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/ . UNABLE_TO_START_RA_J2CA0145=J2CA0145W: Unable to start ResourceAdapter due to the following exception: {0}. The server was unable to start a resource adapter. See the exception and previous log entries for more information. FAILED_CONNECTION_J2CA0021=J2CA0021E: An exception occurred while trying to get a Connection from the Managed Connection resource {1} : {0}. The resource adapter created an exception when attempting to call the getConnection() method. The exception text might provide additional information for determining the problem. 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. EXCEPTION_RETRIEVING_CLASS_PROPERTIES_J2CA0643=J2CA0643E: An exception occurred while attempting to retrieve the class names and properties for type {0}, exception was: {1} An exception occurred while attempting to retrieve the lists of class names and properties for comparison. Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory for more information about the exception. Make sure that you have enough access privileges to run the command. INVALID_ACTIVATION_CONFIG_PROP2_J2CA0305=J2CA0305E: Application {0} has an [activation-config-property] which is NULL or blank and is not valid for the ActivationSpec class {1} of ResourceAdapter {2} and cannot be set. This may have undesirable effects. The application assembler entered a property that does not exist or one that is poorly formatted [activation-config-property]. Reassemble the application with a [activation-config-property] that is valid. ALERT_POOL_LOAD_J2CA0508=J2CA0508W: Pool Load Alert for ConnectionFactory or DataSource {0}. The average connection load (or demand) over approximately the last {1} minutes has exceeded your configured threshold of {2}. A connection factory or data source has a maximum available load that is equal to all of its connections that are in continuous use. This equals its current maxConnections setting. At any point, the pool load is the number of connections in use in addition to any threads that are waiting for a connection. The average pool load is average time of the pool load divided by the interval that is configured by this alert. This alert indicates that you have exceeded the pool average load for the last interval. Excessive load on the pool might be caused by a number of factors, including a maxConnnections setting that is too low, a connection percent efficiency that is too low and causes poor connection utilization, or a demand that is outstripping its capacity. Investigate any possible problems and make the appropriate changes. MCERROR_J2CA0081=J2CA0081E: Method {0} failed while trying to execute method {1} on ManagedConnection {2} from resource {4}. Caught exception: {3} The connection manager caught an exception while trying to perform an operation on a ManagedConnection. Since the ManagedConnection is part of the resource adapter, look for messages from the resource adapter to further isolate the problem. CREATE_METHOD_FAILED2_J2CA0069=J2CA0069E: Method {0} could not create {1} instance. Failed with exception: {2} An internal error occurred. This message is an internal error in the connection manager processing. Collect diagnostic data and visit the IBM support site for more information. UNEXPECTED_RA_FOR_DATASOURCE_J2CA0217=J2CA0217E: The {0} data source is associated with a resource adapter that is not the built-in relational resource adapter (RRA). The configuration ID for the resource adapter that is not correct is {1}. If you configured a data source with scripting, the relationalResourceAdapter attribute might have not been set correctly. Check your configuration script to ensure that relationalResourceAdapter is set to "builtin_rra". ACTIVATION_FAILED_J2CA0138=J2CA0138E: The Message Endpoint activation failed for ActivationSpec {0} and MDB application {1} due to the following exception: {2} This exception is unexpected. The cause is not immediately known. See the exception and other log entries for more details. DEACTIVATION_FAILED_J2CA0140=J2CA0140W: The Message Endpoint pause operation failed for ActivationSpec {0} and MDB Application {1} because the endpoint is currently deactivated, stopped, or an unexpected exception occurred deactivating the endpoint. Message endpoints that are stopped or deactivated cannot be paused. Ensure that the message endpoint is activated before invoking the pause operation. If the endpoint is activated, check the exception and other log entries for more details. SET_ONCE_PROP_ALREADY_SET_J2CA0159=J2CA0159E: Internal error. An attempt has been made to change a set once property that has already been set. The property name is {0} This exception is unexpected. The cause is not immediately known. 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/ . REQUIRED_PROPERTY_NOT_SET_J2CA0133=J2CA0133E: For the installed ResourceAdapter {0} and ActivationSpec {1}, required activation specification properties were missing from the activation-config-properties for the MDB being activated. See the following exception for details: {2} 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>, which may be modified using the application assembly tool. Supply the required values on the activation specification, which is configured on the installed resource adapter, or in an [activation-config-property] entry within the application. DEACTIVATION_FAILED_J2CA0139=J2CA0139E: The Message Endpoint deactivation failed for ActivationSpec {0} and MDB application {1} due to the following exception: {2} This exception is unexpected. The cause is not immediately known. See the exception and other log entries for more details. AS_JNDINAME_MISSING_J2CA0054=J2CA0054E: The Message Endpoint activation failed because no Activation Specification JNDI name was supplied. In order to activate a message endpoint (MDB) a JNDI name to a configured activation specification must be supplied during MDB deployment. Check that the activation specification had been configured for the resource adapter you are using. Verify that the JNDI Name specified when deploying your MDB matches that specified when creating the application Spec on the ResourceAdapter. ALERT_CONN_ERROR_J2CA0500=J2CA0500W: Connection Error Alert for ConnectionFactory or DataSoure {0}. This ConnectionFactory or DataSoure has exceeded {1} connection error events in less than {2} minutes. The 'connErrorAlert' has been enabled for this connection factory or data source. The configuration has optional parameters for indicating a time interval and a threshold for the alert so that the message is issued if the number of connection errors that are observed during the time interval by the connection factory or data source exceeds the threshold. If the frequency of connection errors is excessive, investigate the root cause of connection errors, starting with the error log. NO_CONNECTOR_PROPERTIES_J2CA0004=J2CA0004W: There are no Connection Factory Properties available for {0}. There is a problem with the Systems Management configuration of the connection factory. The properties do not exist for this connection factory. 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/ . NULL_PROPERTY_VALUE_J2CA0085=J2CA0085I: Connector property {0} on resource {1} has a null value. A connector property was not given a value, and it does not have a default. The set method is not called. This could be the cause of a later error. No user action is required. UNABLE_TO_RETRIEVE_J2RA_J2CA0645=J2CA0645E: Unable to retrieve the J2C Resource Adapter from the ObjectName provided. The command was unable to retrieve the J2C Resource Adapter from the ObjectName that was provided. Make sure that the ObjectName entered is the correct name for a J2C Resource Adapter. Correct ObjectName syntax can be retrieved by invoking the AdminConfig.list("J2CResourceAdapter") command. CALLERPRINCIPAL_NOT_PROVIDED_J2CA0669=J2CA0669E: The resource adapter did not provide a CallerPrincipalCallback, an execution subject containing a single principal, or an empty execution subject. The WorkManager could not establish the principal of the caller identity because the resource adapter did not supply an instance of a JASPIC CallerPrincipalCallback necessary for the WorkManager to determine the caller principal, nor did the setupSecurityContext method of the SecurityContext implementation return an execution subject containing either an empty principal set or a principal set containing exactly one principal. Contact the resource adapter vendor to determine why the inbound SecurityContext implementation does not satisfy the requirements necessary for the WorkManager to establish the principal of the caller identity. TRANSACTION_SUPPORT_LEVEL_CHANGED_J2CA0237=J2CA0237I: Transaction support level has been changed from {0} to {1} that was returned by the resource adapter. The resource adapter returned a level of transaction support whose ordinal value is equal to or less than the value specified in the metadata of the resource adapter. The JCA specification requires in such case the level of transaction support to be changed a value returned by the resource adapter. No user action is required. BAD_RETURN_VALUE_FROM_ENLIST_J2CA0087=J2CA0087E: The transaction manager was unable to enlist resource {0} from DataSource {1}. 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. 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. USING_DEFAULT_CMCONFIGDATA_J2CA0122=J2CA0122I: Resource reference {0} could not be located, so the following default values are used: {1} An internal error might have occurred, but most likely a direct JNDI lookup was done on a connection factory or data source. Processing will continue using the default resource-ref values. There is no user action required. SERVERS_RUNNING_DURING_UPDATE_J2CA0647=J2CA0647E: All servers under node {0} must be stopped while updating a Resource Adapter on that node. All servers must be stopped on a node while updating Resource Adapters on the node. Stop all running servers within the node. ACTIVATION_STATE_ACTIVE_J2CA0523=J2CA0523I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} is activated. The message endpoint exists, and it is enabled to handle incoming messages. There is no user action required. UNEXPECTED_CONNECTION_EVENT_J2CA0034=J2CA0034E: An unexpected event was received from the Resource Adapter for resource {2}. Expected ConnectionEvent type {0} and received ConnectionEvent type {1}. This is most likely an error with the specific resource adapter. Contact the resource adapter supplier. OBJECT_DESERIALIZE_FAILED_J2CA0201=J2CA0201E: Object cannot be deserialized. The exception stack trace follows: {0} This is an internal system error that is probably caused by a previous error. Examine any related messages to determine the cause of the problem. If there are no related messages, or they do not help resolve the problem, visit the IBM support site. INVALID_OR_UNEXPECTED_SETTING_J2CA0067=J2CA0067W: Invalid {0} setting of {1}. Defaulting to {2} instead. An internal error occurred. Using the default value. This is only a warning. If an error occurs later it may help in diagnosing the problem. Otherwise This can be ignored. INVALID_CONTEXT_COMBINATION_J2CA0223=J2CA0223E: Work task is requested with both execution and work contexts. Resource adapter must not submit a Work that implements WorkContextProvider along with a valid ExecutionContext. Decide which context to use and either do not submit a Work that implements WorkContextProvider or use a null value for the ExecutionContext parameter in WorkManager methods that take it as argument. ASSPEC_CLASSNAME_NOTFOUND_J2CA0134=J2CA0134E: An ActivationSpec JavaBean class name not found for ResourceAdapter {0}. This exception is unexpected. The cause is not immediately known. 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/ . ALERT_SURGE_MODE_J2CA0513=J2CA0513W: Surge Mode Alert for ConnectionFactory or DataSource {0}. Surge mode has been exited. Data sources and connection factories can be configured to limit the rate at which new connections are created based on the configuration thresholds. If the surge feature has been configured and this alert is disabled, this message indicates that you have exited the surge throttling mode whereby the connection creation rate is governed by the surge configuration parameters. If your connection factory or data source is spending excessive time in surge mode you might want to verify the configuration parameters or determine if there are other underlying causes. DEACTIVATE_FAILED_J2CA0152=J2CA0152E: Deactivation of a Message Endpoint failed because the targeted ResourceAdapter, {0}, is not currently started or was not found. Deactivation key is: {1} The given resource adapter could not be found or was not in a started state. The message endpoint could not be deactivated. Check that the resource adapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid resource adapter. Also, applications must be stopped before the resource adapter is stopped. SHAREDPOOL_REMOVESHAREDCONNECTION_ERROR_J2CA1003=J2CA1003E: Failed to remove MCWrapper {0} from the shared pool. The attempt to remove an MCWrapper failed, causing a potential problem in the shared pool. 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/ . INVALID_CUSTOM_PROP_VALUE_J2CA0692=J2CA0692W: A value of {0} was specified for the {1} custom property defined for the resource with JNDI name of {2}. The value is not valid. The custom property is ignored. A value that is not valid was provided for the custom property being defined. The desired behavior will not take effect. Verify that the value for the custom property being defined is valid. UNEXPECTED_ERROR_OCCURED_GETTING_PROPERTY_J2CA0667=J2CA0667E: An unexpected error has occured while getting the value of the connection factory property {0}. The attempt to get the value of the custom property failed. 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/ . NO_SET_METHOD_EXCP_J2CA0035=J2CA0035E: Class {0}, used by resource {2} did not contain method set{1}. Processing halted. The set method does not exist for this class; the connection manager expected this method to exist. The resource adapter requires this set method to be run to function properly, so the ManagedConnectionFactory is discarded. The class file for this ManagedConnectionFactory might be out of date, or there might be a miscommunication between WebSphere Systems Management and the connection manager. Check that the class files for this resource adapter are up to date. RA_CREATION_FAILED_J2CA0043=J2CA0043E: An Exception occurred while trying to instantiate a ResourceAdapter JavaBean instance for the installed ResourceAdapter defined by key {0}. The exception is: {1} The path for the resource adapter has not been configured correctly, or the resources.xml file (or deployment.xml file if you are using an embedded RAR file) is corrupted. Correct the path configuration for the resource adapter or repair the XML configuration file. NULL_THREAD_POOL_MGR_J2CA0157=J2CA0157E: Unable to get the ThreadPoolMgr service. This exception is unexpected. The cause is not immediately known. 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/ . INVALID_USERNAME_PASSWORD_INBOUND_J2CA0674=J2CA0674E: The user name {0} or password provided by the PasswordValidationCallback is invalid. 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. Configure the resource adapter and enterprise information system to use a valid user name and password. VALIDATION_FAILED_INBOUND_J2CA0684=J2CA0684E: Unable to validate the user name {0} and password that is provided by the PasswordValidationCallback. 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. 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. AS_ALIAS_NOT_VALID_J2CA0149=J2CA0149W: The contents of the AuthenticationAlias assigned to the ActivationSpec {0} used by MDB {1} are invalid. The UserName and/or the Password were either null or blank. The AuthenticationAlias was: {2}, its UserName was: {3}, and its Password was: {4} The user name, password, or both assigned to the authentication alias that is being used by the MDB is not valid. Check that the authentication alias has been properly configured and that it is assigned to either the activation specification configuration or specified as part of the MDB deployment step. ALERT_SURGE_MODE_J2CA0503=J2CA0503W: Surge Mode Alert for ConnectionFactory or DataSource {0}. Surge mode has been entered. Data sources and connection factories can be configured to limit the rate at which new connections are created based on configuration thresholds. If the surge feature has been configured and this alert is enabled, this message indicates that you have entered the surge throttling mode, and the connection creation rate is governed by the surge configuration parameters. If your connection factory or data source is spending excessive time in surge mode, you might want to verify the configuration parameters or investigate for other underlying causes. XML_FILE_READ_J2CA0117=J2CA0117I: Properties file {0} with root element {1} was successfully read. This is an informational message. There is no user action required. NULL_PROPERTY_VALUE_J2CA0050=J2CA0050W: Setting of the Connector property {0} on class {1} for resource {2} will be skipped. Property has a null value. A connector property was not given a value, nor does it have a default. The set method is not called. This could be the root cause of a later error. There is no user action required. NO_ACTIVATION_SPEC_PROP_J2CA0300=J2CA0300I: ActivationSpec {0} has no configuration properties. The ActivationSpec class is {1} for ResourceAdapter {2}. This may have undesirable effects. No configuration properties were supplied for the activation specification. This might be normal, but if a value is required then omitting a value could cause a failure. Supply a value if one is required. CONN_FAILOVER_FAILURE_TO_CONNECT_TO_RESOURCE_J2CA0683=J2CA0683E: Connection management failed to connect to the resource with a JNDI name of {0}. Resource fail-over is disabled. Connection management failed to connect to the specified resource. Verify that the JNDI name provided for the resource in question is valid. Verify that the resource is operational. If connection fail-over has been configured for a resource adapter, verify that the version of the resource adapter implements the required infrastructure. RA_NOT_STARTED_J2CA0153=J2CA0153E: The requested ResourceAdapter {0} is not in a started state. The requested resource adapter was found, but it was not in a started state. This might be because it was stopped by an MBean request, the application server might be shutting down, or the resource adapter might be embedded within an application that has stopped. A resource adapter is not usable in a stopped state. Check that the resource adapter is started. ACTIVATE_FAILED_J2CA0151=J2CA0151E: Activation of Message Endpoint for application {0} failed because the targeted ResourceAdapter, {1}, is not currently started. The given resource adapter could not be found or was not in a started state, so the message endpoint could not be activated. Check that the resource adapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid resource adapter. ERROR_CREATING_XA_RESOURCE_J2CA0061=J2CA0061W: Error creating XA Connection and Resource {0} An error occurred recreating an XA resource. The resource could not be recovered. Check for other related messages that can further explain the problem. FAILED_MANAGED_CONNECTION_J2CA0020=J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection: {0}. The pool manager created an exception when attempting to allocate a managed connection. The exception text might provide additional information for determining the problem. 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. CREATE_CONNECTOR_PROPERTIES_EXCP_J2CA0003=J2CA0003E: An exception occurred while trying to read the Connection Factory Properties for {0} : {1}. There is a problem with the Systems Management configuration of the connection factory. The properties do exist for the connection factory, but they are not in the right format to read and process. 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/ . ACTIVATION_GETACTIVATIONPROPS_FAILED_J2CA0521=J2CA0521E: Acquiring Message Endpoint properties for ActivationSpec {0} and MDB Application {1} failed because the Message Endpoint is currently stopped. Message endpoints that are stopped do not have JMS properties at run time. Check that the message endpoint is not stopped before invoking the getActivationProperties() method. MISSING_AUTH_DATA_ENTRY_J2CA0130=J2CA0130I: {0} [{1}] has Component-managed Authentication Alias [{2}] but no corresponding J2C Authentication Data Entry is defined in security.xml. This may have undesirable effects. A J2C authentication data entry corresponding to the component-managed authentication alias was expected but not found. Define a J2C Authentication data entry under Security > JAAS configuration in the administrative console, and choose this entry for the component-managed authentication alias on the connection factory or the data source configuration. NULL_COMPONENT_METADATA_ACCESSOR_EXCP_J2CA0041=J2CA0041E: The ComponentMetaData instance was null in method {0}. This exception is unexpected. The cause is not immediately known. 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/ . RAR_OLD_VERSION_J2CA0637=J2CA0637I: The version of the Resource Adapter you are updating from is {0} The version of the Resource Adapter you are updating from is specified in the message. This is an informational message only. None FAILED_TO_VALIDATE_AS_J2CA0137=J2CA0137E: The ActivationSpec validate() method failed with an InvalidPropertyException. The ActivationSpec is {0}, which belongs to the installed ResourceAdapter {1} and is associated with the MDB application {2}. See the following list of failed properties along with their values: {3}. The exception is: {4} The resource adapter has rejected the activation specification as it is currently configured. See the exception text from the resource adapter for more details. FAILED_TO_GET_TRANSACTION_STATUS_J2CA0064=J2CA0064E: Failed to get transaction status {0} This is an internal error. 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/ . AS_BIND_FAILED_J2CA0158=J2CA0158E: Failed to bind an Activation Specification to the namespace with JNDI name {0}. The associated Resource Adapter key is {1}. This exception is unexpected. The cause is not immediately known. 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/ . INVALID_RESOURCE_ADAPTER_ID_J2CA0697=J2CA0697E: The resource adapter could not be updated because the specified target object identifier {0} does not exist. The object identifier of an existing resource adapter must be specified for the update operation. Verify the object identifier of the target resource adapter, and retry the update operation. ACTION_NOTIFICATION_FAILURE_TO_CONNECT_TO_RESOURCE_J2CA0687=J2CA0687E: Connection management failed to connect to the resource with a JNDI name of {0}. Failure notification action support is disabled. Connection management failed to connect to the specified resource. Verify that the JNDI name provided for the resource in question is valid. If connection fail-over and failure notification action support have been configured for a resource adapter, verify that the version of the resource adapter implements the required infrastructure. ENGLISH_ONLY_MESSAGE_J2CA0093=J2CA0093W: This is an English only message: {0} Message was not translated. See the message text for details. ENGLISH_ONLY_MESSAGE_J2CA0092=J2CA0092E: This is an English only message: {0}. Message was not translated. See the message text for details. ENGLISH_ONLY_MESSAGE_J2CA0090=J2CA0090I: This is an English only message: {0} The message was not translated. See the message text for details. INVALID_TRANSACTION_SUPPORT_LEVEL_J2CA0236=J2CA0236E: The resource adapter returned a runtime level of transaction support whose value is greater than that specified in the metadata of the resource adapter. The transaction support level has not been changed. The metadata value is {0}, the runtime value is {1}. The JCA specification requires that a resource adapter must always return a level of transaction support whose ordinal value is equal to or less than the value specified in the metadata of the resource adapter. To override the transaction level value specified in the metadata of the resource adapter, use a transaction level support value that is equal to or less than the metadata value. CREATE_MANAGED_CONNECTION_FACTORY_DETAILS_EXCP_J2CA0009=J2CA0009E: An exception occurred while trying to instantiate the ManagedConnectionFactory class {0} used by resource {2} : {1}. There was an exception while attempting to create a ManagedConnectionFactory object. There are several possible reasons for this problem. The connection manager (1) could not find the appropriate class for the ManagedConnectionFactory using the context class loader, (2) could not create a TraceWriter object for the ManagedConnectionFactory, or (3) could not create the ConnectionManager object for the ManagedConnectionFactory. Any of these problems could also be related to an XML definition for the resource adapter that is not valid. 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/ . ALERT_THREAD_CONN_LIMIT_J2CA0510=J2CA0510W: Thread Connection Limit Alert for ConnectionFactory or DataSource {0}. The number of connections in use by this thread of execution is {1}. This has exceeded the configured threshold of {2}. If callstack capture is enabled the callstack at the time the connection was requested will be provided in the alert contents. Any single requesting thread which ties up multiple connections can unexpectedly contribute to rapid pool starvation or inefficient use of connection resources. This alert can help detect such situations and provide information that will help with pinpointing the problem. For more information consult the documentation. ALERT_LTC_NESTING_J2CA0509=J2CA0509W: LTC Nesting Level Alert for ConnectionFactory or DataSource {0}. The depth of Local Transaction Containment Nesting for this request is {1}. This has exceeded the configured threshold of {2}. If callstack capture is enabled the callstack at the time the connection was requested will be provided in the alert contents. The nesting of an LTC that is not expected can have side effects of tying up more connections than expected. This alert might help in determining the problem. Refer to the error text and support documentation for more information. INVALID_COPMP_ALIAS_J2CA0215=J2CA0215W: Component-managed authentication alias {0} for ConnectionFactory or DataSource {1} is invalid. It may be necessary to re-start the server for previous configuration changes to take effect. If the connection factory had been created by a JNDI lookup, previous configuration changes do not take effect until the next server restart. Check the accuracy of the component-managed authentication alias configured on the connection factory or data source. Re-start the server. XA_RESOURCE_ADAPTER_OPERATION_EXCP_J2CA0028=J2CA0028E: An exception occurred while invoking {0} on an XA Resource Adapter from DataSource {2} : {1}. There was a problem processing the given method. The processing within the method did not complete successfully. 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. FILE_UNAVAILABLE_FOR_UPDATE_J2CA0648=J2CA0648E: The RAR file {0} does not exist or cannot be read. The RAR file either does not exist or is not readable. Check the path to the RAR file and make sure that there are no other processes accessing it. RA_STOP_XARECOVERY_FAILED_J2CA0204=J2CA0204W: The attempt to stop ResourceAdapter failed during XARecovery cleanup and will be ignored. It was due to the following exception: {0} An exception occurred while attempting to stop a resource adapter. Take appropriate action based on the exception text. CREATE_RA_MISC_PROPERTIES_EXCP_J2CA0101=J2CA0101E: Unable to obtain RA miscellaneous configuration information for J2CConnectionFactory {0} : {1} The RA miscellaneous configuration object could not be read. See the FFDC logs for more information on the error. BUCKET_CF_SPECIFIC_J2CA0124=J2CA0124I: Pool properties for {1} were read from {0}. This is an informational message. There is no user action required. TRANSACTION_FAILED_J2CA0094=J2CA0094E: The transaction this operation is part of has failed. Cancelling the operation. Throwing exception {0} The transaction for this operation has failed, possibly due to a transaction timeout. See messages from the transaction service for more information. INCOMPATIBLE_PROPERTY_TYPE_J2CA0207=J2CA0207W: A resource adapter artifact has property {0} whose value {2} is incompatible with its type {1}. A connection factory, activation spec or admin object has a resource property which is not valid. The value will remain unset. Correct the resource property so the value is consistent with its data type. NO_CONNECTOR_NAME_EXCP_J2CA0011=J2CA0011E: There is no connector name in the Reference object for method {0}. There is a problem with the Reference object that was initially stored in the JNDI name space. 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/ . ERROR_CREATING_OBJECTNAMES_J2CA0110=J2CA0110W: A JMException was thrown when creating ObjectNames for {0} the exception is {1}. An internal error occurred. The ObjectNames that were used on the lookup were not created. 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/ . MBEAN_NOT_FOUND_J2CA0108=J2CA0108E: the parent MBean for {1} could not be found, the identifier used to find the MBean is {0}. An internal error has occurred. The parent MBean should be created when the connection factory or data source is bound into the namespace. Collect diagnostic data and visit the IBM support web site for more information. NONNODE_UPDATE_SUCCESSFUL_J2CA0654=J2CA0654I: The update of {0} to RAR file {1} was successful. The resource adapter configuration was updated, but not the binaries. The configuration was automatically saved. When updating a resource adapter at a scope other than node scope, only a configuration update is possible. To update the binaries, perform an update on the node scoped resource adapter that the specified resource adapter is a copy of, if it has not been updated already. XA_END_EXCP_J2CA0024=J2CA0024E: Method {0}, within transaction branch ID {1} of resource pool {4}, caught {2} and threw a {3}. 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. 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. XML_PARSING_ERROR_J2CA0125=J2CA0125W: Error parsing XML document {0}. The XML document is not formed correctly. See the XML document for possible errors. DIRECT_LOOKUP_OF_RESOURCE_J2CA0294=J2CA0294W: Direct JNDI lookup of resource {0}. The following default values are used: {1} Avoid using the fully qualified names of resources when looking up resources through Java Naming Directory Interface (JNDI). The Java EE programming model recommends the use of resource references and the local JNDI java:comp/env context. Modify the application to use the preferred Java EE programming model with resource references and the local JNDI java:comp/env context. XA_OPERATION_NOT_SUPPORTED_J2CA0023=J2CA0023E: A two phase XA operation, {0}, was invoked. This Resource Adapter from DataSource {1} does not support two phase processing. 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. Modify the business logic to separate the resource usage into separate transactions. FAILED_TO_OBTAIN_XAResource_J2CA0078=J2CA0078E: An exception was caught while trying to obtain a javax.transaction.xa.XAResource from a ManagedConnection on DataSource {1}. The exception is: {0} The connection manager was unable to obtain a XAResource from the resource adapter. This indicates a problem with the resource adapter. Look for error messages from the resource adapter to identify the problem. BAD_REFERENCE_PARAMETER_EXCP_J2CA0010=J2CA0010E: Parameter in method {0} is not of type Reference: {1}. The getObjectInstance method is invoked by the JNDI lookup processing of the resource. The implementation of the JNDI lookup should be passing in a valid Reference object for the desired resource. Either the name service is passing in a bad object or the Reference object was created incorrectly. 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/ . NO_ACCESS_TO_RA_COPY_J2CA0662=J2CA0662E: There are copies of resource adapter {0} that the command executor does not have configurator access to at the following scopes: {1}. Updating the resource adapter is not recommended. The command executor does not have configurator privilege for a copy of the resource adapter at the given scope. Copies of a Resource Adapter depend on the given Resource Adapter's binary files. They must all be updated, but they cannot be updated without the adequate privileges. Run the command with a user ID that has configurator access privileges to the resource adapter(s) at the scopes that are listed. DO_START_FAILED_J2CA0143=J2CA0143E: Embedded ResourceAdapter initialization failed due to Exception: {0} This exception is unexpected. The cause is not immediately known. 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/ . ALERT_CONN_LOW_EFF_J2CA0501=J2CA0501W: Connection Low Efficiency Alert for ConnectionFactory or DataSoure {0}. The usage efficiency for a connection is {1} which is below the configured alert threshold of {2} percent efficiency. If callstack capture is enabled, the callstack at the time the connection was requested will be provided in the alert contents. You have configured the monitoring of individual connections for low usage efficiency. For connections that are not shared, efficiency is measured from the time the connection is received to the time it is released. For connections that are sharable, efficiency is measured from the time it is received to the time that the sharing boundary ends, which is typically the end of a transaction or component method. The usage efficiency is the amount of time that the connection is used to interact with the backend, divided by the total amount of time the connection has been held. It is expressed as a percentage. If the efficiency is lower than expected, examine the application for possible causes. HA_ENABLED_MISMATCH_J2CA0304=J2CA0304W: Conflicting high availability support was found for resource adapter {0}. The resource adapter was configured to have high availability support enabled, but the resource adapter has a conflicting property value. The resource adapter cannot register with the high availability manager. The resource adapter is configured to be highly available, but the resource adapter implementation class indicates that the resource adapter does not support high availability. Ensure that high availability is enabled for this resource adapter. To enable high availability either select Register this resource adapter with the high availability manager on the Resource adapter page of the administrator console, or include the EnableHASupport attribute on the J2CResourceAdapter configuration object in the wsadmin tool. DUPLICATE_CONNECTOR_PROPERTY_J2CA0308=J2CA0308W: Duplicate connector property not added. {0}. An attempt was made to add a duplicate connector property. The property was not added. 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. EXTRA_APP_ACCESS_J2CA0283=J2CA0283E: Attempt to access embedded Resource Adapter of another application via ConnectionFactory {0}. An application attempted to lookup a connection factory that is associated with an embedded resource adapter for another application. The application should use a connection factory that is associated with its own resource adapter or use a connection factory that is associated with a stand-alone resource adapter. ACTIVATION_STATE_PARTIALLY_ACTIVE_J2CA0530=J2CA0530I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} is partially activated but has been disabled from handling incoming messages. The message endpoint exists, but has been disabled from handling incoming messages by setting the custom property WAS_EndpointInitialState to INACTIVE. Activate the endpoint by using the resume method on the J2CMessageEndpoint MBean. CROSS_COMPONENT_HANDLE_USE_J2CA0166=J2CA0166W: An attempt to concurrently use a connection handle within different application server components has been detected. The connection handle is: {0}. It is a programming model violation to use a connection handle in a component instance that is different from the component instance that first created the connection. Components consist of servlets, JSPs, EJBs, MDBs, and asynchronous Beans. Do not make the connection handle available to any component instance that did not implement the getConnection call. INTERUPTED_EXCEPTION_J2CA0091=J2CA0091E: An InterruptedException occurred on the Garbage Collector thread. An InterruptedException occurred on the thread for the garbage collector. J2C processing will continue, but unused and aged connections will not be collected. 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/ . MAX_NUM_RESERVE_POOLS_EXCEEDED_J2CA1009=J2CA1009E: The number of reserve pools defined by numberOfPoolReserves is {0}. The maximum number of reserve pools allowed is {1}. The supplied number of reserve pools to generate exceeds the maximum number allowed. Change the value of numberOfPoolReserves to be less than or equal to the maximum number of reserve pools allowed. DUPLICATE_USERNAME_PASSWORD_CONNECTOR_PROPERTY_J2CA0103=J2CA0103I: Duplicate connector property not added. {0} An attempt was made to add a duplicate connector property. The property was not added. 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. UNREG_AS_FAILED_J2CA0141=J2CA0141W: Failed to de-register the Activation Specification from the Transaction Service. Caught exception {0}. The transaction service was unable to unregister an activation specification at this time. This might be due to outstanding transactional work involving this activation specification. This might be a transient error. Restarting the server should clear up any outstanding transactions. If the error persists, visit the IBM support web site. CLASS_NOT_FOUND_INVALID_RAR_J2CA0656=J2CA0656E: A ClassNotFoundException was caught during command execution. {0} listed in the ra.xml was {1}, but that class could not be found in {2}. The ra.xml defined a class to be loaded as a Resource Adapter, Connection Factory, Activation Specification or Admin Object, but the class could not be loaded from the rar file. This likely means the RAR file is corrupt or not valid. Confirm that the RAR file is not corrupted, then contact your Resource Adapter vendor to make sure that the Resource Adapter provided is valid. UNABLE_TO_CHANGE_PROPERTY_J2CA0169=J2CA0169E: Unable to change the property {0} on DataSource or ConnectionFactory {1}. The connection manager was unable to make the requested change to the configuration variable at this time. Attempt to change the configuration variable again. DEACTIVATION_INFO_NOT_FOUND_J2CA0100=J2CA0100E: The information object needed to deactivate the endpoint was not found for deactivationKey {0}. Throwing exception {1} This exception is unexpected. The cause is not immediately known. 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/ . CONNECTIONFACTORY_IMPLEMENTATION_REMOVED_J2CA0640=J2CA0640I: The new RAR file is not compatible with the Resource Adapter. A ManagedConnectionFactory implementation class {2} was removed, and there is a configured connection factory that uses the removed type. ConnectionFactory name: {0}, JNDI Name: {1}. The new RAR file has removed a ManagedConnectionFactory implementation, and the Resource Adapter currently has at least one configured factory that makes use of the removed implementation. This makes the Resource Adapter and RAR incompatible for update. To update to the new version of the Resource Adapter, delete the connection factories that use the implementation class that was removed. The configuration for these factories will be lost. FAILED_CONNECTION_RELEASE_J2CA0022=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. 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. Examine the other related messages for explanations and user responses. MALFORMED_PROPERTY_NAME_J2CA0664=J2CA0664E: The property name argument passed to the managed bean getProperty operation is empty or malformed. A empty or malformed property name was used as the argument for the managed bean getProperty operation. Provide a non-empty, valid string as input for the managed bean getProperty operation. UNSUPPORTED_CONTEXTS_FOUND_J2CA0225=J2CA0225E: WorkContext {0} is not supported. The WorkContext is not supported by the application server. Do not use unsupported WorkContext when submitting a Work the implements WorkContextProvider. ATTEMPT_TO_VALIDATE_MC_CONNECTIONS_J2CA0285=J2CA0285W: Method {0} caught an exception during validating managed connections for resource {3}, throwing {2}. Original exception: {1} A call to the method getInvalidConnections() returned a resource exception. Visit the support web site for the provider of the resource adapter. ENLIST_OPTION_USED_J2CA0053=J2CA0053W: Enlist option used is {0}. This differs from the desired option of {1} for resource {2}. The resource adapter does not support the specified TransactionResourceRegistration setting. The J2C Runtime environment is using the default value. There is no user action required. CONN_FAILOVER_RESOURCE_AVAILABLE_J2CA0682=J2CA0682I: The configured resource with a JNDI name of {0} is available to process new requests for the resource with a JNDI name of {1}. The configured primary or alternate resource with the specified JNDI name is now available to process new requests. No action is required. CREATE_MBEAN_PROPS_EXC_J2CA0120=J2CA0120W: An exception occurred when trying to read J2C MBean properties from the referenceable object {0}. An internal error occurred, but it is not terminal. The connection factory or the data source will work correctly. An MBean might not be created for this object, and if one is it might contain bad data. PMI data might also not be able to link to the MBean. 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/ . ALERT_CLAIM_VICTIM_J2CA0507=J2CA0507W: Claim Victim Alert for ConnectionFactory or DataSource {0}. The percentage of victim connections claimed over approximately the last {1} minutes has exceeded your configured threshold of {2} percent. When a connection factory or data source has reached the maxConnection limit and a request comes in for a new connection, and it has connections available in its free pool that do not match the necessary criteria of the request, one of these connections will be destroyed, which is called the victim, so that a new connection can be created. This alert notifies you if the rate at which this is occurring exceeds the threshold that is configured. The excessive claiming of connections is detrimental to performance, and it might indicate a problem with how the application is using connections. In some usage scenarios this might be normal. MISSING_THREAD_POOL_J2CA0289=J2CA0289W: Thread pool {0} has not been defined in the server configuration or is not configured correctly. The thread pool that was specified for the resource adapter must first be created or configured correctly using system administration before it can be used by a resource adapter. Create the missing thread pool or fix the configuration for the thread pool. DEST_LOOKUP_FAILED_REQUIRED_J2CA0164=J2CA0164E: The lookup of the Destination with JNDI Name {0} failed. The Destination is required by the Activation Specification. The lookup failed due to exception {1}. The JNDI lookup of the destination failed. This could be caused by one of the following conditions: (1) the destination referred to by the specified JNDI name has not been configured, (2) the JNDI name is not correct, or (3) some other problem exists that is indicated by the exception. Check that the destination had been configured for the resource adapter that is in use. The destination can be configured as part of the activation specification configuration or during the MDB step during application deployment. Ensure that the JNDI name that is specified matches the name that is specified when creating the destination administered object on the resource adapter. REALM_IS_NOT_TRUSTED_J2CA0685=J2CA0685E: An authenticated JAAS Subject from an untrusted realm {0}, was passed to the application server by the resource adapter. The JAAS Subject that was passed in by the resource adapter does not belong to the application realm nor to a realm that is trusted by the application server. Add the realm to the list of realms trusted by the application server, or modify the resource adapter configuration or source code to pass in a subject that belongs to the application realm or a trusted realm. ILLEGAL_ARGUMENT_EXCEPTION_J2CA0080=J2CA0080E: Method {0} has detected an internal illegal argument and is throwing an IllegalArgumentException. The exception is: {1} The connection manager has detected an internal error. 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/ . NO_VALID_TRANSACTION_CONTEXT_J2CA0040=J2CA0040E: No valid transaction context was found on the thread for method {0} with coordinator {1} using resources from DataSource {2}. 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. 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/ . CREATE_CONNECTOR_POOL_PROPERTIES_EXCP_J2CA0005=J2CA0005E: An exception occurred while trying to read the Connection Pooling Properties for {0} from the namespace: {1}. There is a problem with the Systems Management configuration of the connection factory. The properties for connection pooling do exist for the connection factory, but they are not in the right format to read and process. 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/ . CWTE_NORMAL_J2CA1010=J2CA1010E: Connection not available; timed out waiting for {0} seconds. This occurrs when a connection can not be obtained to a data source. No user action required. ACTIVATION_STATE_STOPPED_J2CA0525=J2CA0525I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} is stopped and its MBean is unusable. Message endpoints stop, or expire, when their host applications or resource adapters stop. Once a message endpoint has stopped, getStatus() is the only method supported by its MBean; all other methods will throw an IllegalStateException. Restart the application hosting the message endpoint and obtain a new MBean reference in order to control the message endpoint. ERROR_SETTING_TRACEWRITER_J2CA0118=J2CA0118W: An exception occurred when setting the trace writer on the ManagedConectionFactory. The MCF used was {0}. The exception was {1}. The trace writer was not able to be set on the MCF. You will not see any specific trace entries for the resource adapter, but tracing for the application server will work if it is enabled. Check that there are no other exceptions in the FFDC logs. The other exceptions might indicate a problem with the ManagedConnectionFactory or in getting the correct PrintWriter. If there are no other exceptions, visit the support web site for the resource adapter. METHOD_EXCEPTION_J2CA0154=J2CA0154E: The method {0} on class {1} returned the following exception: {2} This exception is unexpected. The cause is not immediately known. 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/ . BEAN_VALIDATION_DESCRIPTOR_UNACCESSIBLE_J2CA1005=J2CA1005E: An exception occurred while trying to access the Bean Validation descriptor file {0} : {1}. The validation.xml file exists, but is unaccessible. The file may be unaccessaible due to insufficient read access priviledge on the file system, the file path is a directory, or the thread lacks permission to read the file. Check the FFDC logs. If the file lacks read access priviledge on the file system, add the priviledge to the file. CMSG0002 FILETRANSFERSERVER_NOT_AVAILABLE_J2CA650=J2CA0650E: The FileTransferServer mbean was unavailable, unable to proceed with update. The FileTransferServer mbean was not able to be found, so the RAR file could not be sent, and the update process cannot continue. Check the FFDC logs and System.err logs within the {PROFILE_HOME}/logs directory to see if there are any errors during server startup. MISSING_OR_UNRECOGNIZED_ROOT_ELEMENT_J2CA0116=J2CA0116W: The root element {1} of XML document {0} is not as expected. A properties file was not coded correctly. Check that the root element of the XML document is correct. TRANSACTION_REQUIRED_J2CA0076=J2CA0076E: An active transaction is required for the method {0}. Processing requires the presence of a transaction in order to run the current method. The most common cause of a missing transaction context is that the transaction timed out. 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/ . FAILED_TO_ENLIST_CONNECTION_J2CA0293=J2CA0293E: The Connection Manager lazyEnlist() method requires a non-null ManagedConnection parameter for resource {0}. 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. 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. UNABLE_TO_FIND_CLASS_J2CA0200=J2CA0200E: The Connection Manager was unable to find the class {0}. The connection manager was unable to find the given class. Check that the associated XA resource provider is configured, and restart the server. The resource can then be unconfigured, and the server can be stopped. ERROR_GETTING_PROPERTIES_PATH_J2CA0115=J2CA0115W: {0} occurred getting the absolute path to %WAS_HOME%\properties. An internal error has occurred. 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/ . INCOMPATIBLE_CLASS_FILE_IN_RA_J2CA0248=J2CA0248E: An exception occurred while loading resource adapter class {0}. The class might have been compiled with a newer version of Java than the application server is using. The exception was: {1} Resource adapter classes compiled with a newer version of Java than the server is running can have class incompatibility issues. Verify that the resource adapter is intended to run on the version of Java which the application server is using. MULTIPLE_CALLERPRINCIPALCALLBACKS_NOT_SUPPORTED_J2CA0676=J2CA0676E: The supplied security context provided multiple instances of a JASPIC CallerPrincipalCallback to establish the security context of the work instance. The WorkManager expects the security context to supply exactly zero or one instance of a JASPIC CallerPrincipalCallback while establishing the security context of the work instance. Contact the resource adapter vendor to determine why the resource adapter provides multiple instances of the CallerPrincipalCallback. VARIABLE_OUT_OF_RANGE_J2CA0170=J2CA0170E: Internal error. The variable {0} on DataSource or ConnectionFactory {1} has gone out of its acceptable range. This exception is unexpected. The cause is not immediately known. 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/ . AO_BIND_FAILED_J2CA0039=J2CA0039E: Failed to bind an Administered Object to the namespace with JNDI name {0}. The associated Resource Adapter key is {1}. This exception is unexpected. The cause is not immediately known. 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/ . FAILED_TO_OBTAIN_LOCALTRAN_J2CA0077=J2CA0077E: An exception was caught while trying to obtain a javax.resource.cci.LocalTransaction from a ManagedConnection for resource {1}. The exception is: {0} The connection manager was unable to obtain a LocalTransaction from the resource adapter. This indicates a problem with the resource adapter. Look for error messages from the resource adapter to identify the problem. FAILED_TO_FIND_RA_J2CA0202=J2CA0202E: Internal Error: Failed to find the RAWrapperImpl instance associated with the following key {0}. Throwing exception {1} This exception is unexpected. The cause is not immediately known. 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/ . RA_OP_FAILED_J2CA0150=J2CA0150E: The ResourceAdapter {0} failed to {1} because the ResourceAdapter was not found. The given resource adapter could not be found to perform the operation. This might be because it was not started or has already been shut down. Check that the MBean that you are using is valid. FAILED_DOPRIVILEGED_J2CA0060=J2CA0060E: PrivilegedActionException calling doPrivileged: {0} This is a security runtime error. 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/ . INTERNAL_TARGET_ADAPTER_J2CA0652=J2CA0652E: WebSphere internal adapters are not updateable. The WebSphere internal resource adapters are not updateable through the RAR Update framework. None ZOS_ONLY_CUSTOM_PROP_J2CA0694=J2CA0694W: The {0} custom property defined for the resource with JNDI name of {1} can be defined for the application server only on the z/OS system. This custom property is ignored. The custom property is specific to the application server on a z/OS system. Because the system on which the application server is running is not a z/OS system, the custom property being defined is ignored. Verify that the custom property being defined has no restrictions. COMPARE_MULTIPLE_RA_NO_ACCESS_J2CA0661=J2CA0661E: Monitor privilege is required for all Resource Adapters being compared. Monitor privilege was not found for the {0} Resource Adapter. The command executor could not perform a comparison. The command executor does not have the monitor privilege for the specified Resource Adapter configuration ID. Obtain monitor access privileges from the system administrator for the Resource Adapter that was specified and any related resources. RA_START_FAILED_J2CA0128=J2CA0128E: An Exception occurred while trying to start ResourceAdapter {0}. The exception is: {1} An exception occurred trying to start a resource adapter. This occurred during the reading of the configuration properties or during the call to start the class for this resource adapter. Check the exception and other error messages for more details. Take action based on the exception or the other errors in the log. BUCKET_SERVER_WIDE_J2CA0123=J2CA0123I: Server-wide pool properties were read from {0}. This is an informational message. There is no user action required. INVALID_GROUP_ENCOUNTERED_J2CA0678=J2CA0678W: Group {0} does not belong to the domain associated to the application. 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. 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. RA_METHOD_FAILED_J2CA0089=J2CA0089E: The method {0} on ResourceAdapter JavaBean {1} failed with the following exception: {2} The resource adapter created an exception. This could indicate a problem with the resource adapter. Check the exception for more information. INVALID_EJB_COMPONENT_J2CA0099=J2CA0099E: Invalid EJB component: Cannot use an EJB module with version {0} and CMP version {1} using {2}. An attempt to run an EJB component that is incompatible with the application server was detected. Evaluate the EJB version and CMP version that is supported by the EJB component. Correct any potential problems and redeploy the components. ALERT_POOL_LOW_EFF_J2CA0502=J2CA0502W: Pool Low Efficiency Alert for ConnectionFactory or DataSoure {0}. The average efficiency of all the connections is {1} which has dropped below the configured alert threshold of {2} percent efficiency during the past approximate {3} minutes. You have configured the monitoring of your data source or connection factory for low average connection usage efficiency. The usage efficiency is the total amount of time the connections are used to interact with the the backend data source, divided by the total amount of time the connections have been held, and averaged for the number of connections at any point in time in the pool. It is expressed as a percentage. If the efficiency is lower than expected, examine the application for possible causes. You might want to configure the Connection Low Efficiency Alert with a callstack capture enabled to further isolate the specific application usage which is not efficient. NULL_PROVIDER_OBJECTNAME_J2CA0113=J2CA0113W: The ObjectName for the provider MBean was null. This will cause an error with PMI and will prevent the Connection Factory or Data Source MBean from being linked to its J2CResourceadapter or JDBCProvider (respectively) "parent" MBean. An internal error occurred. The MBeans will not be linked correctly. This does not effect the use of the connection factory or the data source, but it might cause an error if you are using PMI. 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/ . ALERT_CONN_WAIT_TO_J2CA0506=J2CA0506W: Connection Wait Time-out Alert for ConnectionFactory or DataSource {0}. The number of ConnectionWaitTimeoutExceptions issued has exceeded your configured threshold of {1} in less then the configured alert time of {2} minutes . Connection factories or data sources can be configured to wait a certain amount of time for a connection to become amenable. If this time is exceeded, a ConnectionWaitTimeoutException is issued. This alert can be configured to count the number of ConnectionWaitTimeoutExceptions over a given interval and raise an alert if the threshold is exceeded. Refer to the documentation for on ConnectionWaitTimeoutExceptions for more details. CONN_FAILOVER_PRIMARY_AND_ALTERNATE_UNAVAILABLE_J2CA0681=J2CA0681I: The configured primary resource with a JNDI name of {0} and the configured alternate resource that has a JNDI name of {1} are unavailable. Connection management has detected that both the configured primary and alternate resources have become unavailable. Requests cannot be rerouted. Contact your database or system administrator to determine the state of the resources in question. CREATE_RESOURCE_ADAPTER_DD_EXCP_J2CA0001=J2CA0001E: An exception occurred while trying to read the Resource Adapter Deployment Descriptor for {0} : {1}. This indicates a problem with the Systems Management configuration of the resource adapter. A Deployment Descriptor does exist for this resource adapter, but it is not in the right format to read in and process. 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/ . AUTH_MECH_PREFERENCE_NOT_SUPPORTED_J2CA0104=J2CA0104E: Authentication mechanism preference {0} is not supported by the Resource Adapter for ConnectionFactory or DataSource {1}. The authentication mechanism must be one of those specified in the element [authentication-mechanism-type] in the resource adapter's ra.xml file. Use the administrative console to specify an authentication mechanism that is supported by the resource adapter. REGISTER_WITH_SYNCHRONIZATION_EXCP_J2CA0026=J2CA0026E: Method {0} caught {1} while trying to register the Resource Adapter with the Synchronization Manager for the current transaction, and threw a {2}. 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. 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. PARK_OR_REASSOCIATE_FAILED_W_J2CA0083=J2CA0083W: Method {0} failed while trying to execute method {1} on the ConnectionManager. Failing handle is: {2}. Caught the following Exception: {3} The ConnectionHandleManager caught an exception while trying to perform a handle re-association operation. This is expected behavior following a transaction time-out, but in other cases this could be an internal error. Look for messages indicating that a transaction has timed out. If time-outs are occurring you can ignore this message. If you do not see evidence of a transaction time-out, contact support. NULL_MANAGED_CONNECTION_J2CA0015=J2CA0015E: The Connection Pool Manager could not allocate a Managed Connection from resource {0}. 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. 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/ . INCOMPATIBLE_JCA_VERSIONS_J2CA0660=J2CA0660I: The new RAR file is not compatible with the Resource Adapter. The JCA Spec versions of the Resource Adapter and RAR are different. Resource Adapter JCA version: {0}. RAR File JCA Version: {1}. Updating to a RAR file that is of a different JCA spec version than the Resource Adapter is not supported. Choose a resource adapter and RAR file which are compatible for update. CONN_FAILOVER_INVALID_ALTERNATE_SETUP_J2CA0689=J2CA0689W: An alternate resource with a JNDI name of {1} has an alternate resource with a JNDI name of {2}. Resource failover for the alternate resource with a JNDI name of {3} is disabled. Recursive failover to multiple resources is not supported. Failover support for alternate resources that themselves have alternate resources is disabled. Read the documentation available on resource routing for correctly enabling failover support. CUSTOM_CREDENTIALS_MISSING_J2CA0668=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. 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. 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. DUPLICATE_WORK_CONTEXT_J2CA0691=J2CA0691E: The {0} operation failed because the resource adapter {1} requires a Work Context type {2} that is declared more than once in the RAR metadata. The Application Server supports unique Work Context types. The RAR failed to deploy because two or more RequiredWorkContext elements, declared in either the RAR deployment descriptor or an @Connector RAR metadata annotation, specify the same Work Context type. Contact the resource adapter vendor and obtain a new RAR module containing metadata that declares only unique required Work Context types supported by the Application Server. CREATE_SERIALIZABLE_EXCP_J2CA0017=J2CA0017I: An exception occurred while building the serializable for JNDI deployment of {0} : {1}. This error was absorbed and a null returned from the method. There was a problem creating the serializable object to be stored in the JNDI name space for the named resource. This problem will be detected and logged as an error later in the processing. Refer to the additional information that is provided to find related error messages and information from the log file. UNSUPPORTED_WORK_CONTEXT_J2CA0686=J2CA0686E: The {0} operation failed because the resource adapter {1} requires a Work Context type {2} that is not supported by the Application Server. The Application Server supports the following three Work Context types: javax.resource.spi.work.TransactionContext, javax.resource.spi.work.SecurityContext, and javax.resource.spi.work.HintsContext. The RAR failed to deploy because a RequiredWorkContext element, declared in either the RAR deployment descriptor or an @Connector RAR meta-data annotation, specifies a Work Context type that is not supported by the Application Server. Contact the resource adapter vendor and obtain a new RAR module that declares only required Work Context types supported by the Application Server. NODE_UPDATE_SUCCESSFUL_J2CA0653=J2CA0653I: The update of {0} to RAR file {1} was successful, a full binary and configuration update was performed. The configuration has been saved. When updating a node scoped resource adapter, an update is performed on the configuration and the binary files. A configuration save is automatically done. Update any copies of this resource adapter if they have not been updated already. UNRECOGNIZED_VALUE_J2CA0243=J2CA0243E: WebSphere Application Server does not recognize a value of {0} for property {1} which is configured on resource {2}. The value of the property is not understood by WebSphere Application Server. Correct the configuration error. NO_GROUPS_FOR_UNIQUEID_J2CA0679=J2CA0679W: No groups were found for the user with the uniqueId {0} 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. There is no user action required. CREATE_MANAGED_CONNECTION_FACTORY_EXCP_J2CA0013=J2CA0013I: An exception occurred while trying to create ManagedConnectionFactory for {0} : {1}. A problem occured creating the ManagedConnectionFactory from the stored Reference in the JNDI name space. Refer to the additional information that is provided to find related error messages and information from the activity.log file. UNABLE_TO_INITIALIZE_XATERM_J2CA0136=J2CA0136E: Unable to create an XATerminator, due to an exception. The exception will not be re-thrown. The exception is: {0}. The BootstrapContext was unable to return an XATerminator to the resource adapter. See the exception and previous log entries for more details. ERROR_DESTROY_MC_J2CA0063=J2CA0063W: Encountered an error while destroying the ManagedConnection {0} : {1} The destroy operation on a managed connection failed after recovery. 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/ . CONNECTION_DETAILS_J2CA0070=J2CA0070W: Component {0}, is holding {1} number of connection(s). A number of connections are being held by a component. This message typically follows the exception for an unavailable resource unavailable when a getConnection request failed in the application code. Check if one or more components are holding connections excessively. The application might not be closing connection. If a number of connections appear to be working, increase the "max pool size." BEAN_VALIDATION_FACTORY_BUILD_FAILED_J2CA1006=J2CA1006E: An exception occurred while attempting to build the ValidatorFactory for a resource adapter having archive path {0} : {1}. Bean Validation has been disabled for resource adapters having the archive path. This exception is unexpected and indicates a problem with the BeanValidationService, the Bean Validation provider, or the RAR deployment. The cause may not be immediately determined. Check the FFDC logs. If the problem appears due to the RAR configuration, reassmeble the RAR per the WebSphere Application Server InfoCenter and redeploy it. If the problem is due to a failure in a Bean Validation implementation other than that supplied by WebSphere Application Server, contact the Bean Validation provider. CMSG0002 ADMINOBJECT_IMPLEMENTATION_REMOVED_J2CA0641=J2CA0641I: The new RAR file is not compatible with the Resource Adapter. An AdminObject class {2} was removed, and there is a configured Admin Object that uses the removed type. AdminObject name: {0}, JNDI Name: {1}. The new RAR file has removed an Administrative Object implementation, and the Resource Adapter currently has at least one configured AdminObject that makes use of the removed implementation. This makes the Resource Adapter and RAR incompatible for update. Delete the Administrative Objects that use the implementation class that was removed. The configuration for these objects will be lost. NO_MAPPING_CONFIG_ALIAS_J2CA0144=J2CA0144W: No mappingConfigAlias found for ConnectionFactory or DataSource {0}. The component is using container-managed authentication, but no mappingConfigAlias was specified. DefaultPrincipalMapping will be used. This is likely a scripting error with the specified ConnectionFactory or DataSource, or its corresponding CMPConnectorFactory. INCOMPATIBLE_PROP_VALUE_J2CA0663=J2CA0663W: User input value {0} on the new RAR file property {1} is not compatible with the expected type {2}. The default value {3} specified in ra.xml will be used instead. Runtime errors may result from properties whose values are incompatible with their defined type. If the default value is not desired, edit the connection factory, activation spec or admin object on which the property is found. INVALID_SERVLET_LEVEL_J2CA0106=J2CA0106E: A 5.0 Data Source was attempted to be used in a WebModule that was not level 2.3. 5.0 Data sources are only supported for WebModules with servlet level 2.3. Evaluate whether the servlet in question can be migrated to level 2.3. If so, migrate the application and redeploy it. If it cannot be migrated, the servlet must use a Websphere Application Server 4.0 data source. AUTH_MECH_PREFERENCE_NOT_SPECIFIED_J2CA0105=J2CA0105W: Authentication mechanism preference not specified for ConnectionFactory or DataSource {0}. This might be a symptom of a hand-modified resources.xml document. A subject might contain null credentials, or the resource adapter mightnot accept this subject. Use the administrative console to specify an authentication mechanism that is supported by the resource adapter. If the resource adapter does not support any authentication mechanism, choose "None." INVALID_USER_NAME_IN_PRINCIPAL_J2CA0670=J2CA0670E: The WorkManager was unable to establish the security context for the work instance, because the resource adapter provided a caller identity {0}, that does not belong to the security domain associated with the application. The security context provided by the work instance contains a user name that does not exist in the realm (user registry) of the security domain associated to the application. The WorkManager obtained the invalid user name from an instance of a JASPIC CallerPrincipalCallback, whenever an instance is supplied by the resource adapter, or from the execution subject returned by method setupSecurityContext. In case the user is from the same realm, check if the user exists in the user registry for that realm. In case the user is from a different realm, contact the resource adapter vendor since the WorkManager does not currently support users from different realms. METHOD_FAILED_J2CA0132=J2CA0132E: Method {0} caught exception {1}. The method caught an exception that is most likely an internal error. 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/ . BEAN_VALIDATION_VALIDATOR_FAILED_J2CA1008=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. This exception is unexpected and indicates a problem with the Validator implementation. The cause may not be immediately determined. 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 CONNECTION_FACTORY_IMPLEMENTATION_CHANGED_1.0_J2CA0658=J2CA0658I: The new RAR file is not compatible with the JCA 1.0 Resource Adapter. The ManagedConnectionFactory implementation class has changed. The new RAR file has a different ManagedConnectionFactory implementation class. This makes the JCA 1.0 Resource Adapter and RAR incompatible for update. Choose a resource adapter and RAR file which are compatible for update. ALERT_PRETEST_BLOCK_J2CA0515=J2CA0515W: Pretest Block Mode Alert for ConnectionFactory or DataSource {0}. Connection Pretest function has stopped connection request blocking. Data sources and connection factories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on the configuration thresholds. If a connection is not responding the connection manager will block all requests for new connections until it can receive a functioning connection. If the pretesting of connections has been configured and this alert is enabled, this message indicates that you have exited the pretest connection blocking state, and the creation of new connections is now allowed. If your connection factory or data source is spending excessive time in a blocked state, you might want to look for underlying problems with the backend with which you are trying to communicate. BEAN_VALIDATION_FAILED_J2CA0238=J2CA0238E: JavaBean {0} failed Bean Validation due to one or more invalid configuration settings indicated in the following list of constraint violations: {1} The value of one or more configuration properties of the JavaBean instance violates the specified Bean Validation constraints. 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. HA_CAPABILITY_MISMATCH_J2CA0310=J2CA0310W: Resource adapter {0} is configured with high availability setting {1}, but the resource adapter method returnHACapability() returned high availability capability {2}. The high availability capability returned by the Resource adapter method will be used. The resource adapter is configured with a high availability setting that differs from the high availability capability that is supported by the resource adapter. The connection manager will use the high availability capability that is supported by the resource adapter. Use the administrative console or the wsadmin tool to configure the resource adapter with a high availability capability that is supported by the resource adapter. INACTIVE_SUPPORT_USED_J2CA0082=J2CA0082W: InactiveConnectionSupport option {0} used by resource {2}. This differs from the desired option of {1}. The resource adapter does not support the specified InactiveConnectionSupport setting. Visit the support site the developer of the resource adapter. DEST_LOOKUP_FAILED_J2CA0146=J2CA0146W: The lookup of the Destination with JNDI Name {0} failed due to exception {1}. The JNDI lookup of the destination failed. This could be caused by one of the following conditions: (1) the destination referred to by the specified JNDI name has not been configured, (2) the JNDI Name is incorrect, or (3) some other problem exists as indicated by the exception. Check that the destination is configured for the resource adapter that you are using. The destination can be configured as part of the activation specification configuration or during the MDB step during deployment of the application. Ensure that the specified JNDI Name matches the name specified when you create the Destination AdminObject on the resource adapter. ALERT_PRETEST_BLOCK_J2CA0505=J2CA0505W: Pretest Block Mode Alert for ConnectionFactory or DataSource {0}. Connection Pretest function has started connection request blocking. Data sources and connection factories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on the configuration thresholds. If a connection is not responding, the connection manager will block all requests for new connections until it can receive a functioning connection. If the pretesting of connections has been configured and this alert is enabled, this message indicates that you have entered the pretest connection blocking state, and the creation of new connections is not allowed. If your connection factory or data source is spending excessive time in a blocked state, you might want to see if there is an underlying problem with the backend with which you are trying to communicate. DUPLICATE_CONTEXTS_FOUND_J2CA0224=J2CA0224E: Multiple instances of the same WorkContext {0} provided. Resource adapter provided multiple WorkContexts that implement the same WorkContext type. Eliminate duplicates from a list of WorkContexts returned by a Work that implements WorkContextProvider before submitting the Work. CANNOT_LOAD_TM_J2CA0227=J2CA0227E: An error occurred when loading a Transaction Manager from class {0} The Transaction Manager cannot be loaded from the class specified in com.ibm.ws390.jta.TransactionManager system property. This will cause a subsequent failure when creating an instance of the Transaction Manager. 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/ . TRAN_RECOVERY_REG_FAILED_J2CA0084=J2CA0084W: Transaction recovery registration failed for ResourceAdapter {0} with exception {1}. Registration with the transaction service for the recovery of transactions for inbound messages to this resource adapter did not complete successfully. Subsequent transactions with the use inbound transactions might also fail. 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/ . MULTIPLE_RA_INSTANCE_VIOLATION_J2CA0205=J2CA0205E: The Connection Manager has detected a request to create ResourceAdapter {0}, when a pre-existing ResourceAdapter {1} that uses the same class names has been configured to run as a single instance. A resource adapter can be configured to tolerate only one instance of their resource adapter class being instantiated within a JVM. You will receive this message if you have more than one such resource adapter instance configured to run on a given server. This can happen in one of the following circumstances: 1) You deployed more than one Application which embeds the same resource adapter; 2) you have one stand-alone resource adapter deployed in a server and an application embeds the same resource adapter on the same server, or 3) you installed more than one instance of the same resource adapter as stand-alone (shared by all applications). Change your configuration such that the two resource adapters are not deployed to the same server. ACTIVATION_FAILED_J2CA0520=J2CA0520W: The Message Endpoint resume operation failed for ActivationSpec {0} and MDB Application {1} because the endpoint is currently activated or stopped, or an unexpected exception occurred activating the endpoint. Message endpoints that are activated or stopped cannot be resumed. Check that the message endpoint is deactivated before invoking the resume operation. If the endpoint is deactivated, see the exception and other log entries for more details. CREATE_MAPPINGMODULE_PROPERTIES_EXCP_J2CA0095=J2CA0095E: Unable to obtain authentication information for J2CConnectionFactory {0} : {1} The MappingModule object could not be read. See the FFDC logs for more information. CONN_FAILOVER_PRIMARY_UNAVAILABLE_J2CA0680=J2CA0680I: The configured primary resource with a JNDI name of {0} is unavailable. New requests will be routed to the configured alternate resource that has a JNDI name of {1}. Connection Management has detected that the configured primary resource is unavailable. New requests will be routed to the configured alternate resource. Contact your database or system administrator to determine the state of the resource in question. ILLEGAL_STATE_EXCEPTION_J2CA0079=J2CA0079E: Method {0} has detected an internal illegal state and is throwing an IllegalStateException. The exception is: {1} The connection manager has detected an internal error. 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/ .