JAkub Scholz created QPID-5106:
----------------------------------
Summary: 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
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 API).
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 [127.0.0.1:39092-localhost:20000]
TcpTransport closing...
2013-08-30 13:51:18 [Messaging] debug [127.0.0.1:39092-localhost:20000] 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.127.0.0.1:20000-127.0.0.1:39092:
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: [email protected]
For additional commands, e-mail: [email protected]
