AMQP 1.0官方规范完整版：OASIS高级消息队列协议

amqp协议说明

需积分: 10 142 浏览量更新于2024-07-09 收藏 738KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

AMQP (Advanced Message Queuing Protocol) 是一个由 OASIS (Organization for the Advancement of Structured Information Standards) 制定的开放标准，旨在提供一种在分布式系统间高效、可靠地传输数据的消息传递协议。AMQP Version 1.0 于2012年10月29日发布，作为OASIS的一个技术委员会——AMQP TC (Technical Committee) 的成果，其目标是促进企业消息队列系统的互操作性和标准化。 AMQP的核心概念包括以下几个关键点： 1. **协议架构**：AMQP基于分层的设计，包括基础协议层（如连接管理、通道管理、交换机和路由）、消息传输层（帧和序列化）以及应用级别接口（如队列、交换器、绑定等）。这允许开发人员构建高度灵活和可扩展的消息传递解决方案。 2. **安全性**：AMQP支持多种安全机制，如SSL/TLS用于加密通信，提供数据隐私和完整性保护。此外，它还支持访问控制和认证，确保只有授权用户能访问消息和资源。 3. **标准化与版本更新**：文档提供了多个版本，如CSRPD01、OS（Object Storage）和最终的v1.0。这些版本反映了技术的发展和成熟度，最新的v1.0版本是最权威的，包含了所有必要的规范和最佳实践。 4. **互操作性**：AMQP v1.0设计为可以与多种现有的消息中间件、服务和应用程序无缝集成，确保了跨平台和跨供应商的兼容性。 5. **应用场景**：AMQP广泛应用于云计算、物联网(IoT)、微服务架构和企业服务总线等领域，为大规模分布式系统间的异步通信提供了一致性和可靠性。 6. **贡献者与社区**：OASIS AMQP TC 由多位专家领导，如Ram Jeyaraman，他们的电子邮件地址 Ram.Jeyaraman@microsoft.com 是联系该委员会的重要途径，反映了业界对标准化协议的需求和参与。要深入了解AMQP，推荐查阅官方文档，例如http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.xml 和 http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf，这些文档详尽地解释了协议的各个部分及其使用方法。通过学习AMQP，开发者可以构建高效、安全且可扩展的现代消息处理系统。

资源详情

资源推荐

PART 0. OVERVIEW 0.4 Revision History

AMQP-14 : PDF Document should use Sans-Serif font to be consistent with OASIS Standards

AMQP-15 : Move copyright statement to second line of footer to be in line with OASIS style

AMQP-16 : References to INETCO should be “INETCO Systems Limited”

AMQP-17 : Typo in AMQP Open.hostname description

AMQP-18 : Add ﬁgure titles to the HTML presentation

AMQP-19 : Fix generated (sub-)section titles in the PDF where they contain a dash (“-”)

AMQP-20 : PDF Presentation: use correct “open” and “close” double quotes

AMQP-21 : Change presentation of cross-references to show only section number, not title

AMQP-22 : Transport: Incoporate feedback from Steve Huston’s review

AMQP-23 : Abstract/Introduction: Incoporate feedback from Steve Huston’s review

AMQP-24 : Update XML transformation to render “n byte” as “n-byte”

AMQP-25 : Types: Incoporate feedback from Steve Huston’s review

AMQP-26 : Transport: Incoporate feedback from Steve Huston’s review (2)

AMQP-27 : add missing diagram titles

AMQP-28 : Confused use of the terms two’s-complement“ and ”signed“

AMQP-30 : Clarify version negotiation

AMQP-31 : Figure numbering incorrect in the HTML presentation

AMQP-32 : Clarify open behavior

AMQP-33 : Tighten conformance language for 2.4.5

AMQP-34 : Add description of HDR EXCH state in 2.4.6

AMQP-35 : Clariﬁcations to 2.6.12

AMQP-40 : Incorrect title for IEEE1003 reference

AMQP-45 : Transactions: Incorporate feedback from Steve Huston’s review

