Bug 667771
| Summary: | Cannot create a subscription on topic created for another JMS Provider, class of topic provided is: org.apache.qpid.client.AMQAnyDestination | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Gordon Sim <gsim> | ||||
| Component: | qpid-java | Assignee: | Rajith Attapattu <rattapat+nobody> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Reznicek <freznice> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 1.3 | CC: | esammons, freznice | ||||
| Target Milestone: | 2.0 | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause: When creating a durable subscriber with a destination created using an addressing string a javax.jms.InvalidDestinationException is thrown.
Consequence: The application is unable to create durable subscriptions from destinations created using an addressing string. The workaround was to create a Topic using session.createTopic method passing an address string.
Fix: The createDurableSubscription method modified it's destination validation to check if the destination passed in is an instance of javax.jms.Topic and org.apache.qpid.client.AMQDestination instead of just checking if the destination is an instance of org.apache.qpid.client.AMQTopic
Result: The createDurableSubscription method is now able to create a durable subscriber from a destination created using an address string.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-23 15:46:45 UTC | Type: | --- | ||||
| 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: | 702247 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Gordon Sim
2011-01-06 18:19:09 UTC
Created attachment 472108 [details]
test program
Workaround is to not use jndi config but to use Session.createTopic() instaed to obtain the Topic destination. Fixed in upstream at rev 1076516. http://svn.apache.org/viewvc?rev=1076516&view=rev The fixes are now included in rpms from version qpid-java-0.9.1080013-2
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: When creating a durable subscriber with a destination created using an addressing string a javax.jms.InvalidDestinationException is thrown.
Consequence: The application is unable to create durable subscriptions from destinations created using an addressing string. The workaround was to create a Topic using session.createTopic method passing an address string.
Fix: The createDurableSubscription method modified it's destination validation to check if the destination passed in is an instance of javax.jms.Topic and org.apache.qpid.client.AMQDestination instead of just checking if the destination is an instance of org.apache.qpid.client.AMQTopic
Result: The createDurableSubscription method is now able to create a durable subscriber from a destination created using an address string.
The attached code currently crashes with NPE, see bug 702247 for details. Adding dependency on bug 702247. The issue has been corrected on qpid-java-0.10-6, tested on RHEL 5.6/6.1 i[36]86 / x86_64, no more above NPE/exception seen, messages received ok. -> VERIFIED An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2011-0890.html |