Hi Daniil, I am generally very supportive of this effort (although sadly I don't get much time to work on Qpid anymore). We are looking to do more work on AMQP 1.0 at OASIS soon and it would certainly make it easier to add the necessary improvements to Qpid Broker-J if we didn't have to try to work in equivalents for AMQP 0-x protocols. In general there is a lot of tidying up and improvement we can do to the broker if we remove some of the old legacy stuff.
As you imply we need to work out how we make the necessary changes to persisted messages and configuration data. For configuration, I would generally expect that we simply remove any AMQP port configuration which does not support AMQP 1.0. For persisted data we probably have enough code already to convert 0-x messages into 1.0 messages - though doing so in a way which preserves message order probably needs a small amount of work. Theoretically (although I don't like this alternative) we could retain the code to convert 0-x messages into 1.0 messages in memory and thus allow persisted messages to be retained (and potentially simply remove such messages at a later date). Thanks for bringing this forward, Rob On Mon, 17 Aug 2026 at 16:41, Daniil Kirilyuk <[email protected]> wrote: > Hi Colleagues, > > Broker-J currently supports AMQP 0-8, 0-9, 0-9-1, 0-10, and 1.0. > > We would like to propose the following gradual retirement of the AMQP 0-x > protocols: > > - Broker-J 11.0, targeted for 2027: declare AMQP 0-8, 0-9, 0-9-1, and > 0-10 deprecated. They would remain functional during the 11.x line, but > users would be encouraged to migrate to AMQP 1.0. > > > - Broker-J 12.0, targeted no earlier than 2028: remove support for > accepting AMQP 0-x client connections. > > The motivation is to concentrate development, testing, maintenance, and > security work on AMQP 1.0. The Qpid JMS AMQP 0-x client has already been > retired. > > Before deciding on this direction, we would particularly like to understand > the remaining use of AMQP 0-x with Broker-J: > > - Which AMQP 0-x versions are still used with Broker-J? > - Which client libraries and versions are involved? > - Are there migration blockers that prevent using AMQP 1.0? > > The proposed removal in 12.0 concerns AMQP 0-x wire-protocol support. Any > removal would need to include a documented and safe upgrade path for > existing Broker-J installations. In particular, we would need to account > for existing port configuration, durable messages, and other persisted data > that use legacy metadata formats. > > This is a proposal for community discussion and not a final decision. > > Kind regards, > Daniil Kirilyuk >
