Bug 888392 - QpidConnectionFactoryProxy Should Implement Queue/TopicConnectionFactory Interfaces
Summary: QpidConnectionFactoryProxy Should Implement Queue/TopicConnectionFactory Inte...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-jca
Version: 2.1.2
Hardware: All
OS: All
high
high
Target Milestone: 2.3
: ---
Assignee: Weston M. Price
QA Contact: Valiantsina Hubeika
URL:
Whiteboard:
Depends On:
Blocks: 892736
TreeView+ depends on / blocked
 
Reported: 2012-12-18 16:04 UTC by Weston M. Price
Modified: 2016-02-22 00:59 UTC (History)
8 users (show)

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.
Clone Of:
: 892736 (view as bug list)
Environment:
Last Closed: 2013-03-06 18:53:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-4150 0 None None None Never
Apache JIRA QPID-4318 0 None None None Never
Red Hat Product Errata RHSA-2013:0561 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging 2.3 security update 2013-03-06 23:48:13 UTC

Description Weston M. Price 2012-12-18 16:04:56 UTC 
Currently the QpidConnectionFactoryProxy only implements the ConnectionFactory JMS 1.1 API. The proxy needs to implement the Queue/TopicConnectionFactory portions of the API to be consistent and pass certain tests that require this functionality (most notably the JEE TCK).
Comment 1 Weston M. Price 2013-01-07 11:39:02 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?
Comment 2 Weston M. Price 2013-01-07 11:42:30 UTC 
*** Bug 888508 has been marked as a duplicate of this bug. ***
Comment 5 Weston M. Price 2013-01-07 18:20:09 UTC 
*** Bug 892736 has been marked as a duplicate of this bug. ***
Comment 7 Valiantsina Hubeika 2013-01-16 16:00:10 UTC 
1. Could you please advise me where I can find the patch.
2. Could you please suggest tests to run to verify the fix.
Comment 8 Weston M. Price 2013-01-16 16:56:00 UTC 
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.
Comment 9 Valiantsina Hubeika 2013-01-17 08:07:50 UTC 
(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.
Comment 10 Weston M. Price 2013-01-17 11:36:13 UTC 
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.
Comment 12 Valiantsina Hubeika 2013-01-23 14:17:56 UTC 
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.
Comment 14 Valiantsina Hubeika 2013-02-18 09:00:17 UTC 
JEE TCK tests pass.

--> verified
Comment 16 errata-xmlrpc 2013-03-06 18:53:10 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.