Bug 1254951
Summary: | qpidd does not support limiting a container-id to a single connection (JMS ClientID enforcement) | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Robbie Gemmell <rgemmell> |
Component: | qpid-cpp | Assignee: | messaging-bugs <messaging-bugs> |
Status: | NEW --- | QA Contact: | Messaging QE <messaging-qe-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.2 | CC: | gsim, jross, messaging-bugs |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
In this release of the product, when using +qpidd+ as the broker, there can be more than one active connection with the same JMS `client-id`.
This is because +qpidd+ does not recognise the connection capability requested by the JMS client over AMQP 1.0 which allows only a single connection with the same container ID.
As a workaround, +qpidd+ does allow limiting connections by userid, which may satisfy some cases.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 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: |
Description
Robbie Gemmell
2015-08-19 10:05:31 UTC
|