You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/03/29 16:40:41 UTC

[jira] [Commented] (ARTEMIS-1049) JMSDeliveryTime silently break JMSXGroupID

    [ https://issues.apache.org/jira/browse/ARTEMIS-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15947465#comment-15947465 ] 

Justin Bertram commented on ARTEMIS-1049:
-----------------------------------------

What behavior are you expecting and what do you actually observe? Do you have a reproducible test-case?

> JMSDeliveryTime silently break JMSXGroupID
> ------------------------------------------
>
>                 Key: ARTEMIS-1049
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1049
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Igor Vagulin
>
> Due to some issue in code my message get both delivery time and JMSXGroupID property set. This breaks ordering guaranteed by JMSXGroupID, one consumer working thought. 
> Please at least add some warning to log. Spent 2 days of my life trying to hunt this down.
> message produced by code below will not be properly ordered
> {quote}
> conn = connFactory.createConnection();
> session = conn.createSession();
> producer = session.createProducer(null);
> long deliveryTime = ZonedDateTime.now().toEpochSecond() * 1000
> m.setJMSDeliveryTime(deliveryTime);
> m.setStringProperty("JMSXGroupID", "mylovelygroup");
> producer.send(d, m);
> {quote}



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