Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Obsolete
Priority: Major
Fix Version/s: TBD EAP 5
Affects Version/s: EAP_EWP 5.1.2
Component/s: HornetQ
Labels:
- hornetq
Environment:

JBoss-EAP-5.1.2, HornetQ-2.2.10-B2+JBPAPP-8396 (HQ_2_2_10_EAP_GA_JBPAPP-8396-v4, 122)

Steps to Reproduce:
Hide

Create two durable subscribers with having the same cliend id

Configure them to listen to the same Topic

Start the first durable subscriber and then the second durable subscriber

An IllegalStateException will be thrown instead of InvalidClientIDException
Show
Create two durable subscribers with having the same cliend id Configure them to listen to the same Topic Start the first durable subscriber and then the second durable subscriber An IllegalStateException will be thrown instead of InvalidClientIDException
Affects:

Compatibility/Configuration
Docs QE Status:
NEW

Description

According to the JMS API Documentation[1], the JMS broker should throw an InvalidClientIDException when a JMS client specifies a duplicate ClientID for a durable subscriber. However HornetQ throws an IllegalStateException instead.

<snip>
JMSException - if the JMS provider fails to set the client ID for this connection due to some internal error.
InvalidClientIDException - if the JMS client specifies an invalid or duplicate client ID.
IllegalStateException - if the JMS client attempts to set a connection's client ID at the wrong time or when it has been administratively configured.
</snip>

[1] http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html#getClientID%28%29

Attachments

Activity

People

Assignee:: Clebert Suconic

Reporter:: Tyronne Wickramarathne

Votes:: 1 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2012/06/05 8:37 AM

Updated:: 2019/05/21 4:50 AM

Resolved:: 2019/05/21 4:50 AM