search

ari-ban / glassfish-genericjmsra

0 stars 0 forks source link

Expected InvalidDestinationException is not thrown #19

Closed arinban closed 14 years ago

arinban commented 18 years ago

As per the jms spec calling the following API with invalidSubscriptionName should throw InvalidDestinationException. javax.jms.Session.unsubscribe(invalidSubscriptionName).

But this is not observed when we run CTS Compatibility test with Sun Java System Application Server 8.2 PE using genericjmsra 1.0 and IBM MQ 6.0.

Note: CTS compatibility test source code is available only to the licensees who signed up with Sun Microsystems for Java EE License. For more information regarding the Java EE License see the following URL http://java.sun.com/j2ee/verified/

you can also see the following URL for the list of Licensees who already signed up for Java EE license. http://java.sun.com/j2ee/compatibility.html

Environment

Operating System: All Platform: Sun

Affected Versions

[1.0]

arinban commented 6 years ago
arinban commented 18 years ago

@glassfishrobot Commented Reported by raja_perumal

arinban commented 18 years ago

@glassfishrobot Commented binod said: Assigning to Ramesh

arinban commented 18 years ago

@glassfishrobot Commented rampsarathy said: WSMQ 6.0 does not throw this exception when unsubscribe is called. Please refer to the following link for documentation http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/jms77s1.htm

So, this issue cannot be resolved from within the generic JMS RA.

arinban commented 18 years ago

@glassfishrobot Commented rampsarathy said: This is a spec incompatibility in WS MQ cannot fix in RA

arinban commented 18 years ago

@glassfishrobot Commented Was assigned to rampsarathy

arinban commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-19

arinban commented 14 years ago

@glassfishrobot Commented Marked as incomplete on Sunday, September 5th 2010, 8:21:08 pm