[jira] [Commented] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.

2016-09-28 Thread Gordon Sim (JIRA)

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

Gordon Sim commented on QPID-6868:
--

Fix proposed for QPID-7415 has now been committed to master and will be part of 
the next release. It will cause an exception to be thrown for rejected messages 
by default (though this is configurable).

> [AMQP 1.0 C++ Client] No errors for rejected messages.
> --
>
> Key: QPID-6868
> URL: https://issues.apache.org/jira/browse/QPID-6868
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Client
>Affects Versions: qpid-cpp-0.34
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> The _qpid-cpp_ code has been built with _qpid-proton_ version 0.10.
> The broker is ActiveMQ 5.12.1.
> The protocol used in AMQP 1.0.
>Reporter: Håkan Johansson
> Attachments: example.cc
>
>
> When using protocol AMQP 1.0 and non-syncing send calls it is impossible to 
> know if a message was rejected by the broker. I get warnings in the log, but 
> nothing else.
> I have created a short example that shows the issue (see attached file).
> If I call _send_ with _sync_ set to _true_, then I get an exception, just as 
> expected.
> Expected behavior:
> I expect to get an exception when the failed send is first noticed, either in 
> the _sender.send_ call itself, a subsequent _sender.send_ call, or when 
> calling _session.sync_.
> Test program output (sync=false):
> {noformat}
> Writing message 1
> Writing message 2
> Writing message 3
> Writing message 4
> 2015-11-18 10:34:24 [Messaging] warning delivery 0 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 1 was rejected by peer
> Writing message 5
> 2015-11-18 10:34:24 [Messaging] warning delivery 2 was rejected by peer
> Writing message 6
> 2015-11-18 10:34:24 [Messaging] warning delivery 3 was rejected by peer
> Writing message 7
> 2015-11-18 10:34:24 [Messaging] warning delivery 4 was rejected by peer
> Writing message 8
> 2015-11-18 10:34:24 [Messaging] warning delivery 5 was rejected by peer
> Writing message 9
> 2015-11-18 10:34:24 [Messaging] warning delivery 6 was rejected by peer
> Writing message 10
> 2015-11-18 10:34:24 [Messaging] warning delivery 7 was rejected by peer
> Syncing
> 2015-11-18 10:34:24 [Messaging] warning delivery 8 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 9 was rejected by peer
> Closing
> Done
> {noformat}
> Test program output (sync=true):
> {noformat}
> Writing message 1
> Writing message 2
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> Error: Message was rejected by peer
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Commented] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.

2016-09-26 Thread Robbie Gemmell (JIRA)

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

Robbie Gemmell commented on QPID-6868:
--

QPID-7415 and related details on the linked reviewboard seem relevent, perhaps 
check them out.

> [AMQP 1.0 C++ Client] No errors for rejected messages.
> --
>
> Key: QPID-6868
> URL: https://issues.apache.org/jira/browse/QPID-6868
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Client
>Affects Versions: qpid-cpp-0.34
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> The _qpid-cpp_ code has been built with _qpid-proton_ version 0.10.
> The broker is ActiveMQ 5.12.1.
> The protocol used in AMQP 1.0.
>Reporter: Håkan Johansson
> Attachments: example.cc
>
>
> When using protocol AMQP 1.0 and non-syncing send calls it is impossible to 
> know if a message was rejected by the broker. I get warnings in the log, but 
> nothing else.
> I have created a short example that shows the issue (see attached file).
> If I call _send_ with _sync_ set to _true_, then I get an exception, just as 
> expected.
> Expected behavior:
> I expect to get an exception when the failed send is first noticed, either in 
> the _sender.send_ call itself, a subsequent _sender.send_ call, or when 
> calling _session.sync_.
> Test program output (sync=false):
> {noformat}
> Writing message 1
> Writing message 2
> Writing message 3
> Writing message 4
> 2015-11-18 10:34:24 [Messaging] warning delivery 0 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 1 was rejected by peer
> Writing message 5
> 2015-11-18 10:34:24 [Messaging] warning delivery 2 was rejected by peer
> Writing message 6
> 2015-11-18 10:34:24 [Messaging] warning delivery 3 was rejected by peer
> Writing message 7
> 2015-11-18 10:34:24 [Messaging] warning delivery 4 was rejected by peer
> Writing message 8
> 2015-11-18 10:34:24 [Messaging] warning delivery 5 was rejected by peer
> Writing message 9
> 2015-11-18 10:34:24 [Messaging] warning delivery 6 was rejected by peer
> Writing message 10
> 2015-11-18 10:34:24 [Messaging] warning delivery 7 was rejected by peer
> Syncing
> 2015-11-18 10:34:24 [Messaging] warning delivery 8 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 9 was rejected by peer
> Closing
> Done
> {noformat}
> Test program output (sync=true):
> {noformat}
> Writing message 1
> Writing message 2
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> Error: Message was rejected by peer
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Commented] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.

2016-09-26 Thread Radim Kubis (JIRA)

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

Radim Kubis commented on QPID-6868:
---

[~gsim] [~cliffjansen] Could you have a look on this item, please. This is 
blocker for our JAMQ. Thanks.

> [AMQP 1.0 C++ Client] No errors for rejected messages.
> --
>
> Key: QPID-6868
> URL: https://issues.apache.org/jira/browse/QPID-6868
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Client
>Affects Versions: qpid-cpp-0.34
> Environment: Red Hat Enterprise Linux Server release 6.7 (Santiago)
> The _qpid-cpp_ code has been built with _qpid-proton_ version 0.10.
> The broker is ActiveMQ 5.12.1.
> The protocol used in AMQP 1.0.
>Reporter: Håkan Johansson
> Attachments: example.cc
>
>
> When using protocol AMQP 1.0 and non-syncing send calls it is impossible to 
> know if a message was rejected by the broker. I get warnings in the log, but 
> nothing else.
> I have created a short example that shows the issue (see attached file).
> If I call _send_ with _sync_ set to _true_, then I get an exception, just as 
> expected.
> Expected behavior:
> I expect to get an exception when the failed send is first noticed, either in 
> the _sender.send_ call itself, a subsequent _sender.send_ call, or when 
> calling _session.sync_.
> Test program output (sync=false):
> {noformat}
> Writing message 1
> Writing message 2
> Writing message 3
> Writing message 4
> 2015-11-18 10:34:24 [Messaging] warning delivery 0 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 1 was rejected by peer
> Writing message 5
> 2015-11-18 10:34:24 [Messaging] warning delivery 2 was rejected by peer
> Writing message 6
> 2015-11-18 10:34:24 [Messaging] warning delivery 3 was rejected by peer
> Writing message 7
> 2015-11-18 10:34:24 [Messaging] warning delivery 4 was rejected by peer
> Writing message 8
> 2015-11-18 10:34:24 [Messaging] warning delivery 5 was rejected by peer
> Writing message 9
> 2015-11-18 10:34:24 [Messaging] warning delivery 6 was rejected by peer
> Writing message 10
> 2015-11-18 10:34:24 [Messaging] warning delivery 7 was rejected by peer
> Syncing
> 2015-11-18 10:34:24 [Messaging] warning delivery 8 was rejected by peer
> 2015-11-18 10:34:24 [Messaging] warning delivery 9 was rejected by peer
> Closing
> Done
> {noformat}
> Test program output (sync=true):
> {noformat}
> Writing message 1
> Writing message 2
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> 2015-11-18 10:30:10 [Messaging] warning delivery 1 was rejected by peer
> Error: Message was rejected by peer
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org