[
https://issues.apache.org/jira/browse/QPID-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143579#comment-14143579
]
Alan Conway commented on QPID-6107:
-----------------------------------
I see the same thing on fedora, I run spout like this:
/home/aconway/qpid/qpid/python/examples/api/spout --count=3000
'q;{create:always}' --id=foo
I modified spout as per diff below to use qpid_messaging and AMQP 1.0.
I see the same thing running against qpidd or dispatch so it is deinitely a
client side issue.
diff --git a/qpid/doc/book/src/cpp-broker/HA-Queue-Replication.xml
b/qpid/doc/book/src/cpp-broker/HA-Queue-Replication.xml
index 71ad157..81b55a3 100644
--- a/qpid/doc/book/src/cpp-broker/HA-Queue-Replication.xml
+++ b/qpid/doc/book/src/cpp-broker/HA-Queue-Replication.xml
@@ -24,7 +24,7 @@ under the License.
<title>Replicating Queues with the HA module</title>
<para>
As well as support for an active-passive cluster, the
- <filename>HA</filename> module allows you to replicate individual queues,
+ HA module allows you to replicate individual queues,
even if the brokers are not in a cluster. The
<firstterm>original</firstterm>
queue is used as normal. The <firstterm>replica</firstterm> queue is
updated automatically as messages are added to or removed from the original
@@ -36,7 +36,7 @@ under the License.
other than via the automatic updates from the original. Adding or
removing
messages on the replica queue will make replication inconsistent and may
cause message loss.
- The <filename>HA</filename> module does <emphasis>not</emphasis> enforce
+ The HA module does <emphasis>not</emphasis> enforce
restricted access to the replica queue (as it does in the case of a
cluster)
so it is up to the application to ensure the replica is not used until
it has
been disconnected from the original.
@@ -45,7 +45,7 @@ under the License.
<section>
<title>Replicating queues</title>
<para>
- To create a replica queue, the <filename>HA</filename> module must be
+ To create a replica queue, the HA module must be
loaded on both the original and replica brokers (it is loaded by
default.)
You also need to set the configuration option:
<programlisting>
diff --git a/qpid/python/examples/api/spout b/qpid/python/examples/api/spout
index 6584b85..f6af734 100755
--- a/qpid/python/examples/api/spout
+++ b/qpid/python/examples/api/spout
@@ -19,7 +19,7 @@
#
import optparse, time
-from qpid.messaging import *
+from qpid_messaging import *
from qpid.util import URL
from qpid.log import enable, DEBUG, WARN
@@ -98,6 +98,7 @@ else:
content_type = "text/plain"
conn = Connection(opts.broker,
+ protocol='amqp1.0',
reconnect=opts.reconnect,
reconnect_interval=opts.reconnect_interval,
reconnect_limit=opts.reconnect_limit)
> Python Swig wrapped bindings consistently fail with spout and drain
> -------------------------------------------------------------------
>
> Key: QPID-6107
> URL: https://issues.apache.org/jira/browse/QPID-6107
> Project: Qpid
> Issue Type: Bug
> Components: Python Client (Wrapped)
> Reporter: Darryl L. Pierce
> Assignee: Darryl L. Pierce
>
> In testing the packages [1] I have come across an interesting situation.
> It first came up on Ubuntu trusty but then I was able to reproduce it on
> F20.
> If I send less than 2272 messages using the spout tool then things
> success. But at 2273 then the Python bindings fail with:
> Fatal Python error: deallocating None
> Aborted (core dumped)
> using the following command line:
> $ python /usr/share/doc/python-qpid-messaging/examples/python/spout --count
> 2272 "my-queue;{create:always,delete:receiver}"
> I'm not sure why 2273 is the magic number. On Fedora the number seems to
> be a little bit lower at 2269 before it starts to fail as on Debian.
> On the other side, when I then drain the queue with:
> $ python /usr/share/doc/python-qpid-messaging/examples/python/drain "my-queue"
> I can't receive more than 1505 messages on Debian and 1503 on Fedora
> before the same error occurs. To verify this I ran very specific spout
> and drain situations with Python. On Debian I did:
> $ sudo service qpidd stop; sudo service qpidd start; python
> /usr/share/doc/python-qpid-messaging/examples/python/spout --count 1505
> "my-queue;{create:always,delete:receiver}"
> $ python /usr/share/doc/python-qpid-messaging/examples/python/drain "my-queue"
> $ sudo service qpidd stop; sudo service qpidd start; python
> /usr/share/doc/python-qpid-messaging/examples/python/spout --count 1506
> "my-queue;{create:always,delete:receiver}"
> $ python /usr/share/doc/python-qpid-messaging/examples/python/drain
> "my-queue" > output.txtFatal Python error: deallocating None
> Aborted (core dumped)
> On Fedora I changed 1505/1506 to 1503/1504 and the output was
> consistently the same.
> [1] https://launchpad.net/~mcpierce/+archive/ubuntu/qpid-testing/+packages
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