AMQP-46 : Security: Incorporate feedback from Steve Huston’s review

AMQP-48 : Remove capitalization of certain terms within the speciﬁcation

AMQP-49 : Description of “dynamic” ﬁeld refers to non-existent concepts of “session name” and “client-id”

2011-11-08 : Working Draft 1

AMQP-1 : Make the deﬁnition of ﬂow.echo more explicit

AMQP-2 : Make it explicit that ﬂow.properties is only for a link

AMQP-3 : speciﬁcation/overview.xml has a contributor’s name in all caps

AMQP-4 : speciﬁcation/overview.xml is slightly inconsistent in use of company legal entity names and ab-

breviations thereof

amqp-core-complete-v1.0-os

Standards Track Work Product Copyright

29 October 2012

Page 15 of 124

PART 1. TYPES

Part 1: Types

1.1 Type System

The AMQP type system deﬁnes a set of commonly used primitive types for interoperable data representation.

AMQP values can be annotated with additional semantic information beyond that associated with the primitive

type. This allows for the association of an AMQP value with an external type that is not present as an AMQP

primitive. For example, a URL is commonly represented as a string, however not all strings are valid URLs,

and many programming languages and/or applications deﬁne a speciﬁc type to represent URLs. The AMQP

type system would allow for the deﬁnition of a code with which to annotate strings when the value is intended to

represent a URL.

1.1.1 Primitive Types

The AMQP type system deﬁnes a standard set of primitive types for representing both common scalar values and

common collections. The scalar types include booleans, integral numbers, ﬂoating point numbers, timestamps,

UUIDs, characters, strings, binary data, and symbols. The collection types include arrays (monomorphic), lists

(polymorphic), and maps.

1.1.2 Described Types

The primitive types deﬁned by AMQP can directly represent many of the basic types present in most popular

programming languages, and therefore can be trivially used to exchange basic data. In practice, however, even

the simplest applications have their own set of custom types used to model concepts within the application’s

domain. In messaging applications these custom types need to be externalized for transmission.

AMQP provides a means to do this by allowing any AMQP type to be annotated with a descriptor. A descriptor

forms an association between a custom type, and an AMQP type. This association indicates that the AMQP type

is actually a representation of the custom type. The resulting combination of the AMQP type and its descriptor is

referred to as a described type.

A described type contains two distinct kinds of type information. It identiﬁes both an AMQP type and a custom

type (as well as the relationship between them), and so can be understood at two different levels. An application

with intimate knowledge of a given domain can understand described types as the custom types they represent,

thereby decoding and processing them according to the complete semantics of the domain. An application with

no intimate knowledge can still understand the described types as AMQP types, decoding and processing them

as such.

1.1.3 Composite Types

AMQP deﬁnes a number of composite types used for encoding structured data such as frame bodies. A composite

type deﬁnes a composite value where each constituent value is identiﬁed by a well-known named ﬁeld. Each

composite type deﬁnition includes an ordered sequence of ﬁelds, each with a speciﬁed name, type, and multiplicity.

Composite type deﬁnitions also include one or more descriptors (symbolic and/or numeric) for identifying their

deﬁned representations. Composite types are formally deﬁned using the XML notation deﬁned in section 1.3.

amqp-core-complete-v1.0-os

Standards Track Work Product Copyright

29 October 2012

Page 16 of 124

PART 1. TYPES 1.2 Type Encodings

1.1.4 Restricted Types

AMQP deﬁnes the notion of a restricted type. This is a new type derived from an existing type where the permitted

values of the new type are a subset of the values of the existing type. Restricted types are commonly used

programming constructs, the most frequent being “enumerations” which in AMQP terminology are restrictions of

the integral types. However, the AMQP notion of restricted types can also represent more open ended restrictions

such as a URL which can be thought of as a restriction of the string type.

A restricted type deﬁnition might limit the permitted values to either a pre-deﬁned ﬁxed set, or an open-ended set.

In the former case, each permitted value is called a choice and all possible choices are listed in the formal type

deﬁnition. In the latter case, the nature of the restriction is speciﬁed as text in the formal type deﬁnition.

