WebSphere Process Server messages     Operating Systems: All supported

J2CA

J2CA0001E: An exception occurred while trying to read the Resource Adapter Deployment Descriptor for {0} : {1}.
Problem 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.
User response 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}.
Problem This message indicates a problem with the Systems Management configuration for the Resource Adapter. A Deployment Descriptor does not exist for this Resource Adapter.
User response 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}.
Problem 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.
User response 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}.
Problem This message indicates a problem with the Systems Management configuration of the Connection Factory. The Properties do not exist for this Connection Factory.
User response 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}.
Problem 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.
User response 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}.
Problem 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.
User response 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.
Problem 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.
User response 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.
Problem 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.
User response 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}.
Problem 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.
User response 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}.
Problem 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.
User response 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}.
Problem This message indicates a problem with the Reference object that was initially stored in the JNDI name space.
User response 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}.
Problem This message indicates a problem with the Reference object that was initially stored in the JNDI name space.
User response 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}.
Problem This exception indicates a problem with creating the ManagedConnectionFactory from the stored Reference in the JNDI name space.
User response 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.
Problem 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.
User response 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}.
Problem 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.
User response 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.
Problem 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.
User response 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.
Problem 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.
User response 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}.
Problem 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.
User response If the exception text does not indicate a situation that is user controlled, then contact support and collect diagnostic data for them.
J2CA0019W: No Managed Connection Factory Properties data could be assembled for {0}. Processing continued.
Problem 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.
User response 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}.
Problem 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.
User response If there are no user controlled indications, the message may be due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them.
J2CA0021E: An exception occurred while trying to get a Connection from the Managed Connection resource {1} : {0}.
Problem 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.
User response If there are no user controlled indications, the message may be due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them.
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.
Problem 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.
User response 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.
Problem 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.
User response 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}.
Problem 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.
User response 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}.
Problem 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.
User response 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}.
Problem This message indicates a problem while processing the given method. The processing within the method did not complete successfully.
User response 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}.
Problem This message indicates a problem while processing the given method. The processing within the method did not complete successfully.
User response 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}
Problem 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.
User response 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}.
Problem 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.
User response 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}
Problem 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.
User response 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}.
Problem This is most likely an error with the specific resource adapter.
User response Contact support for the resource adapter.
J2CA0035E: Class {0}, used by resource {2} did not contain method set{1}. Processing halted.
Problem 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.
User response 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.
Problem 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.
User response 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}.
Problem An internal error has occurred when reading properties from the namespace.
User response 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}.
Problem An internal error has occurred when reading properties from the namespace.
User response 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}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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}.
Problem Internal error in the J2C runtime. A valid transaction context was required for the given operation but was not found.
User response 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}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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}
Problem Check the failing path string and verify that any non-expanded variables are valid (including their case).
User response 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}
Problem 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.
User response 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}.
Problem An internal error occurred when getting a Subject. A container-managed authentication alias may not have been selected on the connection factory or datasource.
User response 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}.
Problem A connection wait timeout has occurred. A ConnectionWaitTimeoutException was thrown.
User response 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}
Problem An error occurred during creation of a ManagedConnection. Usually this can be resolved by looking at the error messages from the resource adapter.
User response 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}.
Problem 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.
User response 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}
Problem The server was unable enable transaction recovery for this ResourceAdapter. Possible causes include: errors in the archive, class, or native paths; internal server errors.
User response Validate your archive, class, and native paths.
J2CA0049W: ResourceAdapter {0} is being stopped with MessageEndpoints still activated. These MessageEndpoints will be forcefully deactivated.
Problem 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.
User response 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.
Problem 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.
User response None.
J2CA0051E: The attempt to stop ResourceAdapter {0} failed due to the following exception: {1}
Problem An exception occurred while attempting to stop a ResourceAdapter.
User response Take appropriate action based on the exception text.
J2CA0052E: The lookup of the ActivationSpec with JNDI Name {0} failed due to exception {1}.
Problem 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.
User response 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}.
Problem The resource adapter does not support a TransactionResourceRegistration setting of {1}. The J2C Runtime is using the default value of {0}.
User response None.
J2CA0054E: The MessageEndpoint activation failed because no ActivationSpec JNDI name was supplied.
Problem In order to activate a MessageEndpoint (MDB) a JNDI name to a configured ActivationSpec must be supplied during MDB deployment.
User response 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.
Problem 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.
User response 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 Adapter for resource {1}. The exception which was received is {0}
Problem 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.
User response 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.
Problem WebSphere internal error.
User response 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}
Problem 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 re-associated until that transaction commits.
User response Check the application and make sure that the transaction is committed as soon as possible after connections are closed.
J2CA0060E: PrivilegedActionException calling doPrivileged: {0}
Problem WebSphere internal error in the security runtime.
User response 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}
Problem An error occurred recreating an XA Resource, the resource could not be recovered.
User response Check for other related messages that will further explain the specific problem.
J2CA0062W: Encountered an error while cleaning up the Managed Connection: {0} {1}
Problem The cleanup operation on a managed connection failed. The connection could not be cleaned up after recovery.
User response 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}
Problem The destroy operation on a managed connection failed after recovery.
User response 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}
Problem WebSphere internal error.
User response 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}
Problem WebSphere internal error.
User response 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}.
Problem The resource adapter does not support the getter method as documented.
User response Contact the developer of the resource adapter.
J2CA0067W: Invalid {0} setting of {1}. Defaulting to {2} instead.
Problem An internal error occurred, using the default value.
User response 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.
Problem An internal error occurred.
User response This message is due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them.
J2CA0069E: Method {0} could not create {1} instance. Failed with exception: {2}
Problem An internal error occurred.
User response This message is due to an error in the internal J2C runtime processing. Contact support and collect diagnostic data for them.
J2CA0070W: Component {0}, is holding {1} number of connection(s).
Problem 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.
User response 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}
Problem 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.
User response 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}
Problem 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.
User response 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}
Problem 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.
User response 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}.
Problem Normal connection management processing requires the presence of a transaction in order to execute the current method.
User response Start a transaction if your application requires a transaction to successfully use the connection.
J2CA0076E: An active transaction is required for the method {0}.
Problem 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.
User response 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}
Problem The Connection Manager was unable to obtain a LocalTransaction from the ResourceAdapter. This indicates some problem with the ResourceAdapter.
User response 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}
Problem The Connection Manager was unable to obtain a XAResource from the ResourceAdapter. This indicates some problem with the ResourceAdapter.
User response 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}
Problem The Connection Manager has detect an internal error.
User response 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}
Problem The Connection Manager has detect an internal error.
User response 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}
Problem The Connection Manager caught an exception while trying to perform an operation on a ManagedConnection.
User response 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}.
Problem The resource adapter does not support an InactiveConnectionSupport setting of {1}.
User response 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}
Problem The ConnectionHandleManager caught an exception while trying to perform a handle re-association operation. This exception may or may not be a problem. This is expected behavior following a transaction time-out. In all other cases this should be considered a WebSphere internal error.
User response Look for messages indicating that a transaction has timed out. If time-outs are occurring you can ignore this message. If you don't see evidence of a transaction time-out, contact support.
J2CA0084W: Transaction recovery registration failed for ResourceAdapter {0} with exception {1}.
Problem Registration with the transaction service for recovery of transactions for inbound messages to this ResourceAdapter failed. Subsequent use inbound transactions may also fail.
User response 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.
Problem 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.
User response None.
J2CA0086W: Shareable connection {0} from resource {1} was used within a local transaction containment boundary.
Problem Shareable connections are not allowed within a local transaction containment boundary.
User response 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}.
Problem 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.
User response 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.
Problem An internal error has occurred.
User response 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}
Problem The ResourceAdapter threw an exception. This could indicate a problem with the ResourceAdapter.
User response Check the exception for more information.
J2CA0090I: This is an English only message: {0}.
Problem Message was added after translation cutoff and so is not translated.
User response See message for details.
J2CA0091E: An InterruptedException occurred on the Garbage Collector thread.
Problem An unexpected InterruptedException occurred on the Garbage Collector thread. J2C processing will continue, however Unused and Aged connections will not be collected.
User response 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}.
Problem Message was added after translation cutoff and so is not translated.
User response See message for details.
J2CA0093W: This is an English only message: {0}.
Problem Message was added after translation cutoff and so is not translated.
User response See message for details.
J2CA0094E: The transaction this operation is part of has failed. Cancelling the operation. Throwing exception {0}.
Problem The transaction this operation was a part of has failed, possibly due to a transaction timeout.
User response See messages from the transaction service for more information on the failure.
J2CA0095E: Unable to obtain authentication information for J2CConnectionFactory {0} : {1}.
Problem MappingModule object could not be read.
User response See ffdc logs for more information on the failure.
J2CA0096E: NullPointerException on setManagedConnection on MCWrapper {0}
Problem The attempt to create a new MCWrapper failed, causing a NullPointerException on use.
User response 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}.
Problem An unexpected null value was returned from ContainerComponentMetaData.getLocalTran().
User response 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}
Problem The source of the event fired on the listener was not of type ManagedConnection
User response 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}.
Problem An attempt to run an EJB component incompatible with WebSphere Application Server was detected.
User response 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}
Problem This exception is unexpected. The cause is not immediately known.
User response 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}.
Problem RA miscellaneous configuration object could not be read.
User response See ffdc logs for more information on the failure.
J2CA0102E: Invalid EJB component: Cannot use an EJB module with version {0} using {1}.
Problem An attempt to run an EJB component incompatible with WebSphere Application Server was detected.
User response Evaluate the EJB version supported by the EJB component, correct, and redeploy.
J2CA0103W: Duplicate connector property not added. {0}.
Problem An attempt was made to add a duplicate connector property. The property was not added.
User response 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}.
Problem The authentication mechanism must be one of those specified in the resource adapter's ra.xml document element <authentication-mechanism-type>.
User response 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}.
Problem 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.
User response 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.
Problem 5.0 DataSources are only supported for servlet level 2.3 WebModules.
User response 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}.
Problem 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.
User response 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 back end resource does not require authentication. If you are experiencing problems logging in to the back end 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}.
Problem An internal error has occurred. The parent MBean should be created when the ConnectionFactory or DataSource is bound into the namespace.
User response 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}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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}.
Problem An internal error has occurred. The ObjectNames used on the lookup were not created.
User response 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 J2CPerf.
Problem An internal error occurred when trying to obtain a cached instance of J2CPerf.
User response 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.
Problem 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.
User response 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.
Problem 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.
User response 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}.
Problem 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 authentication alias was specified. A Subject with empty user/pw is constructed.
User response In some cases, this 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. 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.
Problem An internal error has occurred.
User response 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.
Problem A properties file was not coded correctly.
User response Ensure that the root element of {0} is correct.
J2CA0117I: Properties file {0} with root element {1} was successfully read.
Problem This is an informational message.
User response None.
J2CA0118W: An exception occurred when setting the trace writer on the ManagedConectionFactory. The MCF used was {0}. The exception was {1}.
Problem 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.
User response 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}.
Problem 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.
User response 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}.
Problem 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.
User response 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}.
Problem 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.
User response 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}
Problem 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.
User response None.
J2CA0123I: Server-wide pool properties were read from {0}.
Problem This is an informational message.
User response None.
J2CA0124I: Pool properties for {1} were read from {0}.
Problem This is an informational message.
User response None.
J2CA0125W: Error parsing XML document {0}.
Problem The XML document is not formed correctly.
User response See the XML document for possible errors.
J2CA0126W: Invalid format for value of element {0} in node {1} of XML document {2}. Returning {3}.
Problem The XML document is not formed correctly.
User response 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.
Problem A ConnectionWaitTimeout of 0 indicates infinite wait time, this thread will sleep until a connection is freed.
User response None.
J2CA0128E: An Exception occurred while trying to start ResourceAdapter {0}. The exception is: {1}
Problem 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.
User response 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}.
Problem 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.
User response 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.
Problem A J2C Authentication Data Entry corresponding to the Component-managed Authentication Alias was expected but not found.
User response 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.
Problem 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.
User response Redeploy the application and correct any mapping mistake, or reassemble the application with valid <activation-config-property>s.
J2CA0132E: Method {0} caught exception {1}.
Problem The method caught an exception which is most likely due to a WebSphere internal error.
User response 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: {2}
Problem 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 under the installed ResourceAdapter. The second comes from the application itself as an <activation-config-property> and may be modified using the application assembly tool.
User response 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}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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 re-thrown. The exception is: {2}.
Problem The BootstrapContext was unable to return a WorkManager to the ResourceAdapter due to a problem configuring the WorkManager.
User response 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 re-thrown. The exception is: {0}.
Problem The BootstrapContext was unable to return an XATerminator to the ResourceAdapter due to an exception.
User response 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}
Problem The ResourceAdapter has rejected the ActivationSpec as it is currently configured.
User response 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}
Problem This exception is unexpected. The cause is not immediately known.
User response 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}
Problem This exception is unexpected. The cause is not immediately known.
User response See the exception and other log entries for more details.
J2CA0140W: The Message Endpoint deactivation (the pause operation) failed for ActivationSpec {0} and MDB Application {1} because the Message Endpoint is currently deactivated or stopped.
Problem Message Endpoints that are stopped or deactivated cannot be paused.
User response Modify the application to verify the Message Endpoint is active before invoking the pause operation.
J2CA0141W: Failed to de-register the ActivationSpec from the Transaction Service. Caught exception {0}.
Problem The transaction service was unable to de-register an ActivationSpec at this time. This may be due to outstanding transactional work involving this ActivationSpec and may be a transient error.
User response Restarting the server should clear up any outstanding transactions. If the error persists, contact customer service.
J2CA0142E: Classloader is not an instance of CompoundClassLoader.
Problem This exception is unexpected. The cause is not immediately known.
User response 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}
Problem This exception is unexpected. The cause is not immediately known.
User response 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}.
Problem The component is using container-managed authentication, but no mappingConfigAlias was specified. DefaultPrincipalMapping will be used.
User response This is likely a scripting error with {0} or its corresponding CMPConnectorFactory.
J2CA0145W: Unable to start ResourceAdapter due to the following exception: {0}.
Problem The server was unable to start a ResourceAdapter.
User response See exception and previous log entries for more information.
J2CA0146W: The lookup of the Destination with JNDI Name {0} failed due to exception {1}.
Problem 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.
User response 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}.
Problem 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.
User response 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}
Problem A CONNECTION_CLOSED ConnectionEvent is required by the J2EE Connector Architecture to contain a valid ConnectionHandle associated with the ManagedConnection instance.
User response 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. The username and/or the Password were either null or blank. The AuthenticationAlias was: {2}, its UserName was: {3}, and its Password was: {4}
Problem UserName and/or Password assigned to the Authentication Alias being used by the MDB is not valid.
User response 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.
Problem The given ResourceAdapter could not be found to perform the operation. This may be due to the fact it has already been shut down.
User response 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.
Problem 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.
User response 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}
Problem The given ResourceAdapter could not be found or was not in a started state so the message endpoint could not be deactivated.
User response 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.
Problem 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.
User response Make sure the ResourceAdapter is started.
J2CA0154E: The method {0} on class {1} returned the following exception: {2}
Problem This exception is unexpected. The cause is not immediately known.
User response 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.
Problem The JNDI lookup of the Authentication Alias assign to the ActivationSpec in use by the given MDB did not complete successfully.
User response 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 re-activation failed during a resume operation on a ResourceAdapter. The ActivationSpec was {0}, the MDB Application was {1}, and the exception was: {2}
Problem This exception is unexpected. The cause is not immediately known.
User response See the exception and other log entries for more details.
J2CA0157E: Unable to get the ThreadPoolMgr service.
Problem This exception is unexpected. The cause is not immediately known.
User response 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}.
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
J2CA0159E: Internal error. An attempt has been made to change a set once property that has already been set. The property name is {0}
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
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.
Problem 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.
User response Take appropriate action based on the exception text.
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''s class was: {1}
Problem 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.
User response 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.
Problem You do not need to supply a destination JNDI name.
User response Do not supply a destination JNDI name.
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 ActivationSpec. The destination JNDI name was: {0}. The supplied object''s class was {1}.
Problem 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.
User response 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}.
Problem 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.
User response 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.
Problem The internal data structures have not been initialized for this connection factory. Some MBean operations are not possible in this state.
User response Attempt the intended operation after the connection factory has been accessed.
J2CA0166E: An attempt to share a connection handle across application server components has been detected. The connection handle is: {0}. Returning exception: {1}
Problem It is against the programming model to use a connection handle in a component instance that is different from the component instance which first created the connection. Components consist of Servlets, JSP's, EJB's, MDB's, and ASYNC Beans.
User response Stop making the connection handle available to any component instance other than the one which did the first getConnection call.
J2CA0167E: An attempt to concurrently use the same connection handle by multiple threads has been detected. The connection handle is: {0}. Returning exception: {1}
Problem It is against the programming model to concurrently access a connection handle from multiple threads.
User response Make sure your code does 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.
J2CA0168E: An exception occurred while trying to instantiate a ConnectionFactory class used by resource {0} : {2}.
Problem This message indicates a problem while attempting to create a ConnectionFactory object because it caught an Exception from the ManagedConnectionFactory.
User response Check the exception and contact support for the ResourceAdapter which is throwing the exception.
J2CA0169E: Unable to change the property {0} on DataSource/ConnectionFactory {1}. Please try again later.
Problem This indicates that the connection manager was unable to make the requested change to the configuration variable at this time.
User response Try again.
J2CA0170E: Internal error. The variable {0} on DataSource/ConnectionFactory {1} has gone out of its acceptable range.
Problem This exception is unexpected. The cause is not immediately known.
User response 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/.
J2CA0200E: The J2C runtime was unable to find the class {0}.
Problem The J2C runtime was unable to find the given class.
User response 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}
Problem This is an internal system error and is probably caused by an earlier failure.
User response 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}
Problem This exception is unexpected. The cause is not immediately known.
User response 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}.
Problem 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.
User response Change you configuration such that the two resource adapters are not deployed to the same server.
J2CA0204W: The attempt to stop ResourceAdapter failed during XARecovery cleanup and will be ignored. It was due to the following exception: {0}
Problem An exception occurred while attempting to stop a ResourceAdapter.
User response Take appropriate action based on the exception text.
J2CA0278W: Could not de-serialize field {0} in class {1}; default value will be used
Problem During de-serialization of an object, an expected field was not found. This is most likely due to the fact that the object is being de-serialized by a different version of the class than the one that serialized it.
User response 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.
Problem This exception is unexpected. The cause is not immediately known.
User response 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.
Problem Configuration properties of a Resource Adapter or Activation Spec override their corresponding introspected properties, unless the type does not match.
User response 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.
Problem User-defined properties of a Resource Adapter or Activation Spec override their corresponding introspected and config properties, unless the type does not match.
User response Check the type of the user-defined config property.
J2CA0282W: Required property {0} was missing from activation spec.
Problem Required property {0} was missing from activation spec.
User response Supply a correct {0} property.
J2CA0283E: Attempt to access embedded resource adapter of another application via connection factory {0}.
Problem An application attempted to lookup a connection factory associated with another application's embedded resource adapter.
User response 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.
Problem The property was not found via introspection on the underlying bean.
User response 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}
Problem A call to method getInvalidConnections returned a resource exception.
User response 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.
Problem This connections resource adapter does not support the pretest connection function.
User response 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.
Problem This are either no or more than one ConnectionDefinitions defined. This implies an internal XML formatting error.
User response Make sure there is only a single ConnectionDefinition defined.
J2CA0288I: Configuration property {0} changed from {1} to {2} for pool {3}
Problem A pool properties value has been changed.
User response None.
J2CA0289W: Thread pool {0} has not been defined in the server configuration or is not configured correctly.
Problem 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.
User response Create the missing thread pool or fix the configuration for the thread pool.
J2CA0290W: Thread pool {0} will be used.
Problem The thread pool that was specified for the resource adapter has not been configured.
User response 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.
Problem Application ear file has supplied an non-existed <activation-config-property>.
User response Fix the application descriptor.
J2CA0292E: The ManagedConnection from resource {0} could not be enlisted with the current transaction.
Problem An internal error has occurred while attempting to process the lazyEnlist method.
User response 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}.
Problem Normally this indicates an error with the resource adapter implementation. The resource adapter called lazyEnlist with a null ManagedConnection.
User response 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}
Problem 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.
User response Modify the application to use the preferred J2EE programming model with resource references and the local JNDI java:comp/env context.
J2CA0295E: The Connection Manager has detected an attempt to start a Local Transaction within a Global (User) Transaction. Check the application code for correctness.
Problem Normally this indicates an error in the application. The application should not start Local Transactions when it is operating in a Global Transaction.
User response 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 which may include the line numbers of the code in question - this can help to narrow down the search. If the line numbers are not found (the code has been jit compiled or otherwise obfuscated), you may want to instrument the code with System.out.println() statements to help find the problem area. If the problem cannot be found contact support.
J2CA0300I: ActivationSpec {0} has no configuration properties. The ActivationSpec class is {1} for ResourceAdapter {2}. This may have undesirable effects.
Problem 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.
User response If a value is required please supply one.
J2CA0301E: The Resource Adapter {0} is not configured properly for HA. HA is disabled. Configured HA properties were isEnableHASupport = {1}, and HACapabiliy = {2}.
Problem There was a mismatch between the configured isEnableHASupport boolean and the HACapability. Processing continues with HA disabled.
User response 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}.
Problem Normally this indicates an unsupported setting. HACapability greater than 1 (one) is not supported.
User response Make sure the Resource adapter is configured with HACapability of 0 or 1.
J2CA0303E: Attempting to {0} Resource Adapter {1} while under HA control.
Problem Normally this indicates a suspend/resume operation was attempted while HA is enabled. Only outbound portions of the RA will be suspended or resumed.
User response 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.
Problem 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.
User response If a value is required please supply one.
J2CA0500W: Connection Error Alert for ConnectionFactory or DataSoure {0}. This ConnectionFactory or DataSoure has exceeded {1} connection error events in less then {2} minutes.
Problem If this message is logged it means that the 'connErrorAlert' has been enabled for this ConnectionFactory or DataSource. The configuration has optional parameters for indicating a time interval and a threshold for the alert such that if the number of connection errors observed by the ConnectionFactory or DataSoure during the time interval exceeds the threshold the alert is issued.
User response If you believe that the frequency of connection errors is unexpectedly excessive then you should investigate the root cause of connection errors. The first place to look would be in the error log.
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.
Problem You have configured the monitoring of individual connections for low usage efficiency. Efficiency is measured from the time the connection is gotten to the time it is released for unshareable connections, and the from the time it is gotten to the time the sharing boundary ends (typically the end of a transaction or component method). The usage efficiency is the amount of time the connection is used to interact with the back end divided by the total amount of time the connection has been held (expressed as a percent).
User response If the efficiency is lower than what you expect you should look at your application to determine why.
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.
Problem You have configured the monitoring of your DataSource/ConnectionFactory for low average connection usage efficiency. The usage efficiency is total amount of time the connections are used to interact with the back end divided by the total amount of time the connections have been held average over the number of connections at any point in time in the pool and expressed as a percent.
User response If the efficiency is lower than what you expect you should look at your application to determine why. You may also want to configure the Connection Low Efficiency Alert with callstack capture enabled to further isolate specific application usage which are inefficient.
J2CA0503W: Surge Mode Alert for ConnectionFactory or DataSource {0}. Surge mode has been entered.
Problem DataSources and ConnectionFactories 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 whereby the connection creation rate is governed by the surge configuration parameters.
User response If your ConnectionFactory or DataSoure is spending a lot of time in surge mode you may want to check to see if the configuration parameters are reasonable or if there is some other underlying cause which needs to be investigated.
J2CA0504W: Hung Connection Mode Alert for ConnectionFactory or DataSource {0}. Hung connection blocking has started.
Problem DataSources and ConnectionFactories can be configured to decide if operations to the back end are not responding in a timely manor (they are hung) based on configuration thresholds. Once hung mode has been entered the connection manager will block all requests for new connections until it detects that requests to the back end are responding reasonably again. If the hang detection has been configured and this alert is enabled, this message indicates that you have entered the hung connection blocking state whereby new connection creation is not allowed.
User response If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if the configuration parameters are reasonable or if there is some other underlying with the back end you are trying to communicate with.
J2CA0505W: Pretest Block Mode Alert for ConnectionFactory or DataSource {0}. Connection Pretest function has started connection request blocking.
Problem DataSources and ConnectionFactories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on configuration thresholds. If a connection is not responding the connection manager will block all requests for new connections until it can get a functioning connection. If the pre-testing of connections has been configured and this alert is enabled, this message indicates that you have entered the pretest connection blocking state whereby new connection creation is not allowed.
User response If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if there is an underlying problem with the back end you are trying to communicate with.
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 .
Problem ConnectionFactorys or DataSources can be configured to wait a certain amount of time for a connection to become amiable. If this time is exceeded a ConnectionWaitTimeoutException is issue. This alert can be configure to count the number of ConnectionWaitTimeoutExceptions over a given interval and raise an alert if the threshold is exceeded.
User response Check the documentation for ConnectionWaitTimeoutExceptions for more details.
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 .
Problem When a ConnectionFactory or DataSource has reached its maxConnection limit and a request comes in for a new connection and it has connections available in its free pool but none of these connections match the needed matching criteria of the request, one of these connections will be destroyed (this is the victim) so that a new connection can be created. This alert notifies you if the rate at which this is occurring is exceeding your configured threshold.
User response Excessive claiming of connections is detrimental to performance and may indicate a problem with the whey the application is using connections, however, depending on the usage scenario this may be normal.
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}.
Problem A ConnectionFactory or DataSource has a maximum available load equal to all of its connections in continuous use (this would equal its current maxConnections setting). The pool load at any point in time is the number of connections in use plus any threads waiting for a connection. The average pool load is time averaged value of the pool load over the interval configured by this alert. This alert tells you that you have exceeded that pool average load for the last interval.
User response Excessive load on the pool may be caused by a number of factors: maxConnnections setting is too low; connection percent efficiency is too low thus causing poor connection utilization; demand is outstripping capacity; etc. Investigate and make appropriate changes.
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.
Problem Unexpected nesting of LTC can have an undesirable side affect of tying up more connections then the user expects. This alert can help detect such situations and provide information that will help with pinpointing the problem.
User response For more information consult the documentation.
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.
Problem 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.
User response For more information consult the documentation.
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.
Problem When applications manage the interaction with the back end, having two connections to a single managed connection can cause data integrity problems since no one owner is in charge of the commit or rollback calls. This is not allow. If this is attempted, a second managed connection will be returned. If this is unexpected it may caused data integrity problems. I may also cause unexpected additional connections to be used. This alert can help detect such situations and provide information that will help with pinpointing the problem.
User response For more information consult the documentation on connection sharing rules for LTCs.
J2CA0513W: Surge Mode Alert for ConnectionFactory or DataSource {0}. Surge mode has been exited.
Problem DataSources and ConnectionFactories 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 disabled, this message indicates that you have exited the surge throttling mode whereby the connection creation rate is governed by the surge configuration parameters.
User response If your ConnectionFactory or DataSoure is spending a lot of time in surge mode you may want to check to see if the configuration parameters are reasonable or if there is some other underlying cause which needs to be investigated.
J2CA0514W: Hung Connection Mode Alert for ConnectionFactory or DataSource {0}. Hung connection blocking has ended.
Problem DataSources and ConnectionFactories can be configured to decide if operations to the back end are not responding in a timely manor (they are hung) based on configuration thresholds. Once hung mode has been entered the connection manager will block all requests for new connections until it detects that requests to the back end are responding reasonably again. If the hang detection has been configured and this alert is enabled, this message indicates that you have exited the hung connection blocking state whereby new connection creation is not allowed.
User response If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if the configuration parameters are reasonable or if there is some other underlying with the back end you are trying to communicate with.
J2CA0515W: Pretest Block Mode Alert for ConnectionFactory or DataSource {0}. Connection Pretest function has stopped connection request blocking.
Problem DataSources and ConnectionFactories can be configured to pretest connections for getConnection requests to ensure the health of the connection based on configuration thresholds. If a connection is not responding the connection manager will block all requests for new connections until it can get a functioning connection. If the pre-testing of connections has been configured and this alert is enabled, this message indicates that you have exited the pretest connection blocking state whereby new connection creation is not allowed.
User response If your ConnectionFactory or DataSoure is spending a lot of time in a blocked state you may want to see if there is an underlying problem with the back end you are trying to communicate with.
J2CA0520W: The Message Endpoint activation (the resume operation) failed for ActivationSpec {0} and MDB Application {1} because the Message Endpoint is currently activated or stopped.
Problem Message Endpoints that are activated or stopped cannot be resumed.
User response Modify the application to verify the Message Endpoint is inactive before invoking the resume operation.
J2CA0521E: Acquiring Message Endpoint properties for ActivationSpec {0} and MDB Application {1} failed because the Message Endpoint is currently stopped.
Problem Message Endpoints that are stopped do not have runtime JMS Properties.
User response Modify the application to verify the Message Endpoint is not stopped before invoking the getJMSProperties() method.
J2CA0523I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} is activated.
Problem The Message Endpoint exists and is enabled to handle incoming messages.
User response None.
J2CA0524I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} is deactivated.
Problem The Message Endpoint exists and is disabled from handling incoming messages.
User response None.
J2CA0525I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} is stopped and its MBean is unusable.
Problem Message Endpoints stop (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.
User response Restart the application hosting the Message Endpoint and obtain a new MBean reference in order to control the Message Endpoint.
J2CA0526I: The Message Endpoint for ActivationSpec {0} and MDB Application {1} cannot be activated because inbound messaging on Resource Adapter {2} is currently disabled by the High_Availability (HA) Manager.
Problem The HA Manager controls the activation of inbound messaging for Resource Adapters having enabled HA Capabilities. The Message Endpoints may be paused and resumed after the HA Manager activates inbound messaging on the Resource Adapter.
User response Avoid pausing or resuming Message Endpoints that are not yet activated by the HA Manager.
J2CA1002E: Invalid MCWrapper {0} from the free pool for resource {1}.
Problem The attempt to reserve an MCWrapper failed.
User response 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.
Problem The attempt to remove an MCWrapper failed, causing a potential problem in the shared pool.
User response 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: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.j2c.resources.J2CAMessages.html

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