Bug 1215806
| Summary: | Provide qpid JMS client that supports AMQP 1.0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Irina Boverman <iboverma> |
| Component: | distribution | Assignee: | mrg-program-list <mrg-program-list> |
| Status: | CLOSED ERRATA | QA Contact: | Michal Toth <mtoth> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | Development | CC: | mtoth, pematous, smumford, zkraus |
| Target Milestone: | 3.2 | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qpid-jms-0.1.0-1 | Doc Type: | Enhancement |
| Doc Text: |
MRG-M now offers a qpid JMS client at version 6.2, which supports AMQP 1.0
This support has been added as a result of requests from customers
Customers can now use AMQP 1.0 through the JMS client. Documentation for this feature is available from http://qpid.apache.org/components/jms/index.html.
.NOTE:
The new AMQP 1.0 qpid-jms client does not support the MRG-specific address strings used by the older AMQP 0.10 java client.
In the new client, the __queue name__ and and __topic name__ strings given to the new client represent only the name of the Queue or Topic to consume from or publish to.
Other concepts from the old client syntax such as subjects or operations to create and delete entities are not supported.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-08 13:10:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1242921, 1245128, 1254588, 1254590, 1264000 | ||
| Bug Blocks: | |||
|
Description
Irina Boverman
2015-04-27 19:17:12 UTC
Dependent bugs are in NEW and ASSIGNED state. QA work on this feature has been halted until dependent bugs are resolved first. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-1879.html |