+

Search Tips   |   Advanced Search

Strict message ordering using activation specifications or ASF listener ports connected to IBM MQ v6.0

Strict message ordering can be achieved when deploying message driven bean applications to the IBM MQ messaging provider for when no special facilities have been coded into the application to handle messages arriving out of order.

For WebSphere Application Server v7 and later, listener ports are stabilized. We should plan to migrate the IBM MQ message-driven bean deployment configurations from using listener ports to using activation specifications. For more information about how to configure activation specifications for non-ASF mode, see Configure activation specifications for non-ASF mode. However, we should not begin this migration until we are sure the application does not have to work on application servers earlier than WAS v7. For example, if we have an application server cluster with some members at v6.1 and some at a later version, we should not migrate applications on that cluster to use activation specifications until after we migrate all the application servers in the cluster to the later version.

The following assumptions have been made in this scenario:


WAS configuration for ordered delivery


Important information about this configuration


Circumstances in which messages can arrive out of order

Messages can arrive out of order with this deployment in the following circumstances:


Considerations for a clustered deployment


Related:

  • Message-driven beans - listener port components
  • Strict message ordering using non-ASF listener ports
  • Strict message ordering using activation specifications or ASF listener ports connected to IBM MQ v7.x
  • Message processing in ASF mode and non-ASF mode
  • Starting a listener port
  • Starting listener ports using scripting
  • Manage the message endpoint lifecycle
  • Tune messaging destinations for the IBM MQ messaging provider
  • Use wsadmin scripting
  • Manage message endpoints
  • Message listener service custom properties
  • Listener port settings
  • Stabilized features of WAS traditional

    IBM MQ library