Bug 506739

Summary: createDurableSubscriber needs to throw InvalidDestinationException if a temp topic is used.
Product: Red Hat Enterprise MRG Reporter: Rajith Attapattu <rattapat+nobody>
Component: qpid-javaAssignee: Rajith Attapattu <rattapat+nobody>
Status: CLOSED ERRATA QA Contact: Jan Sarenik <jsarenik>
Severity: medium Docs Contact:
Priority: low    
Version: 1.1.1CC: gsim, jsarenik, rafaels
Target Milestone: 1.1.6   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-14 17:32:34 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:
Attachments:
Description Flags
bug fix and test case
none
reproducer none

Description Rajith Attapattu 2009-06-18 14:32:30 UTC 
Description of problem:
Currently if a temp topic is passed in to the createDurableSubscriber method, an exception is not thrown. As per the JMS spec we need to throw an InvalidDestinationException.

Version-Release number of selected component (if applicable):
1.1.2

How reproducible:
Always

Steps to Reproduce:
Topic t = session.createTemporaryTopic();
TopicSubscriber ts = createDurableSubscriber(t,"myTopic");
  
Actual results:
No Exception thrown

Expected results:
InvalidDestinationException should be thrown
Comment 1 Rafael H. Schloming 2009-06-22 13:46:01 UTC 
Created attachment 348903 [details]
bug fix and test case
Comment 2 Gordon Sim 2009-06-26 09:25:21 UTC 
Fixed in qpid-java-0.5.751061-8
Comment 3 Jan Sarenik 2009-07-02 14:12:03 UTC 
Created attachment 350276 [details]
reproducer

Put into /usr/share/doc/rhm-0.5/java/org/apache/qpid/example/jmsexample/pubsub/
and then

 cd /usr/share/doc/rhm-0.5/java
 ./runSample.sh org/apache/qpid/example/jmsexample/pubsub/Publisher
Comment 5 errata-xmlrpc 2009-07-14 17:32:34 UTC 
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/RHBA-2009-1153.html