Express (Distributed operating systems), v8.0 > Reference > Messages
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 specified 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 More info at:
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 More info at:
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.
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 More info at:
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 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.
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 More info at:
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 the exception was received while attempting to re-associate. Action See the linked exception for further information.
CWSIV0156E: The connection has been invalidated.
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.
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 an exception was received. Action See the linked exception for further information.
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 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.
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 exception was created while attempting to commit it. Action See the linked exception for further information.
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 exception was created while attempting to roll it back. Action See the linked exception for further information.
CWSIV0200E: The connection from which this session was created has been invalidated.
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.
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 exception was received while attempting to create a connection to the messaging engine. Action See the linked exception for further information.
CWSIV0350E: An internal error occurred. The exception {0} was thrown while attempting to create a core SPI connection factory.
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.
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 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.
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 More info at:
CWSIV0353E: An internal error occurred. The exception {0} was thrown while attempting to clone a connection to the messaging engine.
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.
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 More info at:
CWSIV0355E: An internal error occurred. Whilst creating the managed connection the following exception was thrown: {0}
Explanation An exception was created while attempting to create a managed connection. Action See the linked exception for further information.
CWSIV0356W: The following JCA Connection error has occurred when trying to get the connection. 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 then attempt to obtain another one. Action More info at:
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 More info at:
CWSIV0402E: An internal error occurred. The exception {0} was thrown while attempting to close a connection to the messaging engine.
Explanation An exception was created while attempting to close a connection to the messaging engine. Action See the linked exception for further information.
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 More info at:
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 More info at:
CWSIV0405E: An internal error occurred. The exception {0} was thrown while the container was attempting to begin a local transaction.
Explanation An exception was created while the container was attempting to begin a local transaction. Action See the linked exception for further information.
CWSIV0406E: An internal error occurred. The exception {0} was thrown while the container was attempting to commit a local transaction.
Explanation An exception was created while the container was attempting to commit a local transaction. Action See the linked exception for further information.
CWSIV0407E: An internal error occurred. The exception {0} was thrown while the container was attempting to roll back a local transaction.
Explanation An exception was created while the container was attempting to roll back a local transaction. Action See the linked exception for further information.
CWSIV0408E: An internal error occurred. The exception {0} was thrown while attempting to obtain an SIXAResource.
Explanation An exception was created while attempting to obtain an SIXAResource. Action See the linked exception for further information.
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 More info at:
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 following problems were found when validating the properties defined on the activation specification. The problems are {1}. The activation specification is : {0}
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.
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 More info at:
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 More info at:
CWSIV0504E: The bus name on a Core SPI activation specification must be given a value
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.
CWSIV0505E: The following destination type on a Core SPI activation specification is invalid [{4}]. The values [{0}] or [{1}] or [{2}] or [{3}] are expected.
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.
CWSIV0506E: The following share durable subscription field on a Core SPI activation specification is invalid [{3}]. The values [{0}], [{1}] or [{2}] are expected.
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.
CWSIV0507E: The durable subscription home on a Core SPI activation specification must have a value when using durable subscriptions.
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.
CWSIV0508E: The following destination type on a Core SPI activation specification is invalid [{3}]. The values [{0}] or [{1}] or [{2}] are expected.
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.
CWSIV0509E: The maximum batch size on a Core SPI activation specification must be given a positive value
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.
CWSIV0510E: The following deletion mode on a Core SPI activation specification is invalid [{3}]. The values [{0}] or [{1}] or [{2}] are expected.
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.
CWSIV0511E: The maximum concurrency on a Core SPI activation specification must be given a positive value
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.
CWSIV0512E: The following target type field on a Core SPI activation specification is invalid [{3}]. The values [{0}], [{1}] or [{2}] are expected.
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.
CWSIV0513E: The following target significance field on a Core SPI activation specification is invalid [{2}]. The values [{0}] or [{1}] are expected.
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.
CWSIV0514E: The provider endpoints were set to {0} on a Core SPI activation specification. Provider endpoints are not supported when the property "use server subject" is set.
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.
CWSIV0515E: The "use destination wildcard" property was set on a Core SPI activation specification whilst using a Topic Space. The property "use destination wildcard" is not supported when a Topic Space is used.
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.
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 More info at:
CWSIV0551W: The maximum concurrency for the MDB {0} was set to {1} in it''s activation specification. This is higher than the JCA maximum pool size of {2} and so the MDB''s maximum concurrency has been lowered to {3}
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)
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 More info at:
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 associated with a valid authentication alias. Action See the linked exception for further information. After resolving issue, restart messaging engine, resource adapter or application.
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 More info at:
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 More info at:
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 More info at:
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 More info at:
CWSIV0605W: The Message Endpoint {0} that was listening to the destination {1} should be deactivated as the the maximum number of sequential failures was reached.
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.
CWSIV0606E: An internal error occurred. When attempting to delete the message handle {1} under transaction {2}, the session {0} was not of the required type {3}
Explanation The resource adapter encountered a problem while attempting to delete a message handle Action More info at:
CWSIV0607E: An internal error occurred. When attempting to delete the message handle {2} under transaction {3}, the list of messages {1} was expected to contain 1 message but instead contained {0} messages
Explanation The resource adapter encountered a problem while attempting to delete a message handle Action More info at:
CWSIV0608E: An internal error occurred. When attempting to delete the message handle {1} under transaction {2}, the following exception was thrown {0}
Explanation The resource adapter encountered a problem while attempting to delete a message handle Action More info at:
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 More info at:
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 More info at:
CWSIV0652E: A specific messaging engine must be specified to use JMS resources within a transaction. The connection property {0} must be set to {1}.
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'.
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 More info at:
CWSIV0701E: Use of the method {0} is not supported.
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.
CWSIV0702E: The session is no longer in scope.
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.
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 More info at:
CWSIV0754E: The destination {0} on bus {1} is not defined as a queue point on the bus to which the message-driven bean is connected
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.
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, type or both.
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 More info at:
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 More info at:
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 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.
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 action is 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 the linked exception for further information. 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 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.
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.
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 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.
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 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.
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 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 messaging engine {0} for destination {1} on bus {2} has been successfully created.
Explanation The inbound resource adapter successfully created a connection to a messaging engine for the given endpoint activation. Action No 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 action is required.
CWSIV0779I: The last local messaging engine {0} for bus {1} has been 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 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 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 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.
CWSIV0784I: The local messaging engine {0} on bus {1} is stopping.
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.
CWSIV0785I: The messaging engine {0} on bus {1} is quiescing.
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.
CWSIV0786I: The messaging engine {0} on bus {1} has terminated.
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.
CWSIV0787I: Failed to create a connection to a messaging engine when specifying a target to connect to. The target was of type {0} had a significance of {1} and was named {2}. The target bus was {3}
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.
CWSIV0788I: Failed to create a connection to a messaging engine. The target bus was {0}
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.
CWSIV0789I: Failed to create a connection to a messaging engine that hosts the durable subscription. The target bus was {0} and the durable subscrption home was {1}
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
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 the linked exception for further information. After resolving issue, restart messaging engine, resource adapter or application.
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 the linked exception for further information. After resolving issue, restart messaging engine, resource adapter or application.
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, resource adapter or application.
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, resource adapter or application.
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.
CWSIV0808W: Consumption of messages from the destination {0} on messaging engine {1} on bus {2} has stopped because the session was dropped. The exception was {3}
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.
CWSIV0809W: The wildcard destination name {0} matched zero destinations that are available for consumption of messages on messaging engine {1} on bus {2}
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.
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 More info at:
CWSIV0851E: An internal error occurred. The exception {0} was thrown while attempting to obtain an instance of the onMessage method.
Explanation An exception was created during the attempt to obtain an instance of the onMessage method. Action More info at:
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 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.
CWSIV0901E: An internal error occurred. The exception {0} was thrown while attempting to obtain an instance of the SelectionCriteriaFactory.
Explanation An exception was created during the attempt to obtain an instance of the SelectionCriteriaFactory. Action More info at:
CWSIV0902W: The Message Endpoint {0} that was listening to the destination {1} has been paused by the system.
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.
CWSIV0903W: The Message Endpoint {0} that was listening to the destination {1} was attempted to be paused but the invoke of the MBean failed with the following exception {2}.
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.
CWSIV0904W: During an attempt to stop an MDB there were zero Message Endpoints that could be located for endpoint {0} which was listening to the destination {1}.
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.
CWSIV0905W: During an attempt to stop an MDB there were multiple Message Endpoint that were found endpoint {0} which was listening to the destination {1}. Only one endpoint should exist. The MDB will not be stopped.
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.
CWSIV0906W: The MDB maximum sequential message failure configuration value has been changed from the value {0} to {1}.
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.
CWSIV0907W: The MDB maximum sequential message failure configuration value has been changed from the value {0} to {1}.
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.
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 More info at:
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 More info at:
CWSIV0952E: An internal error occurred. An attempt was made to create a listener on a connection that has been closed.
Explanation The messaging engine connection received a request to create a listener but has already been closed. Action More info at:
CWSIV0953E: An internal error occurred. An attempt was made to create a dispatcher on a connection that has been closed.
Explanation The messaging engine connection received a request to create a dispatcher but has already been closed. Action More info at:
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 Ensure that the correct user name and password are supplied on the ActivationSpec that the message-driven bean 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 Ensure that the correct user name and password are supplied on the ActivationSpec that the message-driven bean is configured to use
CWSIV0957E: The authentication exception {0} was thrown while attempting to get the WAS Subject.
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.
CWSIV0958E: The authorization exception {0} was thrown while attempting to create a connection to messaging engine {1} using the activation specification {2}.
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.
CWSIV0959E: The authorization exception {0} was thrown while attempting to create a connection to messaging engine {1} using the activation specification {2}.
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.
CWSIV0960E: The authorization exception {0} was thrown while attempting to create a connection to the bus {1} using the activation specification {2}.
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.
CWSIV0961E: The authorization exception {0} was thrown while attempting to create a connection to the bus {1} using the activation specification {2}.
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.
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 unique name of the message-driven bean. Action More info at:
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 More info at:
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 More info at:
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 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.
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 could not get an endpoint activation from the pool because it could not locate the pool Action More info at:
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 More info at:
CWSIV1101W: The MDB maximum concurrency configuration value has been changed from the value {0} to {1}.
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.
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 More info at:
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 More info at:
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 unique name of the message-driven bean. Action More info at:
CWSIV1153W: Unable to read the custom property MessageLockExpiry as Platform Messaging was unable to locate the server. The default value of {0} will be used
Explanation The inbound resource adapter could not find the server so the property MessageLockExpiry was assigned a default value. Action More info at:
CWSIV1154W: The value for the MessageLockExpiry appears to be {0}, this can not be converted to an integer. The default value of {1} will be used.
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.
CWSIV1155W: The value for the MessageLockExpiry appears to be {0}, this value can not be negative. The default of {1} will be used
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.
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 More info at:
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 More info at:
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 More info at:
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 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.
CWSIV1210E: An internal error occured, a null was passed in to the method {1} on object {0}. A valid XAResource must be passed in.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWSIV9999E: {0}
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.