Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1058320 - Messaging client needs needs way to default to AMQP version 1.0 (and not to 0.10)
Summary: Messaging client needs needs way to default to AMQP version 1.0 (and not to 0...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 3.0
Hardware: All
OS: All
medium
unspecified
Target Milestone: ---
: ---
Assignee: Gordon Sim
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-27 14:34 UTC by Chuck Rolke
Modified: 2014-07-30 20:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Apache JIRA QPID-5465 None None None Never

Description Chuck Rolke 2014-01-27 14:34:15 UTC
Description of problem:

Connections made through the Messaging Client library create AMQP 0.10 version connections by default. In order to get AMQP 1.0 connections the connection option "{protocol:amqp1.0}" must be specified for every connection.

Moving forward to an AMQP 1.0 world it is desirable to have connections be AMQP 1.0 by default with no connection option required.

Note that this issue is not reporting a bug. The code was designed to work this way. This BZ issue is suggesting an improvement on current behavior.

Version-Release number of selected component (if applicable):

3.0

How reproducible:

100%

Steps to Reproduce:
1. Create a connection with no connection options. It will be AMQP 0-10.
2.
3.

Actual results:

By default only AMQP 0-10 connections are created.

Expected results:

Through some setting/switch/method by default AMQP 1.0 connections are created. Anticipating future AMQP versions this same specification mechanism could select any supported version to be the default.

Additional info:

This feature would simplify life for Apache.NMS.AMQP connection management.


Note You need to log in before you can comment on or make changes to this bug.