oslo.messaging

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

stable/zed

stable/2023.1

master

stable/ussuri

stable/stein

stable/xena

stable/yoga

stable/wallaby

stable/train

stable/victoria

feature/nats-driver

feature/zmq

feature/pika

feature/amqp-dispatch-router

14.3.1

rocky-eol

14.3.0

xena-em

14.2.0

14.1.0

queens-eol

wallaby-em

14.0.0

pike-eol

13.0.0

12.9.4

12.14.0

12.7.3

victoria-em

12.9.3

12.7.2

12.13.0

12.9.2

12.12.0

12.11.1

ussuri-em

12.11.0

12.10.0

12.9.1

12.9.0

ocata-eol

train-em

12.8.0

10.2.4

12.5.2

12.1.6

10.2.3

12.7.1

12.7.0

12.6.1

stein-em

10.2.2

12.1.5

12.6.0

12.5.1

12.5.0

12.1.4

12.4.0

12.1.3

12.3.0

12.1.2

12.2.2

9.5.2

10.2.1

12.2.1

12.1.1

12.2.0

12.1.0

12.0.0

rocky-em

11.0.0

9.5.1

10.5.0

10.4.1

10.4.0

10.3.0

queens-em

8.1.4

5.35.6

10.2.0

10.1.0

10.0.0

9.8.0

9.7.2

5.35.5

9.7.1

9.7.0

8.1.3

9.6.0

pike-em

5.30.8

ocata-em

9.5.0

9.4.0

5.35.4

5.30.7

9.3.1

9.3.0

9.2.1

9.2.0

9.1.1

9.1.0

9.0.1

9.0.0

8.1.2

5.35.3

5.30.6

5.17.4

8.1.1

5.30.5

5.35.2

5.30.4

5.35.1

8.1.0

8.0.0

7.0.0

6.5.0

5.30.3

6.4.1

6.4.0

6.3.0

6.2.0

6.1.0

6.0.0

5.36.0

5.35.0

5.17.3

5.30.2

5.34.1

5.34.0

newton-eol

5.33.1

5.33.0

5.30.1

5.32.0

5.31.0

5.30.0

5.29.0

mitaka-eol

5.10.2

5.17.2

5.28.0

5.27.0

5.26.0

5.25.0

5.24.2

5.24.1

5.24.0

5.23.0

5.22.0

5.21.0

5.20.0

5.19.0

5.18.0

5.17.1

5.17.0

5.16.0

liberty-eol

5.15.0

5.14.0

5.13.0

5.10.1

5.12.0

5.11.0

5.10.0

5.9.0

5.8.0

5.7.0

5.6.0

5.5.0

kilo-eol

5.4.0

5.3.0

5.2.0

5.1.0

5.0.0

4.6.1

4.6.0

4.5.1

4.5.0

4.4.0

4.3.0

4.2.0

4.1.0

4.0.0

juno-eol

3.1.0

3.0.0

2.9.0

2.8.1

2.8.0

2.7.0

2.6.1

2.6.0

1.4.2

2.5.0

2.4.0

2.3.0

2.2.0

2.1.0

2.0.0

1.17.1

1.17.0

1.16.0

icehouse-eol

1.15.0

1.14.0

1.8.3

1.13.0

1.12.1

1.12.0

1.11.0

1.8.2

1.10.0

1.9.0

1.8.1

1.8.0

1.7.0

1.6.0

1.5.1

1.5.0

1.4.1

1.4.0

1.4.0.0a5

1.4.0.0a4

1.3.1

1.4.0.0a3

1.4.0.0a2

1.4.0.0a1

1.3.0

1.3.0a9

1.3.0a8

1.3.0a7

1.3.0a6

1.3.0a5

1.3.0a4

1.3.0a3

1.3.0a2

1.3.0a1

1.2.0a11

1.2.0a10

1.2.0a9

1.2.0a8

1.2.0a7

1.2.0a6

1.2.0a5

1.2.0a4

1.2.0a3

1.2.0a2

1.2.0a1

History

Hervé Beraud 391ce7fc69 Correctly handle missing RabbitMQ queues Currently, setting the '[oslo_messaging] direct_mandatory_flag' config option to 'True' (the default) will result in a 'MessageUndeliverable' exception being raised when sending a reply if a RabbitMQ queue is missing [1]. It was the responsibility of the application to handle this exception, however, many applications are not doing so. This has resulted in a number of bug reports. Start handling this error condition, using a retry loop to attempt to resend the message and work around any temporary glitches. Since attempting to send a reply will will no longer raise an exception, there is little benefit in retaining the '[oslo_messaging] direct_mandatory_flag' config option: users setting this to False will simply not benefit from the retry logic and improved logging added here. This option is already deprecated though and will be fully removed in a future release. [1] https://www.rabbitmq.com/channels.html Change-Id: Id5cddbefbe24ef100f1cc522f44430df77d217cb Closes-Bug: #1905965 (cherry picked from commit `4937949dff`)	2 years ago
..
source	Correctly handle missing RabbitMQ queues	2 years ago
requirements.txt	Switch to newer openstackdocstheme and reno versions	3 years ago

Hervé Beraud 391ce7fc69 Correctly handle missing RabbitMQ queues

Currently, setting the '[oslo_messaging] direct_mandatory_flag' config
option to 'True' (the default) will result in a 'MessageUndeliverable'
exception being raised when sending a reply if a RabbitMQ queue is
missing [1]. It was the responsibility of the application to handle
this exception, however, many applications are not doing so. This has
resulted in a number of bug reports.

Start handling this error condition, using a retry loop to attempt to
resend the message and work around any temporary glitches. Since
attempting to send a reply will will no longer raise an exception,
there is little benefit in retaining the '[oslo_messaging]
direct_mandatory_flag' config option: users setting this to False will
simply not benefit from the retry logic and improved logging added
here. This option is already deprecated though and will be fully
removed in a future release.

[1] https://www.rabbitmq.com/channels.html

Change-Id: Id5cddbefbe24ef100f1cc522f44430df77d217cb
Closes-Bug: #1905965
(cherry picked from commit 4937949dff)

source Correctly handle missing RabbitMQ queues 2 years ago

requirements.txt Switch to newer openstackdocstheme and reno versions 3 years ago