The existing type from which a restricted type is derived is referred to as the source type for the restriction. A

restricted type might or might not be annotated with a descriptor on the wire depending on the formal deﬁnition for

the type.

1.2 Type Encodings

An AMQP encoded data stream consists of untyped bytes with embedded constructors. The embedded con-

structor indicates how to interpret the untyped bytes that follow. Constructors can be thought of as functions that

consume untyped bytes from an open ended byte stream and construct a typed value. An AMQP encoded data

stream always begins with a constructor.

constructor untyped bytes

| |

+--+ +-----------------+-----------------+

| | | |

... 0xA1 0x1E "Hello Glorious Messaging World" ...

| | | | |

| | | utf8 bytes |

| | | |

| | # of data octets |

| | |

| +-----------------+-----------------+

| |

| string value encoded according

| to the str8-utf8 encoding

primitive format code

for the str8-utf8 encoding

Figure 1.1: Primitive Format Code (String)

An AMQP constructor consists of either a primitive format code, or a described format code. A primitive format

code is a constructor for an AMQP primitive type. A described format code consists of a descriptor and a primitive

format-code. A descriptor deﬁnes how to produce a domain speciﬁc type from an AMQP primitive value.

amqp-core-complete-v1.0-os

Standards Track Work Product Copyright

29 October 2012

Page 17 of 124

PART 1. TYPES 1.2 Type Encodings

constructor untyped bytes

| |

+-----------+-----------+ +-----------------+-----------------+

| | | |

... 0x00 0xA1 0x03 "URL" 0xA1 0x1E "http://example.org/hello-world" ...

| | | | |

+------+------+ | | |

| | | |

descriptor | +------------------+----------------+

| |

| string value encoded according

| to the str8-utf8 encoding

primitive format code

for the str8-utf8 encoding

(Note: this example shows a string-typed descriptor, which is

considered reserved)

Figure 1.2: Described Format Code (URL)

The descriptor portion of a described format code is itself any valid AMQP encoded value, including other de-

scribed values. The formal BNF for constructors is given below.

constructor = format-code

/ %x00 descriptor constructor

format-code = fixed / variable / compound / array

fixed = empty / fixed-one / fixed-two / fixed-four

/ fixed-eight / fixed-sixteen

variable = variable-one / variable-four

compound = compound-one / compound-four

array = array-one / array-four

descriptor = value

value = constructor untyped-bytes

untyped-bytes = *OCTET ; this is not actually *OCTET, the

; valid byte sequences are restricted

; by the constructor

; fixed width format codes

empty = %x40-4E / %x4F %x00-FF

fixed-one = %x50-5E / %x5F %x00-FF

fixed-two = %x60-6E / %x6F %x00-FF

fixed-four = %x70-7E / %x7F %x00-FF

fixed-eight = %x80-8E / %x8F %x00-FF

fixed-sixteen = %x90-9E / %x9F %x00-FF

; variable width format codes

variable-one = %xA0-AE / %xAF %x00-FF

variable-four = %xB0-BE / %xBF %x00-FF

; compound format codes

compound-one = %xC0-CE / %xCF %x00-FF

compound-four = %xD0-DE / %xDF %x00-FF

; array format codes

array-one = %xE0-EE / %xEF %x00-FF

array-four = %xF0-FE / %xFF %x00-FF

Figure 1.3: Constructor BNF

Format codes map to one of four different categories: ﬁxed width, variable width, compound and array. Values

encoded within each category share the same basic structure parameterized by width. The subcategory within a

format-code identiﬁes both the category and width.

Fixed Width The size of ﬁxed-width data is determined based solely on the subcategory of the format

code for the ﬁxed width value.

amqp-core-complete-v1.0-os

Standards Track Work Product Copyright

29 October 2012

Page 18 of 124

PART 1. TYPES 1.2 Type Encodings

Variable Width The size of variable-width data is determined based on an encoded size that preﬁxes the

data. The width of the encoded size is determined by the subcategory of the format code

for the variable width value.

