Messages In A Tuxedo /Q Queue Cannot Be Dequeued Unless The Tuxedo Group For The Queue Is Restarted

(Doc ID 1997885.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle Tuxedo - Version 12.1.3 and later
Information in this document applies to any platform.


The application peeks and then dequeues messages from the Tuxedo /Q queues

Some messages on a Tuxedo /Q queue are listed after their expiration time, using qmadmin, and are never removed.

Shutting down and rebooting the entire Tuxedo server group (shutting down individual TMQUEUES is not sufficient) associated
with a Qspace/queue shows, on the next qmadmin qlist execution after reboot, that the messages are no longer listed on the queue.


===================  Fri Mar  6 14:34:57 EST 2015  =====================

qmadmin - Copyright (c) 1996-2012 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
> v
Verbose mode is now on
> qopen myqspace
> qset mytQ
Queue set to myQ

> qlist
Messages on queue myQ:
Msgid BU74rnAADkrAAAAAAAAAAAAAAADkrA=, priority 80, retrycnt 0, msglen 504
 Delivery qos: persistent,      Reply qos: default
 Expiration time: Thu 05 Mar 2015 03:20:06 PM EST
 Correlation id: QS11Q40|27972142558680120501793
Msgid BU74rnAAAnY/AAAAAAAAAAAAAAAnY/=, priority 50, retrycnt 0, msglen 272
 Delivery qos: persistent,      Reply qos: default
 Expiration time: Sat 28 Feb 2015 04:02:47 AM EST
 Correlation id: QS11Q40|27970142511416211919539



 Upgrade to Tuxedo 12.1.3


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms