Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) Release Notes

Oracle Tuxedo Message Queue 12c Release 2 (12.1.3)
Date: December 2014

Revision Date	Summary of Change
December 2014	GA Release

•

•

•

Release 12c R2 (12.1.3)

Oracle Tuxedo Message Queue (OTMQ), provides rich queuing functionality for Oracle Tuxedo applications, as well as for standalone applications. For more information, see Oracle Tuxedo Message Queue Product Overview.

What's New and Improved

Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) includes the following new major features and enhancements:

•

Oracle MessageQ PAMS API Support

For Oracle MessageQ (OMQ) application compatibility, PAMS APIs are supported. OMQ applications can run with OTMQ after they are recompiled and relinked.

For more information, see Oracle Tuxedo Message Queue PAMS Programming Guide.

•

Configuration Migration Tools

Used for OMQ to OTMQ migration, these tools automatically convert the configuration file from OMQ to OTMQ.

For more information, see Migrating from OMQ to OTMQ 12c.

•

Database Message Storage

Provides the ability to store persistent queue messages in Oracle Database (which can leverage various Oracle Database high availability features).

•

Easy Configuration

Improved qspacecreate and qcreate commands allow for easy setup of Oracle Tuxedo Message Queue.

•

Queue Cluster

Allows multiple queue servers in different groups to form one cluster, and run concurrently with the same queue service name. Service requests can be distributed among the groups of the cluster, thus providing a queue cluster distributed across several machines.

For more information, see Oracle Tuxedo Message Queue Reference.

Note:

In this release, enqueued messages cannot be replicated to other queue server groups. Messages can be dequeued only when both sender and receiver are connected to same group(s).

•

Persistent Message Cache

Enqueued persistent messages are kept in memory cache to significantly improve performance (especially for highly concurrent enqueue and dequeue situations).

Supported Platforms

Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) supported platforms are listed in the OTMQ 12c Release 2 (12.1.3) Platform Data Sheets.

Known Issues

Table 1 lists Oracle Tuxedo Message Queue 12c Release 2 (12.1.3) known issues. Entries include a description of the problem, and a workaround or solution where appropriate.

Table 1 Known Issues
Bug Number	Description and Workaround or Solution
20085029	Problem: ENABLE_Q_NOTIFY_REQ messages “usertag” must be unique to the group. For ENABLE_Q_NOTIFY_REQ messages, the usertag must be unique to the group. When applying this usertag in a DISABLE_Q_NOTIFY_REQ message to disable notify, the queue server deletes all subscriptions that match. For example, there are two applications using the same usertag to subscribe to qnotify, when one application sends DISABLE_Q_NOTIFY_REQ to unsubscribe to qnotify, the other subscriptions are also cancelled.
	Platform: All.
	Workaround: Use the unique usertag for ENABLE_Q_NOTIFY_REQ messages from different groups and queues.
20092927	Problem: OTMQ returns different psb status or routine status in RTS UMA messages. When a program calls pams_put_msg to enqueue cross-group messages and the target queue does not exist or is not active, OTMQ returns different psb status or routine status in RTS UMA messages.
	Platform: All
	Workaround: N/A.
20092942	Problem: OTMQ does not return ACK messages when DIP is CONF, ACK, MEM, DEQ or QUE if enqueue fails. When a program calls pams_put_msg to enqueue cross-group messages and the target queue does not exist or is not active, OTMQ does not return ACK messages when DIP is CONF, ACK, MEM, DEQ or QUE if enqueue fails.
	Platform: All
	Workaround: N/A.
20092982	Problem: OTMQ returns different psb status or routine status in ACK messages. When a program calls pams_put_msg to enqueue cross-group messages and the target queue does not exist or is not active, OTMQ returns different psb status or routine status in ACK messages.
	Platform: All
	Workaround: N/A.
20099767	Problem: : MBS queries with QM_STATE_MBS_LIST_ALL_LINK_DOMAIN fail on remote Domain. MBS queries with QM_STATE_MBS_LIST_ALL_LINK_DOMAIN fail on remote Domain.
	Platform: All
	Workaround: N/A