qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Sim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5106) Queue level message sequencing doesn't work with 1.0 client
Date Mon, 02 Sep 2013 16:26:52 GMT

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

Gordon Sim commented on QPID-5106:

The underlying issue was the brokers handling of annotations. However in addition this has
prompted an adjustment to the way in which the qpid::messaging API presents annotations. The
application can choose either to make no distinction between annotations and properties or
to have annotations for a fetched message given in a netsed map. The choice is controlled
through the nest_annotations connection option, whose default value is currently false.
> Queue level message sequencing doesn't work with 1.0 client
> -----------------------------------------------------------
>                 Key: QPID-5106
>                 URL: https://issues.apache.org/jira/browse/QPID-5106
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.24
>         Environment: CentOS 6.4, Qpid 0.24 RC3, C++
>            Reporter: JAkub Scholz
>            Assignee: Gordon Sim
> The JIRA QPID-4591 added the queue level sequencing. I played with it with the 0.24RC3
release and it seems it doesn't work properly with AMQP 1.0 producers (C++ / Qpid Messaging
> My queue is configured with following option:
>     u'qpid.queue_msg_sequence': u'queue.sequence'
> The connection which sends a message into this queue seems to be closed due to the amqp:internal-error:
> [0xda1200:0] <- CLOSE @24 [@29 [:"amqp:internal-error", "Expected descriptor of type
ulong or symbol; found ", null]]
> [0xda1200:0] <- EOS
> 2013-08-30 13:51:18 [Network] debug localhost:20000 decoded 107 bytes from 107
> Exception: Connection closed by peer
> 2013-08-30 13:51:18 [Messaging] debug [] TcpTransport
> 2013-08-30 13:51:18 [Messaging] debug [] Socket closed
> 2013-08-30 13:51:18 [Messaging] debug Driver stopped
> And the broker log seems to complain about the type:
> 2013-08-30 13:51:18 [Broker] warning Exchange response cannot deliver to  queue response.ABCFR_ABCFRALMMACC1.b3458152-e106-42a6-9c8c-4984c08cff81:
Expected descriptor of type ulong or symbol; found
> 2013-08-30 13:51:18 [Broker] error qpid. Expected descriptor
of type ulong or symbol; found
> When the sender is using AMQP 0.10, the sequencing seems to work fine.
> ---
> Additionally, when AMQP 1.0 is used for receiving the sequenced message, I seem to be
unable to get the sequence number property. Using msgProperties["queue.sequence"].asString()
seems to return only empty string and nothing else. Again, with 0.10 the sequence number seems
to be returned properly.
> Thanks & Regards
> Jakub

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

View raw message