Compound Compound data is encoded as a size and a count followed by a polymorphic sequence of

count constituent values. Each constituent value is preceded by a constructor that indicates

the semantics and encoding of the data that follows. The width of the size and count is

determined by the subcategory of the format code for the compound value.

Array Array data is encoded as a size and count followed by an array element constructor followed

by a monomorphic sequence of values encoded according to the supplied array element

constructor. The width of the size and count is determined by the subcategory of the format

code for the array.

The bits within a format code can be interpreted according to the following layout:

Bit: 7 6 5 4 3 2 1 0

+------------------------------------+ +----------+

+------------------------------------+ +----------+

1 octet 1 octet

| |

+-------------------------------------------------+

format-code

ext-type: only present if subtype is 0xF

Figure 1.4: Format Code Layout

The following table describes the subcategories of format-codes:

Subcategory Category Format

==============================================================================

0x4 Fixed Width Zero octets of data.

0x5 Fixed Width One octet of data.

0x6 Fixed Width Two octets of data.

0x7 Fixed Width Four octets of data.

0x8 Fixed Width Eight octets of data.

0x9 Fixed Width Sixteen octets of data.

0xA Variable Width One octet of size, 0-255 octets of data.

0xB Variable Width Four octets of size, 0-4294967295 octets of data.

0xC Compound One octet each of size and count, 0-255 distinctly

typed values.

0xD Compound Four octets each of size and count, 0-4294967295

distinctly typed values.

0xE Array One octet each of size and count, 0-255 uniformly

typed values.

0xF Array Four octets each of size and count, 0-4294967295

uniformly typed values.

Figure 1.5: Subcategory Formats

Please note, unless otherwise speciﬁed, AMQP uses network byte order for all numeric values.

1.2.1 Fixed Width

The width of a speciﬁc ﬁxed width encoding can be computed from the subcategory of the format code for the

ﬁxed width value:

amqp-core-complete-v1.0-os

Standards Track Work Product Copyright

29 October 2012

Page 19 of 124

剩余124页未读，继续阅读

ancoa

粉丝: 11
资源: 18

AMQP 1.0官方规范完整版：OASIS高级消息队列协议

amqp-core-complete-v1.0、amqp.0-10.zip

amqp-client-5.10.0.jar

amqp-client api

E:\ideaWS\spring-rabbitmq-consumers\src\main\java\com\lxy\rabbitmq\listener2\AckListener.java:9:8 java: com.lxy.rabbitmq.listener2.AckListener不是抽象的, 并且未覆盖org.springframework.amqp.core.MessageListener中的抽象方法onMessage(org.springframework.amqp.core.Message)

org.springframework.amqp.core.Message

org.springframework.amqp.core.Queue的属性值

Incompatible types. Found: 'org.springframework.amqp.core.BindingBuilder. DirectExchangeRoutingKeyConfigurer', required: 'org.springframework.amqp.core.BindingBuilder'是什么错误

erlang-23.2.7-2.el7.x86_64.rpm和rabbitmq-server-3.8.14-1.el7.noar

Consider defining a bean of type 'org.springframework.amqp.rabbit.connection.ConnectionFactory' in your configuration.

AMPQ-CPP windows

AMQP.BasicProperties properties = new AMQP.BasicProperties().builder().expiration("10000").build();

A component required a bean of type 'org.springframework.amqp.rabbit.core.RabbitAdmin' that could not be found. 是什么问题

宝塔 php7.3安装amqp

org.springframework.amqp.amqpconnectexception

WARN o.s.amqp.rabbit.listener.BlockingQueueConsumer - Failed to declare queue: hotel.insert

AMQP.BasicProperties properties = new AMQP.BasicProperties().builder().headers(map).build();

org.springframework.amqp.AmqpConnectException: java.net.ConnectException: Connection timed out: connect

Caused by: java.lang.ClassCastException: org.springframework.amqp.core.TopicExchange cannot be cast to java.util.concurrent.Exchanger

org.springframework.amqp.amqpioexception: java.io.ioexception

最新资源