Explanation | A security alias was specified on the resource for which recovery processing is taking place and could not be resolved. Processing will continue with a null user name and password. |
Action | Ensure that the failing alias is defined for the application server in which recovery processing is taking place. |
Explanation | While attempting to obtain an SICoreConnectionFactory through the JCA runtime, an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The connection factory returned from the JCA runtime did not implement SICoreConnectionFactory as expected. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The property map passed to the getConnectionFactory method on SICoreConnectionFactorySelector contained an incorrect value for the given property. |
Action | Ensure that the set of properties passed to the getConnectionFactory method on SICoreConnectionFactorySelector is valid. |
Explanation | The property map passed to the getConnectionFactory method on SICoreConnectionFactorySelector contained a value for the given property that was not of the required type. |
Action | Ensure that the set of properties passed to the getConnectionFactory method on SICoreConnectionFactorySelector is valid. |
Explanation | The property map passed to the getConnectionFactory method on SICoreConnectionFactorySelector requested that the container provide credentials using the default principal mapping but did not specify a container authentication alias. |
Action | Ensure that the set of properties passed to the getConnectionFactory method on SICoreConnectionFactorySelector contains a value for CONTAINER_AUTHENTICATION_ALIAS. |
Explanation | The property map passed to the getConnectionFactory method on SICoreConnectionFactorySelector contained an incorrect value for the given property. |
Action | Ensure that the set of properties passed to the getConnectionFactory method on SICoreConnectionFactorySelector is valid. |
Explanation | While attempting to obtain a connection through the connection manager an exception was received. |
Action | See linked exception for cause. |
Explanation | While attempting to obtain a connection through the JCA connection manager a connection of an unexpected type was returned. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An attempt has been made to create a new SIUncoordinatedTransaction when the current one has not been completed. |
Action | Ensure commit or rollback is called on the current SIUncoordinatedTransaction before creating a new one. |
Explanation | An attempt has been made to create a new SIUncoordinatedTransaction while there is a container-managed transaction on the thread. |
Action | Modify the application so that the call is made in an environment where there is no container-managed transaction on the thread. |
Explanation | The creation of an SIXAResource is not supported when using the RA_CONNECTION implementation of the Platform Messaging core SPI as global transactions are handled by the resource adapter. |
Action | If the application must handle global transactions explicitly then use a different implementation of the Platform Messaging core SPI, otherwise remove the call to getSIXAResource. |
Explanation | The cloning of a connection is not supported when using the RA_CONNECTION implementation of the core SPI. |
Action | Consider whether cloning of a connection is required or whether simply creating another connection would suffice. |
Explanation | The current connection has been dissociated from its managed connection but the connection manager does not support lazy enlistment for the re-association to take place. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The current connection has been dissociated from its managed connection and an error occurred while attempting to re-associate. |
Action | See linked exception for cause. |
Explanation | A previous error has caused the connection to be invalidated. |
Action | Check error logs to determine cause of previous error. The application should create a new connection. |
Explanation | While attempting to obtain the current container transaction the connection an error occurred. |
Action | See linked exception for cause. |
Explanation | An attempt has been made to use a transaction parameter of null when there is still an active SIUncoordinatedTransaction associated with this connection. |
Action | Either pass the active SIUncoordinatedTransaction as the transaction parameter or call commit/rollback on it first before passing null. |
Explanation | An attempt has been made to use an SIUncoordinatedTransaction as the transaction parameter when there is a different active SIUncoordinatedTransaction associated with this connection. |
Action | Ensure that the application is passing the current active SIUncoordinatedTransaction associated with the connection or null if the operation should be performed outside of the transaction. |
Explanation | The use of an SIXAResource as the transaction parameter is not supported when using the RA_CONNECTION implementation of the Platform Messaging core SPI as global transactions are handled by the resource adapter. |
Action | If the application must handle global transactions explicitly then use a different implementation of the Platform Messaging core SPI, otherwise pass null as the transaction parameter. |
Explanation | The object passed as the transaction parameter was not of a recognized type. |
Action | Ensure that the transaction parameter is either null, an SIUncoordinatedTransaction obtained from this connection or an SibRaAutoCommitTransaction. |
Explanation | The container has detected an outstanding application local transaction at the end of a sharing scope and an error has occurred while attempting to commit it. |
Action | See linked exception for cause. |
Explanation | The container has detected an outstanding application local transaction at the end of a sharing scope and an error has occurred while attempting to roll it back. |
Action | See linked exception for cause. |
Explanation | The use of ConsumerSession methods relating to the asynchronous receipt of messages are not supported when using the RA_CONNECTION implementation of the Platform Messaging core SPI. |
Action | If asynchronous receipt of messages is required, use a different implementation of the Platform Messaging core SPI. |
Explanation | A previous error has caused the connection to be invalidated. |
Action | Check error logs to determine cause of previous error. The application should create a new connection and session. |
Explanation | The use of ConsumerSession methods relating to the asynchronous receipt of messages are not supported when using the RA_CONNECTION implementation of the Platform Messaging core SPI. |
Action | If asynchronous receipt of messages is required, use a different implementation of the Platform Messaging core SPI. |
Explanation | An error occurred while attempting to create a connection to the messaging engine. |
Action | See linked exception for cause. |
Explanation | An error occurred while attempting to create a core SPI connection factory using the factory type TRM_CONNECTION. |
Action | See linked exception for cause. |
Explanation | The creation of a connection factory is not supported in a non-managed environment when using the RA_CONNECTION implementation of the core SPI as a connection manager is required to provide container transaction support. |
Action | In a non-managed environment create a connection factory using the SICoreConnectionFactorySelector with a FactoryType other than RA_CONNECTION. |
Explanation | The connection manager has attempted to create a managed connection without specifying any connection request information. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while attempting to clone a connection to the messaging engine during the creation of a managed connection. |
Action | See linked exception for cause. |
Explanation | The object passed as the connection request information parameter was not of the expected type. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while attempting to create a managed connection. |
Action | See linked exception for cause. |
Explanation | An error has been caught whilst obtaining a connection. The system will purge the connection and attempt to obtain another one. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while attempting to clone a connection to the messaging engine. |
Action | See linked exception for cause. |
Explanation | The object passed as the connection request information parameter was not of the expected type. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while attempting to close a connection to the messaging engine. |
Action | See linked exception for cause. |
Explanation | The object passed as the connection parameter was not of the type expected by this resource adapter. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The container is attempting to begin a local transaction when there is already one active. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An error occurred while the container was attempting to begin a local transaction. |
Action | See linked exception for cause. |
Explanation | An error occurred while the container was attempting to commit a local transaction. |
Action | See linked exception for cause. |
Explanation | An error occurred while the container was attempting to roll back a local transaction. |
Action | See linked exception for cause. |
Explanation | An error occurred while attempting to obtain an SIXAResource. |
Action | See linked exception for cause. |
Explanation | The activation specification passed on endpoint activation was not of the type expected by the resource adapter. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | During the activation of an endpoint the given activation specification was determined to be incorrect. |
Action | See linked exception for incorrect properties and correct values in administered activation specification or message-driven bean's deployment descriptor. |
Explanation | During validation of the given activation specification one or more properties were determined to be incorrect. |
Action | Correct values for given properties in administered activation specification or message-driven bean's activation-config properties then start the application. |
Explanation | During endpoint activation the core SPI resource adapter was attempting to obtain an SIDestinationAddressFactory and an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | During the registration of the WLM classifier for the core SPI resource adapter with the handler registry an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The endpoint activation received an exception from the message endpoint factory indicating that there is no onMessage for this endpoint when trying to determine its transactionality. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A request was made for a connection to the given messaging engine but the endpoint activation has been deactivated. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter was attempting to process the given messaging engine when it received an exception. Messages from destinations localized on that messaging engine will not be received by the message-driven bean. If the linked exception is an authentication exception then ensure that the activation specification has been assocaited with a valid authentication alias. |
Action | See linked exception for cause. After resolving issue, restart messaging engine or resource adapter. |
Explanation | The message endpoint factory has returned a message endpoint that does not implement the SibRaMessageListener interface as expected. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to unlock a set of messages. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to delete a message under the given transaction. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to delete messages under the given transaction. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to obtain the request metrics instance. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to obtain the XAResource from a connection in order to pass it on endpoint creation. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to invoke beforeDelivery on an endpoint prior to calling onMessage. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The XAResource has not been enlisted after calling beforeDelivery despite the message endpoint factory indicating that the onMessage method is transacted. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to clone a connection that would be returned from getConnection on the session to be passed to the endpoint. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The given method may not be invoked on the session passed to the onMessage method of a Platform Messaging core SPI MDB. |
Action | Remove the offending call and, if required, create a separate Platform Messaging core SPI session. |
Explanation | The session passed to the onMessage method of a Platform Messaging core SPI MDB may not be used once the method has completed. |
Action | Remove the offending call and, if required, create a separate Platform Messaging core SPI session. |
Explanation | A message-driven bean using the default messaging provider may only connect to messaging engines running in the same server of which there are none enabled. |
Action | Check that the message-driven bean is configured with the correct bus name, that the SIB service is enabled for this server and that this server or its cluster is a member of the bus. |
Explanation | An unexpected exception was received when attempting to determine the set of messaging engines with queue points for the given destination. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A message-driven bean must be connected to the bus on which the destination from which it consumes resides. Foreign buses are not supported. |
Action | Modify the activation specification for the message-driven bean so that it connects to the required bus or move the destination to the bus to which the message-driven bean is connecting. |
Explanation | The destination type defined on the message-driven bean's activation specification does not match the type of the configured destination. |
Action | Check that the message-driven bean's activation specification is configured with the correct destination and/or type. |
Explanation | The given destination was not a local, a foreign or an alias destination. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The destination configured on the message-driven bean does not exist in the given bus. |
Action | Check the definition of the destination on the message-driven bean's activation specification or bindings. |
Explanation | An unexpected exception was received when attempting to obtain the definition of the given destination. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A message-driven bean was configured to connect to the given bus but there were no suitable active messaging engines within the local server. Message consumption will begin when a suitable local messaging engine becomes active. |
Action | Ensure that either a suitable messaging engine is in the process of starting in which case a message will be displayed when a successful connection is made. |
Explanation | The activation of a messaging engine on the required bus has led to the creation of a new consumer for the given destination. |
Action | No user action required. |
Explanation | During the stopping of the given messaging engine the resource adapter received an exception when attempting to connect to an alternative messaging engine. |
Action | See linked exception for cause. After resolving issue, restart messaging engine or resource adapter. |
Explanation | An asynchronous exception was received for the given consumer. The corresponding message-driven bean will be deactivated and will receive no further messages. |
Action | See exception for cause. After resolving issue, restart messaging engine, resource adapter or application. |
Explanation | An exception was received for the given connection. The corresponding message-driven bean will be deactivated and will receive no further messages. |
Action | See exception for cause. After resolving issue, restart messaging engine, resource adapter or application. |
Explanation | The given endpoint activation was using a messaging engine which has now been stopped. There are no other active messaging engines to connect to. The associated message-driven bean will start to receive messages again when a suitable messaging engine becomes available. |
Action | No user action required. |
Explanation | The inbound resource adapter successfully connected to a local messaging engine but then received an exception when attempting to create a consumer on a remote queue point. |
Action | Ensure that a messaging engine with a queue point for the given destination is available. The resource adapter will automatically re-attempt the creation of the consumer periodically. |
Explanation | The inbound resource adapter received an exception for an existing consumer on a remote queue point. |
Action | Ensure that a messaging engine with a queue point for the given destination is available. The resource adapter will automatically re-attempt to recreate the consumer periodically. |
Explanation | The inbound resource adapter has now successfully created a consumer for the given remote destination. |
Action | No user action required. |
Explanation | A message-driven bean using the default messaging provider may only connect to messaging engines running in the same server and, following a configuration update, there are no longer any messaging engines defined. No more messages will be received for that destination. |
Action | If the message-driven bean is no longer required, then uninstall the corresponding application. Otherwise, update the configuration again so that there is once again a messaging engine defined on the same server and then restart the application. |
Explanation | When processing the updated configuration for the given messaging engine an exception was received. Messages for the queue point on that messaging engine may not be received by the corresponding message-driven bean. |
Action | See the exception for the cause. After resolving the issue, restart the messaging engine, resource adapter, or application. |
Explanation | The given exception was received for a consumer while the corresponding messaging engine was reloading its configuration. |
Action | This warning may be ignored if the queue point to which the consumer was attached has deliberately been deleted as part of the configuration updates. If a replacement queue point has been defined, then a new consumer will be created when the update has completed. |
Explanation | The inbound resource adapter received an exception when attempting to connect to a remote messaging engine. |
Action | Ensure that a messaging engine on the given bus is available. The resource adapter automatically attempts to connect to the bus periodically. |
Explanation | The inbound resource adapter received an exception for an existing connection to a remote messaging engine. |
Action | Ensure that a messaging engine on the given bus is available. The resource adapter automatically attempts to connect to the bus periodically. |
Explanation | The inbound resource adapter successfully created a connection to a remote messaging engine for the given endpoint activation. |
Action | No user action is required. |
Explanation | The given endpoint activation was connecting remotely because no local messaging engines were enabled. All remote connections are now closed. When the local messaging engine is active, a new connection is attempted. |
Action | No user action is required. |
Explanation | The given endpoint activation was connecting locally, but no remaining local messaging engines are enabled. The resource adapter is attempting to connect to a remote messaging engine. |
Action | No user action is required. |
Explanation | The inbound resource adapter received notification that the remote messaging engine to which it was connected has terminated. |
Action | Ensure that a messaging engine on the given bus is available. The resource adapter automatically attempts to connect to the bus periodically. |
Explanation | The inbound resource adapter received notification that the remote messaging engine to which it was connected is quiescing and has disconnected. |
Action | Ensure that a messaging engine on the given bus is available. The resource adapter automatically attempts to connect to the bus periodically. |
Explanation | The inbound resource adapter received an exception when connecting to a remote messaging engine. |
Action | Ensure that a messaging engine on the given bus is available. |
Explanation | The inbound resource adapter received an exception when attempting to connect to a remote messaging engine. The corresponding message-driven bean is deactivating and cannot receive further messages. |
Action | See the exception to determine the cause. After resolving the issue, restart the resource adapter or application. |
Explanation | The inbound core SPI resource adapter was attempting to create a connection for the given messaging engine when it received an exception. Messages from destinations localized on that messaging engine will not be received by the message-driven bean. |
Action | See linked exception for cause. After resolving issue, restart messaging engine or resource adapter. |
Explanation | The inbound resource adapter was attempting to create a consumer for the given destination when it received an exception. Messages from that destination localization will not be received by the message-driven bean. |
Action | See linked exception for cause. After resolving issue, restart messaging engine or resource adapter. |
Explanation | The inbound resource adapter was attempting to add a destination listener for the given messaging engine when it received an exception. Messages from queue points on that messaging engine will not be received by the message-driven bean. |
Action | See the linked exception for the cause. After resolving the issue, restart the messaging engine or resource adapter. |
Explanation | The inbound resource adapter was attempting to create a consumer for the given new destination when it received an exception. Messages from that queue point will not be received by the message-driven bean. |
Action | See the linked exception for the cause. After resolving the issue, restart the messaging engine or resource adapter. |
Explanation | An asynchronous exception was received for the given consumer. The corresponding message-driven bean will be deactivated and will receive no further messages. |
Action | See exception for cause. After resolving issue, restart messaging engine, resource adapter or application. |
Explanation | An exception was received for the given connection. The corresponding message-driven bean will be deactivated and will receive no further messages. |
Action | See exception for cause. After resolving issue, restart messaging engine, resource adapter or application. |
Explanation | The message endpoint factory has returned a message endpoint that does not implement the SibRaMessageListener interface as expected. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An exception was thrown during the attempt to obtain an instance of the onMessage method. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | An exception was thrown whilst the inbound resource adapter was attempting to create a listener for the given destination. |
Action | See linked exception for cause. After resolving issue, restart messaging engine, resoure adapter or application. |
Explanation | An exception was thrown during the attempt to obtain an instance of the SelectionCriteriaFactory. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter was attempting to create a connection when an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter was attempting to create a connection when an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The messging engine connection received a request to create a listener but has already been closed. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The messging engine connection received a request to create a dispatcher but has already been closed. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter was attempting to create a connection when an authentication exception was received. |
Action | Please ensure that the correct username and password are supplied on the ActivationSpec that the MDB is configured to use |
Explanation | The inbound resource adapter was attempting to create a connection when an authentication exception was received. |
Action | Please ensure that the correct username and password are supplied on the ActivationSpec that the MDB is configured to use |
Explanation | The inbound resource adapter requires the message endpoint factory to implement the given interface in order to obtain the J2EE name of the message-driven bean. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter dispatch target received a request object that was not of the expected type. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter dispatch target did not receive back a single message in exchange for the given message handle. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter failed to process the given message handle received from the control region adjunct. |
Action | See exception details for cause. Message delivery will be reattempted once the message lock has expired. |
Explanation | The inbound resource adapter failed to obtain an endpoint activation from the pool since it could not locate the pool |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter was attempting to retrieve the messages from an enumeration when an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter was attempting to retrieve the messages from an enumeration when an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter was attempting to obtain the identifier for a session when an unexpected exception was received. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter requires the message endpoint factory to implement the given interface in order to obtain the J2EE name of the message-driven bean. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter failed to deliver the given message and the subsequent attempt to unlock it failed with the given exception. The message lock will eventually expire and the message will be redelivered. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to invoke beforeDelivery on an endpoint prior to calling onMessage. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to create an uncoordinated transaction on the given connection. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The resource adapter received an exception when attempting to register the given synchronization with the transaction manager. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The inbound resource adapter requires the uncoordinated transaction to implement the given interface in order to perform the one-phase commit optimization. |
Action | Ensure that the configuration is as documented in the InfoCenter for the one-phase commit optimization and, in particular, that a local messaging engine is available for the resource adapter to connect to. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |