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


CWSIV

CWSIV0001W: Failed to resolve the security alias {0} during recovery processing.
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.
CWSIV0050E: An internal error occurred. The exception {0} was received from the JCA runtime while attempting to obtain a connection factory.
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/.
CWSIV0051E: An internal error occurred. The connection factory returned from the JCA runtime {0} does not implement SICoreConnectionFactory.
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/.
CWSIV0052E: The value {0} is not valid for the connection factory property {1}. Valid values are {2} and {3}.
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.
CWSIV0053E: The connection factory property {0} is not of the required type {1}.
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.
CWSIV0054E: Connection factory properties must contain a value for CONTAINER_AUTHENTICATION_ALIAS.
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.
CWSIV0055E: The value {0} is not valid for the connection factory property {1}. Valid values are {2} and {3}.
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.
CWSIV0100E: An exception was received from the connection manager while attempting to obtain a connection.
Explanation While attempting to obtain a connection through the connection manager an exception was received.
Action See linked exception for cause.
CWSIV0101E: An internal error occurred. The JCA connection manager returned a connection {0} that was not of the expected type {1}.
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/.
CWSIV0150E: An existing SIUncoordinatedTransaction has not been completed.
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.
CWSIV0151E: There is a container-managed transaction on the thread.
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.
CWSIV0152E: The creation of an SIXAResource is not supported.
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.
CWSIV0153E: The cloning of a connection is not supported.
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.
CWSIV0154E: An internal error occurred. The connection manager {0} does not support lazy enlistment.
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/.
CWSIV0155E: An internal error occurred. The exception {0} was thrown while attempting to re-associate with a managed connection.
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.
CWSIV0156E: The connection has been invalidated.
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.
CWSIV0157E: An internal error occurred. The exception {0} was thrown while attempt to obtain the current container transaction.
Explanation While attempting to obtain the current container transaction the connection an error occurred.
Action See linked exception for cause.
CWSIV0158E: There is an active SIUncoordinatedTransaction associated with this connection.
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.
CWSIV0159E: The active SIUncoordinatedTransaction associated with this connection was not passed.
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.
CWSIV0160E: An SIXAResource is not a valid transaction parameter.
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.
CWSIV0161E: The transaction parameter {0} was not of a recognized type.
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.
CWSIV0162E: An internal error occurred. The exception {0} was thrown while the container was attempting to commit an application local transaction.
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.
CWSIV0163E: An internal error occurred. The exception {0} was thrown while the container was attempting to roll back an application local transaction.
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.
CWSIV0164E: Methods relating to asynchronous message receipt are not supported.
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.
CWSIV0200E: The connection from which this session was created has been invalidated.
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.
CWSIV0250E: Methods relating to asynchronous message receipt are not supported.
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.
CWSIV0300E: An internal error occurred. The exception {0} was thrown while attempting to create a connection to the messaging engine.
Explanation An error occurred while attempting to create a connection to the messaging engine.
Action See linked exception for cause.
CWSIV0350E: An internal error occurred. The exception {0} was thrown while attempting to create a core SPI connection factory.
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.
CWSIV0351E: Creation of a connection factory in a non-managed environment is not supported.
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.
CWSIV0352E: An internal error occurred. Connection request information is required to create a managed 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/.
CWSIV0353E: An internal error occurred. The exception {0} was thrown while attempting to clone a connection to the messaging engine.
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.
CWSIV0354E: An internal error occurred. The connection request information object {0} was not of the expected type {1}.
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/.
CWSIV0355E: An internal error occurred. Whilst creating the managed connection the following exception was thrown: {0}
Explanation An error occurred while attempting to create a managed connection.
Action See linked exception for cause.
CWSIV0356W: The following JCA Connection error has occurred when trying to get the connetion. The retrieving of the connection will be retried. The exception is {0}.
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/.
CWSIV0400E: An internal error occurred. The exception {0} was thrown while attempting to clone a connection to the messaging engine.
Explanation An error occurred while attempting to clone a connection to the messaging engine.
Action See linked exception for cause.
CWSIV0401E: An internal error occurred. The connection request information object {0} was not of the expected type {1}.
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/.
CWSIV0402E: An internal error occurred. The exception {0} was thrown while attempting to close a connection to the messaging engine.
Explanation An error occurred while attempting to close a connection to the messaging engine.
Action See linked exception for cause.
CWSIV0403E: An internal error occurred. The connection object {0} was not of the expected type {1}.
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/.
CWSIV0404E: An internal error occurred. There is already an active container local transaction.
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/.
CWSIV0405E: An internal error occurred. The exception {0} was thrown while the container was attempting to begin a local transaction.
Explanation An error occurred while the container was attempting to begin a local transaction.
Action See linked exception for cause.
CWSIV0406E: An internal error occurred. The exception {0} was thrown while the container was attempting to commit a local transaction.
Explanation An error occurred while the container was attempting to commit a local transaction.
Action See linked exception for cause.
CWSIV0407E: An internal error occurred. The exception {0} was thrown while the container was attempting to roll back a local transaction.
Explanation An error occurred while the container was attempting to roll back a local transaction.
Action See linked exception for cause.
CWSIV0408E: An internal error occurred. The exception {0} was thrown while attempting to obtain an SIXAResource.
Explanation An error occurred while attempting to obtain an SIXAResource.
Action See linked exception for cause.
CWSIV0451E: An internal error occurred. The activation specification {0} passed on endpoint activation was not of the expected type {1}.
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/.
CWSIV0452E: The exception {1} was thrown while attempting to validate the activation specification {0} during endpoint activation.
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.
CWSIV0501E: The properties {1} defined on the activation specification {0} are incorrect.
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.
CWSIV0502E: An internal error. The following exception was thrown while attempting to obtain an SIDestinationAddressFactory: {0}.
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/.
CWSIV0503E: An internal error has occurred during the registration of the WLM classifier for the core SPI resource adapter: {0}.
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/.
CWSIV0550E: An internal error occurred. The exception {1} was thrown by the message endpoint factory {0} when attempting to determine whether the onMessage method is transacted.
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/.
CWSIV0554E: An internal error occurred. An attempt was made to obtain a connection to the messaging engine with UUID {0} on bus {1} after the endpoint {2} has been deactivated.
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/.
CWSIV0555E: The exception {0} was thrown when processing the startup of messaging engine {1} on bus {2} for endpoint activation {3}.
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.
CWSIV0600E: An internal error occurred. The message endpoint {0} does not implement the expected interface {1}.
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/.
CWSIV0601E: An internal error occurred. The exception {0} was received when attempting to unlock the messages {1}.
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/.
CWSIV0602E: An internal error occurred. The exception {0} was received when attempting to delete the message {1} under transaction {2}.
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/.
CWSIV0603E: An internal error occurred. The exception {0} was received when attempting to delete the messages {1} under transaction {2}.
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/.
CWSIV0604E: An internal error occurred. The exception {0} was received when attempting to obtain the request metrics instance.
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/.
CWSIV0650E: An internal error occurred. The exception {0} was received when attempting to obtain the XAResource from connection {1}.
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/.
CWSIV0651E: An internal error occurred. The exception {0} was received when attempting to invoke beforeDelivery on endpoint {1}.
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/.
CWSIV0652E: An internal error occurred. The XAResource {0} has not been enlisted after calling beforeDelivery on endpoint {1}.
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/.
CWSIV0700E: An internal error occurred. The exception {0} was received when attempting to clone the parent connection for session {1}.
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/.
CWSIV0701E: Use of the method {1} is not supported.
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.
CWSIV0702E: The session is no longer in scope.
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.
CWSIV0752E: There are no messaging engines enabled for the bus {0} on the same server as the message-driven bean.
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.
CWSIV0753E: An internal error occurred. The following exception was thrown when attempting to determine the set of queue points for the destination {1}: {0}.
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/.
CWSIV0754E: The destination {0} on bus {1} is foreign to the bus to which the message-driven bean is connected.
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.
CWSIV0755E: The destination {0} on bus {1} is of the type {3} not the required type {2}.
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.
CWSIV0756E: An internal error occurred. The destination {0} on bus {1} has a definition of an unexpected 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/.
CWSIV0757E: The destination {0} on bus {1} was not found.
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.
CWSIV0758E: An internal error occurred. The following exception was thrown when attempting to obtain the definition of destination {0} on bus {1}: {2}.
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/.
CWSIV0759W: During activation of a message-driven bean, no suitable active messaging engines were found in the local server on the bus {0}.
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.
CWSIV0764I: A consumer has been created for a message-driven bean against destination {2} on bus {0} following the activation of messaging engine {1}.
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.
CWSIV0765E: The exception {0} was thrown when attempting to create a connection to another messaging engine during the stopping of messaging engine {1} on bus {2}.
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.
CWSIV0766E: The exception {0} was thrown to the consumer for destination {1} on messaging engine {2} on bus {3} for endpoint activation {4}.
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.
CWSIV0767E: The exception {0} was thrown on a connection to messaging engine {1} for endpoint activation {2}.
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.
CWSIV0768I: The last local messaging engine {0} on bus {1} used by endpoint activation {2} is stopping.
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.
CWSIV0769W: The creation of a consumer for remote destination {0} on bus {1} for endpoint activation {2} failed with exception {3}.
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.
CWSIV0770W: A consumer for remote destination {0} on bus {1} for endpoint activation {2} failed with exception {3}.
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.
CWSIV0771I: A consumer for remote destination {0} on bus {1} for endpoint activation {2} has now been successfully created.
Explanation The inbound resource adapter has now successfully created a consumer for the given remote destination.
Action No user action required.
CWSIV0772E: There are no longer any messaging engines defined for the bus {0} on the same server as the message-driven bean for destination {1}.
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.
CWSIV0773E: The exception {0} was thrown when processing the updated configuration for messaging engine {1} on bus {2} for endpoint activation {3}.
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.
CWSIV0774W: The exception {0} was thrown to the consumer for destination {1} on messaging engine {2} on bus {3} for endpoint activation {4} while the messaging engine was reloading its configuration.
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.
CWSIV0775W: The creation of a connection for destination {0} on bus {1} for endpoint activation {2} failed with exception {3}.
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.
CWSIV0776W: A connection to remote messaging engine {0} on bus {1} for endpoint activation {2} failed with exception {3}.
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.
CWSIV0777I: A connection to remote messaging engine {0} for destination {1} on bus {2} for endpoint activation {3} is successfully created.
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.
CWSIV0778I: The local messaging engine {0} for bus {1} that is required by endpoint activation {2} is now available.
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.
CWSIV0779I: The last local messaging engine {0} for bus {1} that is required by endpoint activation {2} is destroyed.
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.
CWSIV0780W: The remote messaging engine {0} on bus {1} to which endpoint activation {2} was connected has terminated.
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.
CWSIV0781W: The remote messaging engine {0} on bus {1} to which endpoint activation {2} was connected is quiescing.
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.
CWSIV0782W: The creation of a connection for destination {0} on bus {1} for endpoint activation {2} failed with exception {3}.
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.
CWSIV0783E: The creation of a connection for destination {0} on bus {1} for endpoint activation {2} failed with exception {3}.
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.
CWSIV0801E: The exception {0} was thrown during the creation of a connection to messaging engine {1} on bus {2}.
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.
CWSIV0803E: The exception {0} was thrown during the creation of a consumer for the destination {1} on messaging engine {2} on bus {3}.
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.
CWSIV0804E: The exception {0} was thrown during the addition of a destination listener for messaging engine {1} on bus {2}.
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.
CWSIV0805E: The exception {0} was thrown during the creation of a consumer for the new destination {1} on messaging engine {2} on bus {3}.
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.
CWSIV0806E: The exception {0} was thrown to the consumer for destination {1} on messaging engine {2} on bus {3} for endpoint activation {4}.
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.
CWSIV0807E: The exception {0} was thrown on a connection to messaging engine {1} for endpoint activation {2}.
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.
CWSIV0850E: An internal error occurred. The message endpoint {0} does not implement the expected interface {1}.
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/.
CWSIV0851E: An internal error occurred. The exception {0} was thrown while attempting to obtain an instance of the onMessage method.
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/.
CWSIV0900E: The exception {0} was thrown while attempting to create a listener for destination {1} on bus {2} using connection {3}.
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.
CWSIV0901E: An internal error occurred. The exception {0} was thrown while attempting to obtain an instance of the SelectionCriteriaFactory.
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/.
CWSIV0950E: An internal error occurred. The exception {0} was thrown while attempting to create a connection on factory {1}.
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/.
CWSIV0951E: An internal error occurred. The exception {0} was thrown while attempting to create a connection to messaging engine {1}.
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/.
CWSIV0952E: An internal error occurred. An attempt was made to create a listener on a connection that has been closed.
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/.
CWSIV0953E: An internal error occurred. An attempt was made to create a dispatcher on a connection that has been closed.
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/.
CWSIV0954E: The authentication exception {0} was thrown while attempting to create a connection on factory {1}.
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
CWSIV0955E: The authentication exception {0} was thrown while attempting to create a connection to messaging engine {1}.
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
CWSIV1000E: An internal error occurred. The message endpoint factory {0} passed to the resource adapter did not implement the expected interface {1}.
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/.
CWSIV1050E: An internal error occurred. The request object {0} passed to the resource adapter did not implement the expected interface {1}.
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/.
CWSIV1051E: An internal error occurred. The array of messages {3} returned for the message handle {2} from the session {0} on messaging engine {1} did not contain a single message.
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/.
CWSIV1052W: The inbound resource adapter received the exception {3} when processing the message handle {2} from the session {0} on messaging engine {1}.
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.
CWSIV1053E: An internal error occurred. The inbound resource adapter failed to locate an endpoint activation pool for {0} so was unable to retreive an endpoint activation
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/.
CWSIV1100E: An internal error occurred. The exception {0} was thrown while attempting to obtain messages from the enumeration {1}.
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/.
CWSIV1150E: An internal error occurred. The exception {0} was thrown while attempting to obtain messages from the enumeration {1}.
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/.
CWSIV1151E: An internal error occurred. The exception {0} was thrown while attempting to obtain the identifier for the session {0} created from connection {1}.
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/.
CWSIV1152E: An internal error occurred. The message endpoint factory {0} passed to the resource adapter did not implement the expected interface {1}.
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/.
CWSIV1153E: An internal error occurred. The exception {2} was thrown while attempting to unlock message {0} from enumeration {1}.
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/.
CWSIV1200E: An internal error occurred. The exception {0} was received when attempting to invoke beforeDelivery on endpoint {1}.
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/.
CWSIV1201E: An internal error occurred. The exception {1} was received when attempting to create an uncoordinated transaction on connection {0}.
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/.
CWSIV1202E: An internal error occurred. The exception {1} was received when attempting to register the synchronization {0}.
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/.
CWSIV1203E: The transaction {0} returned from the connection did not implement the expected interface {1}.
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.
CWSIV9999E: {0}
Explanation If the message does not give sufficient information, check previous messages for further help.
Action See previous messages for further information.
Reference topic    

Terms of Use | Feedback

Last updated: Feb 21, 2008 7:07:28 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.sib.ra.CWSIVMessages.html

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