Bug 888392
| Summary: | QpidConnectionFactoryProxy Should Implement Queue/TopicConnectionFactory Interfaces | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Weston M. Price <wprice> | |
| Component: | qpid-jca | Assignee: | Weston M. Price <wprice> | |
| Status: | CLOSED ERRATA | QA Contact: | Valiantsina Hubeika <vhubeika> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 2.1.2 | CC: | cdewolf, esammons, iboverma, lzhaldyb, mcressma, rattapat+nobody, tross, vhubeika | |
| Target Milestone: | 2.3 | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | qpid-jca-0.18-7 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
Currently the QpidConnectionFactoryProxy only implements the ConnectionFactory JMS 1.1 API. The proxy needs to implement the Queue/TopicConnectionFactory portions of the API (JMS 1.0).
Consequence:
TCK test failures that use these interfaces.
Fix:
QpidConnectionFactoryProxy to implement Queue/TopicConnectionFactory interfaces.
Result:
TCK tests that rely on those interfaces should now pass.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 892736 (view as bug list) | Environment: | ||
| Last Closed: | 2013-03-06 18:53:10 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: | ||||
| Bug Blocks: | 892736 | |||
|
Description
Weston M. Price
2012-12-18 16:04:56 UTC
The fix for this has been checked in on trunk. I know we are at the blocker stage for 2.3, however, since QE and a customer both need this fix. It has no impact on any component of the release other than JCA so I was wondering if we could get it in? *** Bug 888508 has been marked as a duplicate of this bug. *** *** Bug 892736 has been marked as a duplicate of this bug. *** 1. Could you please advise me where I can find the patch. 2. Could you please suggest tests to run to verify the fix. Justin or Irina integrated the patch so they would be better able to answer. In that patch is a unit test that tests the supported interfaces. (In reply to comment #8) > Justin or Irina integrated the patch so they would be better able to answer. > In that patch is a unit test that tests the supported interfaces. Setting need_info to Justin and Irina. Please see questions in the comment 7. Hi vhubeika...sorry, we talked about this in scrum yesterday. Currently the patch can be found at: wmprice@gethsemane ~/mrgm/qpid-internal (0.18-mrg *) $ git remote -v origin git://mrg1.lab.bos.redhat.com/qpid.git (fetch) origin git://mrg1.lab.bos.redhat.com/qpid.git (push) wmprice@gethsemane ~/mrgm/qpid-internal (0.18-mrg *) $ git branch -a | egrep jca remotes/origin/0.14-jca remotes/origin/0.18-mrg-2.2-jca remotes/origin/mrg_2.0.x-jca-rebase wmprice@gethsemane ~/mrgm/qpid-internal (0.18-mrg *) $ So, it's in our internal git repository. The branch you want is remotes/origin/0.18-mrg-2.2-jca Let me know if you need anything else. As a part of verification, code revision has been performed. The bug will be verified once the JEE TCK tests will be performed and passed. JEE TCK tests pass. --> verified 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. http://rhn.redhat.com/errata/RHSA-2013-0561.html |