[jira] [Updated] (ARTEMIS-1206) [Core JMS Client] Violates JMS 2.0 Specification - allows two active connections with same clientid

2017-06-05 Thread Michael Andre Pearce (JIRA)

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Andre Pearce updated ARTEMIS-1206:
--
Description: 
Currently it is possible to make two completely separate client connections to 
the broker, with the same client id.

This was found/raised on looking at differing behaviours between the Core JMS 
Client and the Qpid AMQP Client.
https://issues.apache.org/jira/browse/ARTEMIS-1205

Attached is a test case, where by the Qpid Client errors, where as the Core 
Client does not.



  was:
Currently it is possible to make two completely separate client connections to 
the broker, with the same client id.




> [Core JMS Client] Violates JMS 2.0 Specification - allows two active 
> connections with same clientid
> ---
>
> Key: ARTEMIS-1206
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1206
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Michael Andre Pearce
> Attachments: JMSDurableConsumerTest2.java
>
>
> Currently it is possible to make two completely separate client connections 
> to the broker, with the same client id.
> This was found/raised on looking at differing behaviours between the Core JMS 
> Client and the Qpid AMQP Client.
> https://issues.apache.org/jira/browse/ARTEMIS-1205
> Attached is a test case, where by the Qpid Client errors, where as the Core 
> Client does not.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (ARTEMIS-1206) [Core JMS Client] Violates JMS 2.0 Specification - allows two active connections with same clientid

2017-06-05 Thread Michael Andre Pearce (JIRA)

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Andre Pearce updated ARTEMIS-1206:
--
Description: 
Currently it is possible to make two completely separate client connections to 
the broker, with the same client id.



> [Core JMS Client] Violates JMS 2.0 Specification - allows two active 
> connections with same clientid
> ---
>
> Key: ARTEMIS-1206
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1206
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Michael Andre Pearce
> Attachments: JMSDurableConsumerTest2.java
>
>
> Currently it is possible to make two completely separate client connections 
> to the broker, with the same client id.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (ARTEMIS-1206) [Core JMS Client] Violates JMS 2.0 Specification - allows two active connections with same clientid

2017-06-05 Thread Michael Andre Pearce (JIRA)

 [ 
https://issues.apache.org/jira/browse/ARTEMIS-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Andre Pearce updated ARTEMIS-1206:
--
Attachment: JMSDurableConsumerTest2.java

> [Core JMS Client] Violates JMS 2.0 Specification - allows two active 
> connections with same clientid
> ---
>
> Key: ARTEMIS-1206
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1206
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Michael Andre Pearce
> Attachments: JMSDurableConsumerTest2.java
>
>
> Currently it is possible to make two completely separate client connections 
> to the broker, with the same client id.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)