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 specified 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The connection factory returned from the JCA runtime did not implement SICoreConnectionFactory as expected. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 JCA connection manager a connection of an unexpected type was returned. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 because 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The current connection has been dissociated from its managed connection and the exception was received while attempting to re-associate. |
Action | See the linked exception for further information. |
Explanation | A previous error has caused the connection to be no longer valid. |
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 an exception was received. |
Action | See the linked exception for further information. |
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 because 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 exception was created while attempting to commit it. |
Action | See the linked exception for further information. |
Explanation | The container has detected an outstanding application local transaction at the end of a sharing scope and an exception was created while attempting to roll it back. |
Action | See the linked exception for further information. |
Explanation | A previous error has caused the connection to be no longer valid. |
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 exception was received while attempting to create a connection to the messaging engine. |
Action | See the linked exception for further information. |
Explanation | An exception was created while attempting to create a core SPI connection factory using the factory type TRM_CONNECTION. |
Action | See the linked exception for further information. |
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 because 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An exception was created while attempting to clone a connection to the messaging engine during the creation of a managed connection. |
Action | See the linked exception for further information. |
Explanation | The object passed as the connection request information parameter was not of the expected type. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An exception was created while attempting to create a managed connection. |
Action | See the linked exception for further information. |
Explanation | An error has been caught whilst obtaining a connection. The system will purge the connection then attempt to obtain another one. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The object passed as the connection request information parameter was not of the expected type. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An exception was created while attempting to close a connection to the messaging engine. |
Action | See the linked exception for further information. |
Explanation | The object passed as the connection parameter was not of the type expected by this resource adapter. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The container is attempting to begin a local transaction when there is already one active. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An exception was created while the container was attempting to begin a local transaction. |
Action | See the linked exception for further information. |
Explanation | An exception was created while the container was attempting to commit a local transaction. |
Action | See the linked exception for further information. |
Explanation | An exception was created while the container was attempting to roll back a local transaction. |
Action | See the linked exception for further information. |
Explanation | An exception was created while attempting to obtain an SIXAResource. |
Action | See the linked exception for further information. |
Explanation | The activation specification passed on endpoint activation was not of the type expected by the resource adapter. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 the values for the given properties in the administered activation specification, or in the message-driven bean's activation configuration, 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | During validation of the properties configured on a Core SPI activation specification the bus name was found not to be valid. |
Action | Correct the value of the bus name property on the activation specification then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the destination type was found not to be valid. |
Action | Correct the value of the destination type property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the share durable subscription was found not to be valid |
Action | Correct the value of the share durable subscription property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the durable subscription home was found not to be valid |
Action | Correct the value of the durable subscription home property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the destination type was found not to be valid. Since no destination name is supplied Topics are not permitted |
Action | Correct the value of the destination type property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the maximum batch size was found not to be valid |
Action | Correct the value of the maximum batch size property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the deletion mode was found not to be valid |
Action | Correct the value of the deletion mode property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the maximum concurrency was found not to be valid. |
Action | Correct the value of the maximum concurrency property on the activation specification then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the target type was found not to be valid. |
Action | Correct the value of the target type property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification the target significance was found not to be valid |
Action | Correct the value of the target significance property on the activation specification then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification, the provider endpoint was found not to be valid because the use server subject property is set. |
Action | Please ensure that provider endpoints property is not set if use server subject is set. Correct the value of the property on the activation specification, then restart the server. |
Explanation | During validation of the properties configured on a Core SPI activation specification, the "use destination wildcard" was found not to be valid because a Topic Space is being used. |
Action | Ensure that "use destination wildcard" property is not set when using a Topic Space. Correct the value of the property on the activation specification, then restart the server. |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The configuration of the maximum concurrency on the activation specification was set to high or the maximum concurrency on the JCA's maximum pool size was set too low. This should not cause a problem because Platform Messaging will lower the maximum concurrency on the activation specification but a warning is issued to the user to let the user know that the maximum concurrency they have configured will not be used. |
Action | This warning will continue to be shown whenever the message-driven bean is started. To remove this warning message lower the activation specifications maximum concurrency or raise the maximum pool size of the JCA's endpoint pool (using the JVM system property com.ibm.websphere.ejbcontainer.poolSize) |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 associated with a valid authentication alias. |
Action | See the linked exception for further information. After resolving issue, restart messaging engine, resource adapter or application. |
Explanation | The resource adapter received an exception when attempting to unlock a set of messages. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter received an exception when attempting to delete a message under the given transaction. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter received an exception when attempting to delete messages under the given transaction. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter received an exception when attempting to obtain the request metrics instance. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The System has determined that there is a possible problem with the MDB associated with the message endpoint. |
Action | Investigate possible problems with the MDB that could cause sequential failures. The message endpoint can be deactivated to stop further errors occurring, use the Message Endpoint MBean passing the endpoint name in this message to deactivate the endpoint or stop the application that contains the Message Driven Bean. |
Explanation | The resource adapter encountered a problem while attempting to delete a message handle |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter encountered a problem while attempting to delete a message handle |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter encountered a problem while attempting to delete a message handle |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter received an exception when attempting to invoke beforeDelivery on an endpoint prior to calling onMessage. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | To permit the recovery of transactions it is necessary that a connection factory target a specific messaging engine in the bus. |
Action | Change the connection factory properties 'targetGroup' to 'the name of a messaging engine in the bus', 'targetType' to 'ME' and 'targetSignificance' to 'Required'. |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The given method cannot be invoked on the session passed to the onMessage method of a Platform Messaging core SPI message-driven bean. |
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 message-driven bean cannot be used once the method has completed. |
Action | Remove the offending call and, if required, create a separate Platform Messaging core SPI session. |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A message-driven bean must be connected to the bus that hosts the destination from which the bean consumes. 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, type or both. |
Explanation | The given destination was not a local, a foreign or an alias destination. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A message-driven bean was configured to connect to the given bus but there are no suitable active messaging engines within the local server. Message consumption will begin when a suitable local messaging engine becomes active. |
Action | Ensure that a suitable messaging engine is started. A message is 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 action is 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 the linked exception for further information. 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 that 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 action is 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 | When processing the updated configuration for the given messaging engine an exception was received. Messages for the queue point on that messaging engine cannot 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 can 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 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 messaging engine for the given endpoint activation. |
Action | No 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 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 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 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 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 given endpoint activation was using a messaging engine that has now been stopped. The resource adapter will attempt to connect to a different messaging engine. |
Action | No action is required. |
Explanation | The inbound resource adapter received notification that the 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 notification that the 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 system failed to connect to a messaging engine when given a set of target information. This may be a temporary connection problem if no messaging engine that matches the target data is available or this may be a configuration issue with the activation specification being used. |
Action | Ensure that a messaging engine on the given bus that matches the supplied target information is available. The resource adapter automatically attempts to connect to the bus periodically. If the messaging engine is available then check the activation config settings are correct, particularly the busname and the target information. |
Explanation | The system failed to connect to a messaging engine. This may be a temporary connection problem if no messaging engine is available in the bus or this may be a configuration issue with the activation specification being used. |
Action | Ensure that a messaging engine on the given bus is available. The resource adapter automatically attempts to connect to the bus periodically. If the messaging engine is available then check the activation config settings are correct, particularly the busname. |
Explanation | The system failed to connect to the messaging engine that hosts the durable subscription home. This may be a temporary connection problem if the messaging engine is unavailable in the bus or this may be a configuration issue with the activation specification being used. |
Action | Ensure that the messaging engine that host the durable subscription home on the given bus is available. The resource adapter automatically attempts to connect to the bus periodically. If the messaging engine is available then check the activation config settings are correct, particularly the busname and durable subscription home |
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 the linked exception for further information. After resolving issue, restart messaging engine, resource adapter or application. |
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 the linked exception for further information. After resolving issue, restart messaging engine, resource adapter or application. |
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, resource adapter or application. |
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, resource adapter or application. |
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 session was dropped for the reason stated in the exception. This might be because the specified destination has been deleted or marked as send-only. The corresponding message-driven bean will be deactivated and will receive no further messages. |
Action | If this warning was not expected, resolve the issue then restart the application, resource adapter or messaging engine as appropriate. |
Explanation | The activation specification contains a wildcard destination name in order to consume messages from multiple destinations, however the wildcard name matches zero available destinations |
Action | Ensure that the activation specification should be using wildcarding destination name, that the destination wildcarded name will match some destinations and that the specifed user details are allowed to consume from the destinations. |
Explanation | The message endpoint factory has returned a message endpoint that does not implement the SibRaMessageListener interface as expected. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An exception was created during the attempt to obtain an instance of the onMessage method. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An exception was created whilst the inbound resource adapter was attempting to create a listener for the given destination. |
Action | See the linked exception for further information. Resolve the issue then restart the application, resource adapter or messaging engine as appropriate. |
Explanation | An exception was created during the attempt to obtain an instance of the SelectionCriteriaFactory. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The system paused the message endpoint because it detected a problem with the message-driven bean's message endpoint. |
Action | Investigate possible problems with the message-driven bean that could cause sequential errors. When you are ready to resume the message endpoint, use the administrative console. Alternatively, use the message endpoint MBean to resume the endpoint, passing to it the endpoint name in this message. |
Explanation | The system detected a problem with a message endpoint's message-driven bean but the attempt to pause the message endpoint failed. |
Action | Check the status of the message endpoint using wsadmin scripting or the administrative console. If the message endpoint is active, pause the endpoint and investigate possible problems with the message-driven bean. Resume the endpoint when you are ready. |
Explanation | The system cannot locate a message endpoint. |
Action | Check the status of the message endpoint using wsadmin scripting or the administrative console. If the message endpoint is active, pause the endpoint and investigate possible problems with the message-driven bean. Resume the endpoint when you are ready. |
Explanation | The system detected multiple message endpoints. It was unable to identify which message endpoint to pause. |
Action | Check the status of all the message endpoints on this message-driven bean using wsadmin scripting or the administrative console. If a message endpoint is active, pause the endpoint and investigate possible problems with the message-driven bean. Resume the endpoint when you are ready. |
Explanation | The maximum sequential message failure value has changed because strict message ordering has been turned on. |
Action | No action is necessary unless you require the sequential message failure function. If you require the sequential message failure function, turn off strict message ordering. |
Explanation | The maximum sequential message failure value has changed because no exception destination is defined for the destination on which the message-driven bean is listening. |
Action | No action is necessary unless you require the sequential message failure function. If you require the sequential message failure function, configure an exception destination for the destination. |
Explanation | The inbound resource adapter was attempting to create a connection when an unexpected exception was received. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The inbound resource adapter was attempting to create a connection when an unexpected exception was received. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The messaging engine connection received a request to create a listener but has already been closed. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The messaging engine connection received a request to create a dispatcher but has already been closed. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The inbound resource adapter was attempting to create a connection when an authentication exception was received. |
Action | Ensure that the correct user name and password are supplied on the ActivationSpec that the message-driven bean is configured to use |
Explanation | The inbound resource adapter was attempting to create a connection when an authentication exception was received. |
Action | Ensure that the correct user name and password are supplied on the ActivationSpec that the message-driven bean is configured to use |
Explanation | The inbound resource adapter was attempting to create a connection using the server subject, but couldn't get the subject. |
Action | Check Application Server security settings are configured correctly. |
Explanation | The inbound resource adapter was attempting to create a connection when an authorization exception was received. |
Action | Ensure that a correct authentication alias is setup on the activation specification that the message-driven bean is configured to use. |
Explanation | The inbound resource adapter was attempting to create a connection when an authorization exception was received. |
Action | Check that the authentication alias on the activation specification, that the message-driven bean is configured to use, is authorized to connect to the messaging engine. |
Explanation | The inbound resource adapter was attempting to create a connection when an authorization exception was received. |
Action | Ensure that a correct authentication alias is setup on the activation specification that the message-driven bean is configured to use. |
Explanation | The inbound resource adapter was attempting to create a connection when an authorization exception was received. |
Action | Check that the authentication alias on the activation specification, that the message-driven bean is configured to use, is authorized to connect to bus. |
Explanation | The inbound resource adapter requires the message endpoint factory to implement the given interface in order to obtain the unique name of the message-driven bean. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The inbound resource adapter dispatch target received a request object that was not of the expected type. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The inbound resource adapter was unable 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 could not get an endpoint activation from the pool because it could not locate the pool |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The maximum concurrency value has changed because strict message ordering has been turned on. |
Action | No action is required unless concurrent message-driven beans are required. If so then turn off strict message ordering. |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The inbound resource adapter requires the message endpoint factory to implement the given interface in order to obtain the unique name of the message-driven bean. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The inbound resource adapter could not find the server so the property MessageLockExpiry was assigned a default value. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | When reading the value for MessageLockExpiry it was unable to convert the value to an integer. |
Action | Check the value assigned to the custom property MessageLockExpiry is an integer, restart the server for the changes to take effect. |
Explanation | Negative values are not allowed for the message lock expiry time |
Action | Check the value assigned to the custom property MessageLockExpiry is either positive or zero, then restart the server for the changes to take effect. |
Explanation | The resource adapter received an exception when attempting to invoke beforeDelivery on an endpoint prior to calling onMessage. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter received an exception when attempting to create an uncoordinated transaction on the given connection. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The resource adapter received an exception when attempting to register the given synchronization with the transaction manager. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 system is correctly configured in order to take advantage of the one-phase commit optimization between a messaging engine and a database when also using entity beans that use container managed persistence. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | If the message does not give sufficient information, see the accompanying error messages for further information. |
Action | See the accompanying error messages for further information. |