WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


J2CA

J2CA0001E: An exception occurred while trying to read the Resource Adapter Deployment Descriptor for {0} : {1}.
Explanation This message 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.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0002W: There is no Resource Adapter Deployment Descriptor available for {0}.
Explanation This message indicates a problem with the Systems Management configuration for the Resource Adapter. A Deployment Descriptor does not exist for this Resource Adapter.
Action Check that resources.xml exists and contains a <resourceProviders xmi:type="resources.j2c:J2CResourceAdapter" . . .> element. If not, or if it looks incorrect, delete and re-create the resource adapter via the Admin Console.
J2CA0003E: An exception occurred while trying to read the Connection Factory Properties for {0} : {1}.
Explanation This message indicates 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 in and process.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0004W: There are no Connection Factory Properties available for {0}.
Explanation This message indicates a problem with the Systems Management configuration of the Connection Factory. The Properties do not exist for this Connection Factory.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0005E: An exception occurred while trying to read the Connection Pooling Properties for {0} from the namespace: {1}.
Explanation This message indicates a problem with the Systems Management configuration of the Connection Factory. The Connection Pooling Properties do exist for the Connection Factory, but they are not in the right format to read in and process.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0006W: There are no Connection Pooling Properties available for {0}.
Explanation This message indicates a problem with the Systems Management configuration of the Connection Factory. The Connection Pooling Properties do not exist for this Connection Factory.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0007W: An exception occurred while invoking method set{0} on {1} used by resource {3} : {2}. Processing continued.
Explanation This message indicates a problem with invoking a method on a deployed object. The names of these methods are determined by the name/value pairs contained in the JavaBean's Properties. These in turn are based on the contents of the Resource Adapter's ra.xml file. Processing will continue since the default values for this particular property may be sufficient to continue execution. Or, this particular property may not even be required by the specified deployed object.
Action This may indicate a mismatch between the Resource Adapter's XML definition and the actual Java class provided for the JavaBean's implementation. Examine the attributes supplied by the resource adapter. It may be necessary to provide this failure notification to the resource adapter provider.
J2CA0008W: Class {0} used by resource {2} did not contain method set{1}. Processing continued.
Explanation This message indicates a missing method on a deployed object. The names of these methods are determined by the name/value pairs contained in the JavaBean's Properties. These in turn are based on the contents of the Resource Adapter's ra.xml file. Processing will continue since the default values for this particular property may be sufficient to continue execution. Or, this particular property may not even be required by the specified deployed object.
Action This may indicate a mismatch between the Resource Adapter's XML definition and the actual Java class provided for the JavaBean's implementation. Examine the attributes supplied by the resource adapter. It may be necessary to provide this failure notification to the resource adapter provider.
J2CA0009E: An exception occurred while trying to instantiate the ManagedConnectionFactory class {0} used by resource {2} : {1}.
Explanation This message indicates a problem while attempting to create a ManagedConnectionFactory object. There are several possible reasons for this problem. The runtime (1) couldn't find the appropriate class for the ManagedConnectionFactory via the current class loader, (2) couldn''t create a TraceWriter object for the ManagedConnectionFactory, (3) or couldn''t create the ConnectionManager object for the ManagedConnectionFactory. Any of these could also be related to an invalid XML definition for the Resource Adapter.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0010E: Parameter in method {0} is not of type Reference : {1}.
Explanation The getObjectInstance method is invoked by the JNDI lookup processing of the Resource. The JNDI lookup implementation 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 in the first place.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0011E: There is no connector name in the Reference object for method {0}.
Explanation This message indicates a problem with the Reference object that was initially stored in the JNDI name space.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0012E: The connector name is null in the Reference object for method {0}.
Explanation This message indicates a problem with the Reference object that was initially stored in the JNDI name space.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0013I: An exception occurred while trying to create ManagedConnectionFactory for {0} : {1}.
Explanation This exception indicates a problem with creating the ManagedConnectionFactory from the stored Reference in the JNDI name space.
Action This informational message provides additional information for related error messages in the activity.log. Reference those error messages for additional explanations and user responses.
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.
Explanation This exception indicates a problem with 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.
Action This informational message provides additional information for related error messages in the activity.log. Reference those error messages for additional explanations and user responses.
J2CA0015E: The Connection Pool Manager could not allocate a Managed Connection from resource {0}.
Explanation The Pool Manager could not allocate a Managed Connection. This may be due to properties associated with the Pool Manager (ie. maximum connections exceeded). A NULL managed connection was returned by the Pool Manager.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0016E: A two phase XA operation, {0}, was invoked within transaction ID {1}. This resource adapter from pool {2} does not support two phase processing.
Explanation This message indicates that an attempt was made to use the connection within the context of an XA transaction along with other XA capable resources. This is not a valid operation for this resource adapter.
Action Modify the logic to separate the resource usage into separate transactions.
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.
Explanation This exception indicates a problem with 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.
Action This informational message provides additional information for related error messages in the activity.log. Reference those error messages for additional explanations and user responses.
J2CA0018E: An exception occurred while trying to create Resource Adapter Connection Factory {0} : {1}.
Explanation This message indicates a problem with the Resource Adapter creating the desired Connection Factory. The exception text should provide additional details on the actual problem.
Action If the exception text does not indicate a situation that is user controlled, then contact WebSphere support and provide the data from running collector.bat.
J2CA0019W: No Managed Connection Factory Properties data could be assembled for {0}. Processing continued.
Explanation This message indicates that due to other logged problems, the properties for the Managed Connection Factory could not be assembled. This may or may not cause runtime problems -- it will depend on the default values of the various properties as provided by the Resource Adapter.
Action Check for other related messages that will further explain the specific problems with the property data. If your connections seem to work okay, you could ignore this message. Otherwise, attempt to follow the User Response sections as documented by the other messages.
J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection: {0}.
Explanation This message indicates that an exception was thrown by the Pool Manager when attempting to allocate a Managed Connection. The exception text should help with deciphering the problem encountered.
Action If there are no user controlled indications, the message may be due to an error in the internal J2C runtime processing. Contact WebSphere support and provide the data from running collector.bat.
J2CA0021E: An exception occurred while trying to get a Connection from the Managed Connection resource {1} : {0}.
Explanation This message indicates that an exception was thrown by the Resource Adapter when attempting to call getConnection. The exception text should help with deciphering the problem encountered.
Action If there are no user controlled indications, the message may be due to an error in the internal J2C runtime processing. Contact WebSphere support and provide the data from running collector.bat.
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 rethrown.
Explanation This message indicates that a problem was encountered while attempting to clean up after a failed getConnection. This message is informational and should be combined with other related messages for proper problem determination.
Action Examine other related messages for Explanation and User Responses.
J2CA0023E: A two phase XA operation, {0}, was invoked. This resource adapter from datasource {1} does not support two phase processing.
Explanation This message indicates an attempt to invoke an XA operation on a resource adapter that only supports local transactions. This may indicate that a local transaction resource adapter was accidentally included within the context of an XA transaction along with other XA capable resources.
Action Modify the business logic to separate the resource usage into separate transactions.
J2CA0024E: Method {0}, within transaction branch ID {1} of resource pool {4}, caught {2} and threw a {3}.
Explanation This message indicates a problem while processing the given method. Since the interface defines specific exceptions that can be thrown, the caught exception had to be mapped to the thrown exception. The processing within the method did not complete successfully.
Action Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception.
J2CA0026E: Method {0} caught {1} while trying to register the Resource Adapter with the Synchronization Manager for the current transaction, and threw a {2}.
Explanation This message indicates a problem while processing the given method. Since the interface defines specific exceptions that can be thrown, the caught exception had to be mapped to the thrown exception. The processing within the method did not complete successfully.
Action Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception.
J2CA0027E: An exception occurred while invoking {0} on an XA Resource Adapter from dataSource {3}, within transaction ID {1}: {2}.
Explanation This message indicates a problem while processing the given method. The processing within the method did not complete successfully.
Action Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception.
J2CA0028E: An exception occurred while invoking {0} on an XA Resource Adapter from datasource {2}: {1}.
Explanation This message indicates a problem while processing the given method. The processing within the method did not complete successfully.
Action Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception.
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}
Explanation This may be a symptom of an incorrectly hand-modified resources.xml document. Alternatively,if you are using an application with an embedded ResourceAdapter, this may be a symptom of an incorrectly hand-modified deployment.xml document.
Action If you have hand-modified either a resources.xml or a deployment.xml file, please correct any errors there. If you have not edited these files, this may be and internal application server error.
J2CA0030E: Method {0} caught {1} while trying to enlist resources from datasource {3} with the Transaction Manager for the current transaction, and threw a {2}.
Explanation This message indicates a problem while processing the given method. Since the interface defines specific exceptions that can be thrown, the caught exception had to be mapped to the thrown exception. The processing within the method did not complete successfully.
Action Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors that caused the exception.
J2CA0031I: Method {0} caught {1} while trying to delist resources from dataSource {3} from the Transaction Manager for the current transaction and threw {2}
Explanation This message indicates a problem while attempting to delist resources from the transaction manager. This message is for informational purposes, unless it occurs on a regular basis.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0034E: An unexpected event was received from the resource adapter for resource {2}. Expected ConnectionEvent type {0} and received ConnectionEvent type {1}.
Explanation This is most likely an error with the specific resource adapter.
Action Contact support for the resource adapter.
J2CA0035E: Class {0}, used by resource {2} did not contain method set{1}. Processing halted.
Explanation The set method does not exist for this class, the J2C runtime expected this method to exist. The resource adapter requires this set method to be executed to function properly, so the ManagedConnectionFactory is discarded. The class file for this ManagedConnectionFactory may be out of date, or there may be a miscommunication between Websphere Systems Management and the J2C runtime.
Action Ensure that the class files for this resource adapter are up to date.
J2CA0036E: An exception occurred while invoking method set{0} on {1} used by resource {3} : {2}. Processing halted.
Explanation The set method could not be executed. 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.
Action Ensure that the class files for this resource adapter are up to date.
J2CA0037E: An exception occurred when trying to read the DataSource Properties for {0} from the namespace : {1}.
Explanation An internal error has occurred when reading properties from the namespace.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0038E: An exception occurred when trying to read the ManagedConnectionFactory Properties for {0} from the namespace : {1}.
Explanation An internal error has occurred when reading properties from the namespace.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0039E: Failed to bind an Administered Object to the namespace with JNDI name {0}. The associated Resource Adapter key is {1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0040E: No valid transaction context was found on the thread for method {0} with coordinator {1} using resources from dataSource {2}.
Explanation Internal error in the J2C runtime. A valid transaction context was required for the given operation but was not found.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0041E: The ComponentMetaData instance was null in method {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0042E: An Exception occurred while trying to expand part of a path. The failing piece is {0}. The exception is: {1}
Explanation Check the failing path string and verify that any unexpanded variables are valid (including their case).
Action Fix any invalid variables.
J2CA0043E: An Exception occurred while trying to instantiate a ResourceAdapter java bean instance for the installed ResourceAdapter defined by key {0}. The exception is: {1}
Explanation This indicates either that the path for the ResourceAdapter has been configured incorrectly or that the resources.xml file (or deployment.xml file if you are using an embedded RAR file) has been corrupted.
Action Correct the ResourceAdapter path configuration or corrupt xml configuration file.
J2CA0044E: The ConnectionManager failed to get a Subject from the security service associated with connection factory {0}. Received exception {1}.
Explanation An internal error occurred when getting a Subject. A container-managed authentication alias may not have been selected on the connection factory or datasource.
Action Check that a valid container-managed authentication alias is specified on the connection factory or datasource.
J2CA0045E: Connection not available while invoking method {0} for resource {1}.
Explanation A connection wait timeout has occurred. A ConnectionWaitTimeoutException was thrown.
Action Reconfigure the connection pool. You may increase the maximum number of connections, or increase connection wait time to avoid this condition.
J2CA0046E: Method {0} caught an exception during creation of the ManagedConnection for resource {3}, throwing {2}. Original exception: {1}
Explanation An error occurred during creation of a ManagedConnection. Usually this can be resolved by looking at the error messages from the resource adapter.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0047E: Property {0} for ResourceAdapter {1} has an invalid type of {2}.
Explanation ResourceAdapter properties are only allowed to be of 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.
Action Fix the Resource Adapter code such that it is compliant.
J2CA0048E: The setup of XA Transaction recovery for inbound message support did not complete for ResourceAdapter {0}. The following exception was caught: {1}
Explanation The server was unable enable transaction recovery for this ResourceAdapter. Possible causes include: errors in the archive, class, or native paths; internal server errors.
Action Validate your archive, class, and native paths.
J2CA0049W: ResourceAdapter {0} is being stopped with MessageEndpoints still activated. These MessageEndpoints will be forcefully deactivated.
Explanation ResourceAdapters should be stopped only after all MessageEndpoints have been deactivated. MessageEndpoints get deactivated when the application which is supplying the MessageEndpoint is stopped. Currently, only MDB's can be a MessageEndpoint.
Action Make sure you stop your applications which contain endpoints which are associated with a particular ResourceAdapter before you stop that ResourceAdapter.
J2CA0050W: Setting of the Connector property {0} on class {1} for resource {2} will be skipped. Property has a null value.
Explanation 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.
Action None.
J2CA0051E: The attempt to stop ResourceAdapter {0} failed due to the following exception: {1}
Explanation An exception occurred while attempting to stop a ResourceAdapter.
Action Take appropriate action based on the exception text.
J2CA0052E: The lookup of the ActivationSpec with JNDI Name {0} failed due to exception {1}.
Explanation The JNDI lookup of the ActivationSpec failed. This could be caused by one of the following conditions: 1) the ActivationSpec 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.
Action Make sure the ActivationSpec had been configured for the ResourceAdapter you are using. Make sure that the JNDI Name specified when deploying your MDB matches that specified when creating the application Spec on the ResourceAdapter.
J2CA0053W: Enlist option used is {0}. This differs from the desired option of {1} for resource {2}.
Explanation The resource adapter does not support a TransactionResourceRegistration setting of {1}. The J2C Runtime is using the default value of {0}.
Action None.
J2CA0054E: The MessageEndpoint activation failed because no ActivationSpec JNDI name was supplied.
Explanation In order to activate a MessageEndpoint (MDB) a JNDI name to a configured ActivationSpec must be supplied during MDB deployment.
Action Make sure the ActivationSpec had been configured for the ResourceAdapter you are using. Make sure that the JNDI Name specified when deploying your MDB matches that specified when creating the application Spec on the ResourceAdapter.
J2CA0055W: Connection handle not closed at end of the unit of work scope. Handles will be closed by the Connection Manager.
Explanation Either a Activity Session, Transaction, or Local Transaction work scope is ending and connection handles have not been closed. Support for caching handles outside the current unit of work scope is not supported for this configuration or release.
Action Inspect your code and make sure you always close your connection handles before the unit of work the handle is involved in ends.
J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource {1}. The exception which was received is {0}
Explanation The Connection Manager has been notified by the Resource Adapter that a fatal error has occurred on the connection. This informational message is logged so that the user can see the exception returned.
Action The Connection Manager will remove the failing connection, or all the connections (depending on configuration) from the pool. This is normal behavior. If you look at the exception and determine that it is unexpected, then investigate the exception and correct the problem which is causing the exception to occur.
J2CA0057E: The interactionPending method was unable to find a transaction wrapper class.
Explanation Websphere internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0058E: The ConnectionManager was unable to associate Connection {0} with ManagedConnection {1} for resource {3}. Received exception: {2}
Explanation Usually this is due to an application error. An example : A cached connection is enlisted in a transaction, then the connection is closed. Before the transaction completes another request is sent to the same EJB that originally opened the connection. The cached handle is still associated with the original transaction and cannot be reassociated until that transaction commits.
Action Check the application and make sure that the transaction is committed as soon as possible after connections are closed.
J2CA0060E: PrivilegedActionException calling doPrivileged: {0}
Explanation Websphere internal error in the security runtime.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0061W: Error creating XA Connection and Resource {0}
Explanation An error occurred recreating an XA Resource, the resource could not be recovered.
Action Check for other related messages that will further explain the specific problem.
J2CA0062W: Encountered an error while cleaning up the Managed Connection: {0} {1}
Explanation The cleanup operation on a managed connection failed. The connection could not be cleaned up after recovery.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0063W: Encountered an error while destroying the Managed Connection: {0} {1}
Explanation The destroy operation on a managed connection failed after recovery.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0064E: Failed to get transaction status {0}
Explanation Websphere internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0065E: ClassCastException tried to cast : {0} to {1}. {2}
Explanation WebSphere internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0066E: Failed calling get method {0} on the ManagedConnectionFactory {1} used by resource {4} with the value {2}. Exception is {3}.
Explanation The resource adapter does not support the getter method as documented.
Action Contact the developer of the resource adapter.
J2CA0067W: Invalid {0} setting of {1}. Defaulting to {2} instead.
Explanation An internal error occurred, using the default value.
Action This is a warning message, if an error occurs later it may help in diagnosing the problem. Otherwise this message can be ignored.
J2CA0068E: Method {0} could not create {1} instance.
Explanation An internal error occurred.
Action This message is due to an error in the internal J2C runtime processing. Contact WebSphere support and provide the data from running collector.bat.
J2CA0069E: Method {0} could not create {1} instance. Failed with exception: {2}
Explanation An internal error occurred.
Action This message is due to an error in the internal J2C runtime processing. Contact WebSphere support and provide the data from running collector.bat.
J2CA0070W: Component {0}, is holding {1} number of connection(s).
Explanation This message indicates number of connection(s) being held by a component. his message follows the resource unavailable exception when getConnection request failed in user code.
Action Check if one or more components are excessively holding connections. A user programming error may not be closing connection. If number of connections appear to be ok, try increasing "max pool size".
J2CA0072E: Unable to obtain a ConnectionFactory or DataSource configuration ID while trying to start a ResourceAdapter. The ConnectionFactory or DataSource configuration information which makes up the ID is either missing or corrupted. The following Exception was caught: {0}
Explanation This may be a symptom of an incorrectly hand-modified resources.xml document. Alternatively, if you are using an application with an embedded ResourceAdapter, this may be a symptom of an incorrectly hand-modified deployment.xml document.
Action If you have hand-modified either a resources.xml or a deployment.xml file, please correct any errors there. If you have not edited these files, this may be and internal application server error.
J2CA0073E: Unable to delist connection from resource {2} from transaction in method {0} due to exception. Initiating destruction of connection. Exception is: {1}
Explanation Due to an internal error which was received, the Connection Manager was unable to delist a connection from the transaction it was involved in. As a result it will attempt to destroy the connection.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0074E: Unable to enlist connection from resource {2} with current transaction in method {0} due to exception. Initiating destruction of connection. Exception is: {1}
Explanation Due to an internal error which was received, the Connection Manager was unable to enlist a connection with the current transaction. As a result it will attempt to destroy the connection.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0075W: An active transaction should be present while processing method {0}.
Explanation Normal connection management processing requires the presence of a transaction in order to execute the current method.
Action Start a transaction if your application requires a transaction to successfully use the connection.
J2CA0076E: An active transaction is required for the method {0}.
Explanation Processing requires the presence of a transaction in order to execute the current method. The most common cause of a missing transaction context is that the transaction had timed out.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0077E: An exception was caught while trying to obtain a javax.resource.cci.LocalTransaction from a ManagedConnection for resource {1}. The exception is: {0}
Explanation The Connection Manager was unable to obtain a LocalTransaction from the ResourceAdapter. This indicates some problem with the ResourceAdapter.
Action Look for error messages from the ResourceAdapter to identify the problem.
J2CA0078E: An exception was caught while trying to obtain a javax.transaction.xa.XAResource from a ManagedConnection on datasource {1}. The exception is: {0}
Explanation The Connection Manager was unable to obtain a XAResource from the ResourceAdapter. This indicates some problem with the ResourceAdapter.
Action Look for error messages from the ResourceAdapter to identify the problem.
J2CA0079E: Method {0} has detected an internal illegal state and is throwing an IllegalStateException. The exception is: {1}
Explanation The Connection Manager has detect an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0080E: Method {0} has detected an internal illegal argument and is throwing an IllegalArgumentException. The exception is: {1}
Explanation The Connection Manager has detect an internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0081E: Method {0} failed while trying to execute method {1} on ManagedConnection {2} from resource {4}. Caught exception: {3}
Explanation The Connection Manager caught an exception while trying to perform an operation on a ManagedConnection.
Action Since the ManagedConnection is part of the ResourceAdapter, look for messages from the ResourceAdapter to further isolate the problem.
J2CA0082W: InactiveConnectionSupport option {0} used by resource {2}. This differs from the desired option of {1}.
Explanation The resource adapter does not support an InactiveConnectionSupport setting of {1}.
Action Contact the developer of the resource adapter.
J2CA0083W: Method {0} failed while trying to execute method {1} on the ConnectionManager. Failing handle is: {2}. Caught the following Exception: {3}
Explanation The ConnectionHandleManager caught an exception while trying to perform a handle reassociation operation. This exception may or may not be a problem. This is expected behavior following a transaction timeout. In all other cases this should be considered a Websphere internal error.
Action Look for messages indicating that a transaction has timed out. If timeouts are occurring you can ignore this message. If you don't see evidence of a transaction timeout, contact support.
J2CA0084W: Transaction recovery registration failed for ResourceAdapter {0} with exception {1}.
Explanation Registration with the transaction service for recovery of transactions for inbound messages to this ResourceAdapter failed. Subsequent use inbound transactions may also fail.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0085I: Connector property {0} on resource {1} has a null value.
Explanation 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.
Action None.
J2CA0086W: Shareable connection {0} from resource {1} was used within a local transaction containment boundary.
Explanation Shareable connections are not allowed within a local transaction containment boundary.
Action Connection was made non-shareable. This may have adverse effects. In the future, you will get an exception in this case.
J2CA0087E: The transaction manager was unable to enlist resource {0} from datasource {1}.
Explanation This message indicates a problem enlisting in a transaction, the resource may have already been enrolled in a transaction or the transaction may not have been in the correct state.
Action Check that the business logic of the application is properly catching the thrown exception and contains the necessary recovery logic. Also check log files for earlier errors (specifically transaction errors) that may have caused the exception.
J2CA0088W: The ManagedConnection that is being destroyed from resource {1} is in an invalid state {0}. Processing will continue.
Explanation An internal error has occurred.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0089E: The method {0} on ResourceAdapter java bean {1} failed with the following exception: {2}
Explanation The ResourceAdapter threw an exception. This could indicate a problem with the ResourceAdapter.
Action Check the exception for more information.
J2CA0090I: This is an English only message: {0}.
Explanation Message was added after translation cutoff and so is not translated.
Action See message for details.
J2CA0091E: An InterruptedException occurred on the Garbage Collector thread.
Explanation An unexpected InterruptedException occurred on the Garbage Collector thread. J2C processing will continue, however Unused and Aged connections will not be collected.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0092E: This is an English only message: {0}.
Explanation Message was added after translation cutoff and so is not translated.
Action See message for details.
J2CA0093W: This is an English only message: {0}.
Explanation Message was added after translation cutoff and so is not translated.
Action See message for details.
J2CA0094E: The transaction this operation is part of has failed. Cancelling the operation. Throwing exception {0}.
Explanation The transaction this operation was a part of has failed, possibly due to a transaction timeout.
Action See messages from the transaction service for more information on the failure.
J2CA0095E: Unable to obtain authentication information for J2CConnectionFactory {0} : {1}.
Explanation MappingModule object could not be read.
Action See ffdc logs for more information on the failure.
J2CA0096E: NullPointerException on setManagedConnection on MCWrapper {0}
Explanation The attempt to create a new MCWrapper failed, causing a NullPointerException on use.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0097E: The call to ContainerComponentMetaData.getLocalTran returned null: {0}.
Explanation An unexpected null value was returned from ContainerComponentMetaData.getLocalTran().
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0098E: A ClassCastException occurred attempting to cast event.getSource to ManagedConnection: {0}
Explanation The source of the event fired on the listener was not of type ManagedConnection
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0099E: Invalid EJB component: Cannot use an EJB module with version {0} and CMP version {1} using {2}.
Explanation An attempt to run an EJB component incompatible with WebSphere Application Server was detected.
Action Evaluate the EJB version and CMP version supported by the EJB component, correct, and re-deploy.
J2CA0100E: The information object needed to deactivate the endpoint was not found for deactivationKey {0}. Throwing exception {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0101E: Unable to obtain RA miscellaneous configuration information for J2CConnectionFactory {0} : {1}.
Explanation RA miscellaneous configuration object could not be read.
Action See ffdc logs for more information on the failure.
J2CA0102E: Invalid EJB component: Cannot use an EJB module with version {0} using {1}.
Explanation An attempt to run an EJB component incompatible with WebSphere Application Server was detected.
Action Evaluate the EJB version supported by the EJB component, correct, and re-deploy.
J2CA0103W: Duplicate connector property not added. {0}.
Explanation An attempt was made to add a duplicate connector property. The property was not added.
Action A Custom Property of a connection factory or datasource specified a UserName or Password while a component-managed authentication alias was also specified. The alias takes precedence over the Custom Properties. Alternatively, this could be a symptom of a hand-modified resources.xml document.
J2CA0104E: Authentication mechanism preference {0} is not supported by the resource adapter for connection factory or datasource {1}.
Explanation The authentication mechanism must be one of those specified in the resource adapter's ra.xml document element <authentication-mechanism-type>.
Action Use the Administrative Console to specify an authentication mechanism which is supported by the resource adapter.
J2CA0105W: Authentication mechanism preference not specified for connection factory or datasource {0}.
Explanation This may be a symptom of a hand-modified resources.xml document. A Subject may contain null credentials. The resource adapter may or may not accept this Subject.
Action Use the Administrative Console to specify an authentication mechanism which is supported by the resource adapter. If the resource adapter does not support any authentication mechanism, choose none.
J2CA0106E: A 5.0 DataSource was attempted to be used in a WebModule that was not level 2.3.
Explanation 5.0 DataSources are only supported for servlet level 2.3 WebModules.
Action Evaluate whether the servlet in question can be migrated to level 2.3, if so migrate the application and redeploy. If it cannot be migrated, the servlet must use a WAS 4.0 DataSource.
J2CA0107I: Component-managed authentication alias not specified for connection factory or datasource {0}.
Explanation The component is accessing the connection factory or datasource with res-auth=Application, but no user/pw is available. This may result in an allocateConnection failure later on.
Action In some cases, this may be ignored. For example, if a valid user/pw in the ConnectionSpec is passed on the getConnection method, or if the backend resource does not require authentication. If you are experiencing problems logging in to the backend resource, use the Administrative Console to specify a component-managed authentication alias for {0}.
J2CA0108E: the parent MBean for {1} could not be found, the identifier used to find the MBean is {0}.
Explanation An internal error has occurred. The parent MBean should be created when the ConnectionFactory or DataSource is bound into the namespace.
Action Run collector.bat and provide the data to WebSphere support.
J2CA0109E: Method {0} obtained a NULL {1} where a required object was expected. Throwing exception {2}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0110W: A JMException was thrown when creating ObjectNames for {0} the exception is {1}.
Explanation An internal error has occurred. The ObjectNames used on the lookup were not created.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0111W: An Error occurred when trying to find a cached instance of J2C Perf.
Explanation An internal error occurred when trying to obtain a cached instance of J2CPerf.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
Explanation An internal error has occurred. The MBeans should be created when binding the referenceable object into JNDI and during a JNDI lookup respectively. Both ObjectNames will be set to null, and the Pmi Data will be created, but will not link with the MBeans.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0113W: The ObjectName for the provider MBean was null. This will cause an error with PMI and will prevent the factory or dataSource MBean from being linked to its J2CResourceadapter or JDBCProvider (respectively) "parent" MBean.
Explanation An internal error has occurred. The MBeans will not be linked correctly. This does not effect the use of the ConnectionFactory or DataSource, but may cause an error if you are using PMI.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0114W: No container-managed authentication alias found for connection factory or datasource {0}.
Explanation The component did not specify a login configuration on the resource-reference to {0}. The deprecated container-managed authentication on the connection factory or datasource is used, but no container-managed authenticaion alias was specified. A Subject with empty user/pw is constructed.
Action In some cases, this may be ignored. If you are experiencing problems logging in to the backend resource, define a login configuration on the resource-reference using a deployment tool. If the deprecated mechanism for container-managed authentication is desired, use the Admin Console or scripting tools to create the connection factory or datasource 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.
J2CA0115W: {0} occurred when trying to get the absolute path to %WAS_HOME% properties.
Explanation An internal error has occurred.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0116W: The root element {1} of XML document {0} is not as expected.
Explanation A properties file was not coded correctly.
Action Ensure that the root element of {0} is correct.
J2CA0117I: Properties file {0} with root element {1} was successfully read.
Explanation This is an informational message.
Action None.
J2CA0118W: An exception occurred when setting the trace writer on the ManagedConectionFactory. The MCF used was {0}. The exception was {1}.
Explanation The trace writer was not able to be set on the MCF. You will not see any Resource Adapter specific trace entries, WebSphere trace will work if it is enabled.
Action Check that there are no other exceptions in the FFDC logs - the other exceptions may indicate a problem with the ManagedConnectionFactory or in getting the correct PrintWriter. If there are no other exceptions, contact support for the resource adapter.
J2CA0119W: An Exception occurred when reading properties for a DataSource MBean {0}.
Explanation Usually this means an internal error has occurred. The DataSource MBean will not have all the information you may expect (some operations will return bad values). However the DataSource runtime object is still useable and this warning will not adversely effect any applications.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0120W: An exception occurred when trying to read J2C MBean properties from the referenceable object {0}.
Explanation An internal error has occurred. However the error is non-terminal, the ConnectionFactory or DataSource will work correctly. An MBean might not be created for this object, and even if one is it may contain bad data. This can also effect PMI - it might not be able to link to the MBean.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0121W: An Exception occurred when trying to register an MBean for {0}. : {1}.
Explanation An internal error has occurred and the J2C Runtime was unable to create an MBean. The ConnectionFactory or DataSource will still function, however statistics cannot be accessed through an MBean, this also effects the PMI link to the MBean.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0122I: Resource reference {0} could not be located, so the following default values are used: {1}
Explanation An internal error may have occurred, but most likely a direct JNDI lookup was done on a ConnectionFactory or DataSource. Processing continues using the default resource-ref values.
Action None.
J2CA0123I: Server-wide pool properties were read from {0}.
Explanation This is an informational message.
Action None.
J2CA0124I: Pool properties for {1} were read from {0}.
Explanation This is an informational message.
Action None.
J2CA0125W: Error parsing XML document {0}.
Explanation The XML document is not formed correctly.
Action See the XML document for possible errors.
J2CA0126W: Invalid format for value of element {0} in node {1} of XML document {2}. Returning {3}.
Explanation The XML document is not formed correctly.
Action See the XML document for possible errors.
J2CA0127I: A ConnectionWaitTimeout of 0 has been specified for {0}. The request will wait until a connection can be obtained.
Explanation A ConnectionWaitTimeout of 0 indicates infinite wait time, this thread will sleep until a connection is freed.
Action None.
J2CA0128E: An Exception occurred while trying to start ResourceAdapter {0}. The exception is: {1}
Explanation An Exception occurred while trying to start a ResourceAdapter. This has occurred either during the reading of the configuration properties or during the actual call to start the ResourceAdapter class for this Resource Adapter. Check the exception and other error messages for more details.
Action Take action based on the exception or the other errors in the log.
J2CA0129E: An exception occurred while trying to instantiate the ActivationSpec class {0} used by ResourceAdapter {1} : {2}.
Explanation This message indicates a problem while attempting to create an ActivationSpec object. There are several possible reasons for this problem. The most common reason is that the runtime couldn't find the appropriate class for the ActivationSpec via the current class loader. This could also be related to an invalid XML definition for the Resource Adapter.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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.
Explanation A J2C Authentication Data Entry corresponding to the Component-managed Authentication Alias was expected but not found.
Action Define a J2C Authentication Data Entry under Security > JAAS Configuration in the WebSphere Administrative console, and choose this for Component-managed authentication alias on the Connection Factory or Data Source configuration.
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.
Explanation A set method does not exist for listed <activation-config-property> on the ActivationSpec 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.
Action Redeploy the application and correct any mapping mistake, or reassemble the application with valid <activation-config-property>s.
J2CA0132E: Method {0} caught exception {1}.
Explanation The method caught an exception which is most likely due to a Websphere internal error.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0133E: For the installed ResourceAdapter {0} and ActivationSpec {1} Required ActivationSpec properties were missing from the activation-config-properties for the MDB being activated. See the following exception for details: {3}
Explanation The ResourceAdapter marks certain ActivationSpec properties as required and the value has not been supplied. These properties can be set from two different spots. The first is when you create an ActivationSpec configuration object on under the installed ResourceAdapter. The second come from the application itself as an <activation-config-property> and may be modified using the application assembly tool.
Action Supply the required values on either the ActivationSpec which is configured on the installed ResourceAdapter, or in an <activation-config-property> within the application.
J2CA0134E: An ActivationSpec class name not found for ResourceAdapter {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 rethrown. The exception is: {2}.
Explanation The BootstrapContext was unable to return a WorkManager to the ResourceAdapter due to a problem configuring the WorkManager.
Action See the exception and previous log entries for more details.
J2CA0136E: Unable to create an XATerminator, due to an exception. The exception will not be rethrown. The exception is: {0}.
Explanation The BootstrapContext was unable to return an XATerminator to the ResourceAdapter due to an exception.
Action See the exception and previous log entries for more details.
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}
Explanation The ResourceAdapter has rejected the ActivationSpec as it is currently configured.
Action See the exception from the ResourceAdapter for more details.
J2CA0138E: The MessageEndpoint activation failed for ActivationSpec {0} and MDB Application {1}, due to the following exception: {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action See the exception and other log entries for more details.
J2CA0139E: The MessageEndpoint deactivation failed for ActivationSpec {0} and MDB Application {1}, due to the following exception: {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action See the exception and other log entries for more details.
J2CA0140E: The MessageEndpoint deactivation failed because the MessageEndpoint is not currently activated.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0141W: Failed to unregister the ActivationSpec from the Transaction Service. Caught exception {0}.
Explanation The transaction service was unable to unregister an ActivationSpec at this time. This may be due to outstanding transactional work involving this ActivationSpec and may be a transient error.
Action Restarting the server should clear up any outstanding transactions. If the error persists, contact customer service.
J2CA0142E: Classloader is not an instance of CompoundClassLoader.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0143E: Embedded ResourceAdapter initialization failed due to Exception: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0144W: No mappingConfigAlias found for connection factory or datasource {0}.
Explanation The component is using container-managed authentication, but no mappingConfigAlias was specified. DefaultPrincipalMapping will be used.
Action This is likely a scripting error with {0} or its corresponding CMPConnectorFactory.
J2CA0145W: Unable to start ResourceAdapter due to the following exception: {0}.
Explanation The server was unable to start a ResourceAdapter.
Action See exception and previous log entries for more information.
J2CA0146W: The lookup of the Destination with JNDI Name {0} failed due to exception {1}.
Explanation 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.
Action Make sure the Destination had been configured for the ResourceAdapter you are using. The Destination can either be configured as part of the ActivationSpec configuration or during the MDB step during application deployment. Make sure that the JNDI Name specified matches that specified when creating the Destination AdminObject on the ResourceAdapter.
J2CA0147W: CMPConnectorFactory is missing {0}-managed authentication alias, but corresponding Datasource {1} defines {0}-managed authentication alias {2}.
Explanation 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.
Action Make sure the Destination had been configured for the ResourceAdapter you are using. The Destination can either be configured as part of the ActivationSpec configuration or during the MDB step during application deployment. Make sure that the JNDI Name specified matches that specified when creating the Destination AdminObject on the ResourceAdapter.
J2CA0148W: A null ConnectionHandle was found in the CONNECTION_CLOSED ConnectionEvent {0}
Explanation A CONNECTION_CLOSED ConnectionEvent is required by the J2EE Connector Architecture to contain a valid ConnectionHandle associated with the ManagedConnection instance.
Action The ResourceAdapter must use ConnectionEvent.setConnectionHandle() to supply the ConnectionHandle in the CONNECTION_CLOSED ConnectionEvent.
J2CA0149W: The contents of the Authentication Alias assigned to the ActivationSpec {0} used by MDB {1} are not valid. Username and/or the Password were either null or blank. The AuthenticationAlias was: {2}, its UserName was: {3}, and its Password was: {4}
Explanation UserName and/or Password assigned to the Authentication Alias being used by the MDB is not valid.
Action Make sure that authentication alias has been properly configured and assigned to either the ActivationSpec configuration, or as specified as part of the MDB deployment step.
J2CA0150E: The ResourceAdapter {0} failed to {1} because the ResourceAdapter was not found.
Explanation The given ResourceAdapter could not be found to perform the operation. This may be due to the fact it has already been shut down.
Action Make sure the MBean you are using is still valid.
J2CA0151E: Activation of MessageEndpoint for application {0} failed because the targeted ResourceAdapter, {1}, is not currently started.
Explanation The given ResourceAdapter could not be found or was not in a started state so the message endpoint could not be activated. This may be due to the fact it has already been shut down.
Action Make sure the ResourceAdapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid ResourceAdapter.
J2CA0152E: Deactivation of a MessageEndpoint failed because the targeted ResourceAdapter, {0}, is not currently started or was not found. Deactivation key is: {1}
Explanation The given ResourceAdapter could not be found or was not in a started state so the message endpoint could not be deactivated.
Action Make sure the ResourceAdapter is configured correctly, has not been stopped, and that the MDB is mapped to use a valid ResourceAdapter. Also, applications must be stopped before the Resource Adapter is stopped.
J2CA0153E: The requested ResourceAdapter {0} is not in a started state.
Explanation The requested ResourceAdapter was found but was not in a started state. A ResourceAdapter is not usable in a stopped state. This may be due to the fact it has stopped by an MBean request, the application server may be shutting down, or if the ResourceAdapter is embedded within an application, the application has been stopped.
Action Make sure the ResourceAdapter is started.
J2CA0154E: The method {0} on class {1} returned the following exception: {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0155W: The lookup of the Authentication Alias {0}, assigned to the ActivationSpec {1} by application {2} has failed.
Explanation The JNDI lookup of the Authentication Alias assign to the ActivationSpec in use by the given MDB did not complete successfully.
Action Make sure that authentication alias has been properly configured and assigned to either the ActivationSpec configuration, or as specified as part of the MDB deployment step.
J2CA0156E: The MessageEndpoint reactivation failed during a resume opperation on a ResourceAdapter. The ActivationSpec was {0}, the MDB Application was {1}, and the exception was: {2}
Explanation This exception is unexpected. The cause is not immediately known.
Action See the exception and other log entries for more details.
J2CA0157E: Unable to get the ThreadPoolMgr service.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0158E: Failed to bind an ActivationSpec to the namespace with JNDI name {0}. The associated Resource Adapter key is {1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0159W: The attempt to stop ResourceAdapter failed during XARecovery cleanup and will be ignored. It was due to the following exception: {0}
Explanation An exception occurred while attempting to stop a ResourceAdapter.
Action Take appropriate action based on the exception text.
J2CA0160W: The type of the destination property on the 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.
Explanation The type of the destination property on the activationSpec must be javax.jms.Destination if the destination JNDI name is use. The type on the activation spec is not compatible with this. Therefore, the JNDI name will be ignored.
Action Take appropriate action based on the exception text.
J2CA0161W: The type of the object refered 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''s class was: {1}
Explanation The type of the destination property on the activationSpec must be javax.jms.Destination if the destination JNDI name is use. The type on the activation spec is not compatible with this. Therefore, the JNDI name will be ignored.
Action Take appropriate action based on the exception text.
J2CA0162W: You have supplied a destination JNDI name for ActivationSpec {0}. This activationSpec does not have a setDestination method. The destination JNDI Name will be ignored.
Explanation You do not need to supply a destination JNDI name.
Action Do not supply a destination JNDI name.
J2CA0163E: The type of the object refered to by the supplied destination JNDI name is wrong. The object must implement javax.jms.destination. Destination is a required property for this ActivationSpec. The destination JNDI name was: {0}. The supplied object''s class was {1}.
Explanation The type of the destination property on the activationSpec must be javax.jms.Destination if the destination JNDI name is use. The type on the activation spec is not compatible with this. Therefore, the JNDI name will be ignored.
Action Supply a destination JNDI name which refers to an AdminObject which implements the javax.jms.Destination interface.
J2CA0164E: The lookup of the Destination with JNDI Name {0} failed. The Destination is required by the ActivationSpec. The lookup failed due to exception {1}.
Explanation 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.
Action Make sure the Destination had been configured for the ResourceAdapter you are using. The Destination can either be configured as part of the ActivationSpec configuration or during the MDB step during application deployment. Make sure that the JNDI Name specified matches that specified when creating the Destination AdminObject on the ResourceAdapter.
J2CA0165I: The connection pool is not available. The connection pool is created at first JNDI lookup of a data source or connection factory.
Explanation The internal data structures have not been initialized for this connection factory. Some MBean operations are not possible in this state.
Action Attempt the intended operation after the connection factory has been accessed.
J2CA0200E: The J2C runtime was unable to find the class {0}.
Explanation The J2C runtime was unable to find the given class.
Action Ensure that the associated XA resource provider is configured and restart the server. The resource can then be unconfigured and the server shutdown.
J2CA0201E: Object cannot be deserialized. The exception stack trace follows: {0}
Explanation This is an internal system error and is probably caused by an earlier failure.
Action Examine any related messages in order to determine the cause of the problem. If there are no related messages or they do not help to resolve the problem, please contact IBM Support.
J2CA0202E: Internal Error: Failed to find the RAWrapperImpl instance associated with the following key {0}. Throwing exception {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0203E: The runtime has detected a request to create more than one instance of a ResourceAdapter class. This resource adapter does not support more than one instance of a ResourceAdapter class per JVM. The resource adapter which is already initialized in the server is {0}. The resource adapter that is currently trying to be initialized is {1}.
Explanation Some resource adapters can only tolerate one instance of their ResourceAdapter class to be instantiated within a JVM. If you have more than one such resource adapter instance configured to run on a given server, you will get this message. This can happen for any of the following reasons: 1) You configured the same resource adapter instance at more then one scope (i.e. cell, node, or server); 2) You deployed more than one Application which embeds the same resource adapter with a configuration such that the ResouceAdapter class says that the two instances are equal, or 3) you have one stand alone resource adapter deployed in a server and an application embeds the same resource adapter on the same server with a configuration such that the ResourceAdapter class indicates that both are equal.
Action Change you configuration such that the two resource adapters are not deployed to the same server.
J2CA0278W: Could not deserialize field {0} in class {1}; default value will be used
Explanation During deserialization of an object, an expected field was not found. This is most likely due to the fact that the object is being deserialized by a different version of the class than the one that serialized it.
Action This warning indicates a potential problem, but no user action is necessary unless further errors arise.
J2CA0279W: An Error occurred when trying to create pmi data.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0280W: When merging config property {0}, its type, {1}, did not match the introspected type, {2}. Keeping the introspected type.
Explanation Configuration properties of a Resource Adapter or Activation Spec override their corresponding introspected properties, unless the type does not match.
Action Check the type of the config property.
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.
Explanation User-defined properties of a Resource Adapter or Activation Spec override their corresponding introspected and config properties, unless the type does not match.
Action Check the type of the user-defined config property.
J2CA0282W: Required property {0} was missing from activation spec.
Explanation Required property {0} was missing from activation spec.
Action Supply a correct {0} property.
J2CA0283E: Attempt to access embedded resource adapter of another application via connection factory {0}.
Explanation An application attempted to lookup a connection factory associated with another application's embedded resource adapter.
Action The application should use a connection factory associated with its own resource adapter or use a connection factory associated with a standalone resource adapter.
J2CA0284W: Resource property {0} is skipped.
Explanation The property was not found via introspection on the underlying bean.
Action Compare this property in the ra.xml and the java bean.
J2CA0285W: Method {0} caught an exception during validating managed connections for resource {3}, throwing {2}. Original exception: {1}
Explanation A call to method getInvalidConnections returned a resource exception.
Action Contact the resource adapter provider.
J2CA0286W: Connection {0} from resource {1} cannot be used with pretest connection configured. Turning off pretest connection support for this resource adapter.
Explanation This connections resource adapter does not support the pretest connection function.
Action Reconfigure pretest connection to false for this resource adapter.
J2CA0287E: {0} does not have a single ConnectionDefinition. The program will attempt to continue using the first ConnectionDefinition.
Explanation This are either no or more than one ConnectionDefinitions defined. This implies an internal XML formatting error.
Action Make sure there is only a single ConnectionDefinition defined.
J2CA0288I: Pool property {0} changed from {1} to {2} for pool {3}
Explanation A pool properties value has been changed.
Action None.
J2CA0289W: Thread pool {0} has not been defined in the server configuration or is not configured correctly.
Explanation 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.
Action Create the missing thread pool or fix the configuration for the thread pool.
J2CA0290W: Thread pool {0} will be used.
Explanation The thread pool that was specified for the resource adapter has not been configured.
Action Configure the missing thread pool.
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.
Explanation Application ear file has supplied an non-existed <activation-config-property>.
Action Fix the application descriptor.
J2CA0292E: The ManagedConnection from resource {0} could not be enlisted with the current transaction.
Explanation An internal error has occurred while attempting to process the lazyEnlist method.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0293E: The Connection Manager lazyEnlist method requires a non-null ManagedConnection parameter for resource {0}.
Explanation Normally this indicates an error with the resource adapter implementation. The resource adapter called lazyEnlist with a null ManagedConnection.
Action Contact the resource adapter provider for assistance. 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.
J2CA0294W: Deprecated usage of direct JNDI lookup of resource {0}. The following default values are used: {1}
Explanation Avoid using the fully qualified names of resources when looking up resources through Java Naming Directory Interface (JNDI). The J2EE programming model recommends the use of resource references and the local JNDI java:comp/env context.
Action Modify the application to use the preferred J2EE programming model with resource references and the local JNDI java:comp/env context.
J2CA0300I: ActivationSpec {0} has no configuration properties. The ActivationSpec class is {1} for ResourceAdapter {2}. This may have undesirable effects.
Explanation No configuration properties were supplied for the ActivationSpec. This may be normal, however, if a value is required not having a value could cause a failure.
Action If a value is required please supply one.
J2CA0301E: The Resource Adapter {0} is not configured properly for HA. HA is disabled. Configured HA{roperties were isEnableHASupport = {1}, and HACapabiliy = {2}.
Explanation There was a mismatch between the configured isEnableHASupport boolean and the HACapability. Processing continues with HA disabled.
Action Make sure the Resource adapter is configured correctly and implements the getHACapability() method and has the isEnabledHASupport property.
J2CA0302E: Invalid HA State, Resource Adapter {0}, has HACapabiliy = {1}.
Explanation Normally this indicates an unsupported setting. HACapability greater than 1 (one) is not supported.
Action Make sure the Resource adapter is configured with HACapability of 0 or 1.
J2CA0303E: Attempting to {0} Resource Adapter {1} while under HA control.
Explanation Normally this indicates a suspend/resume operation was attempted while HA is enabled. Only outbound portions of the RA will be suspended or resumed.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA0306I: Application {0} has provided no <activation-config-property> for the ActivationSpec class {1} of ResourceAdapter {2}. This may have undesirable effects.
Explanation No value was supplied for the activation-config-property. This may be normal. If a value is required, not having a value could cause a failure.
Action If a value is required please supply one.
J2CA1002E: Invalid MCWrapper {0} from the free pool for resource {1}.
Explanation The attempt to reserve an MCWrapper failed.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
J2CA1003E: Failed to remove MCWrapper {0} from the shared pool.
Explanation The attempt to remove an MCWrapper failed, causing a potential problem in the shared pool.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
Reference topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 5:37:33 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.j2c.resources.J2CAMessages.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)