At the end I have managed to make it run using AMQP 1.0 protocol against both
Qpid Java broker and Qpid C++ broker.
With Qpid Java broker I had to switch to REST Queue creator and also specify
management parameters. The final command then looks like:
For the C++ broker I have created queues by
Hi,
I want to use performance tests which are part of the Qpid Java Broker to
measure the throughput of several brokers. I was able to configure and run
it using AMQP 0-10 protocol. However, I am struggling to make it use the
AMQP 1.0 client.
What I did:
- specified jndi-config=perftests-jndi-qpid
Hi Gordon,
I have played with the qpid.session.byte_limit and it does affect the
behavior. When I increased the limit to 1024 * 1024 * 10 I was able to send
100 messages. On the other hand, when I switched to smaller messages (1024
bytes size) and decreased the byte_limit to 1024 bytes the problem
Hi Gordon,
yes, it looks exactly like the issue described in QPID-4524. It seems
strange to me that the issue was closed with a statement - expected
behavior. I have increased the sync_op_timeout to 5 minutes, but it just
delayed the same error on the client. It is also not a store performance
pro
Hi Gordon,
I have tested qpid client 0.32 and also 6.0.2 (neither is working against
C++ server). If I use the same code (send three 1MB messages) against Java
Qpid broker, everything works. I am attaching logs, where you can see that
after sending the first message the client waits for completion
I am unable to send 1MB messages using Java JMS API to Qpid (C++ broker)
v0.34 if I use asynchronous send mode (no 'sync_publish' connection option).
First message is sent normally, but the client hangs up on second
producer.send(message) call.
If I use synchronous send mode (sync_publish='all') o
Hello Fraser,
thank you once again. I have verified that Python qmf/console.py is using
QMF v1 (as well as qpid-tool for example) and that is why I see different
(unique) ObjectIds than comparing to Java which uses QMF v2.
We will use some different mechanism on our side which is able to deal wit
Hello Fraser and thanks for an exhaustive answer.
There are still some foggy parts in this behavior for me, but let me clarify
firstly some parts which were not explained clearly from my side:
* we are connecting to the C++ Qpid broker
* we are really using asynchronous mechanism from Java QMF AP
Hi Robbie,
thank you for an extensive answer. It is clear to me now.
Michal
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Java-Qpid-Broker-flow-to-disk-tp7591254p7591439.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Hello,
I am curious what is the current state of the flow-to-disk implementation in
Java Qpid broker. Especially, what happens if there are no consumers and
cumulated size of persistent messages starts to reach the JVM memory limit.
Thank you,
Michal
--
View this message in context:
http://q
Hi all,
we have just now raised the JIRA issue: QPID-4636. The patch is attached.
Thanks. Best regards,
Michal
--
View this message in context:
http://qpid.2158936.n2.nabble.com/SSL-Client-Authentication-in-Java-broker-tp7589210p7589736.html
Sent from the Apache Qpid users mailing list archi
Hi Phil,
thank you for your answer!
Michal
--
View this message in context:
http://qpid.2158936.n2.nabble.com/JDBC-store-in-Qpid-Java-broker-tp7587432p7587525.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
Hello,
what is the current state of the support for JDBC message store in Java Qpid
broker? I do see the mention of the SQL store in Qpid documentation, but
there is no more written (just the plain page):
http://qpid.apache.org/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores.h
Hi,
we are encountering problems when using the ssl transport layer in Python
clients. When the client is sending messages in burst to the broker in
asynchronous manner (sync=False in Sender.send) the exception is
occasionally thrown with the following output:
[Errno 1] _ssl.c:1217: error:1409F07
Hello, I have extended the Jakub's patch for file based certificate client
authentication.
It is attached to the same https://issues.apache.org/jira/browse/QPID-3914
JIRA issue .
This patch extends the Jakub's one for the missing client file based
authentication under the Windows. A client may s
15 matches
Mail list logo