Re: [VOTE] Release Qpid JMS client 0.10.0

On 27/06/16 17:33, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.10.0 Qpid JMS client release, please test it and vote accordingly. The source and binary archives can be grabbed from here: https://dist.apache.org/repos/dist/dev/qpid/jms/0.10.0-rc1/ Those files and the othe

default SASL mech in JMS examples (was Re: [VOTE] Release Qpid JMS client 0.10.0)

On 29/06/16 13:30, Robbie Gemmell wrote: Its usiong guest:guest as those are the credentials passed to the connection factory when creating the connection. Doh! I should have realised that. Changing the example to not specify a user and password resolves the issue. Might that be a better defau

Re: [VOTE] Release Qpid Java 6.0.4 (RC1)

On 28/06/16 09:06, Keith W wrote: Hi all, A release candidate for the next release (6.0.4) of the Qpid Java Components has been created. The list of changes can be found in Jira: https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.4 Please

Re: default SASL mech in JMS examples (was Re: [VOTE] Release Qpid JMS client 0.10.0)

On 29/06/16 13:43, Robbie Gemmell wrote: I did it that way as a way of showing folks how to do authentication when creating the connection from the factory. Which is indeed valuable. I personally dislike examples using ANONYMOUS, though I can see the appeal that it avoids particular credentia

Re: Subject retention in reply-to

On 29/06/16 14:53, William Davidson wrote: I'm trying to use a subject as part of a replyTo but am seeing differing behavior between queues and topics. Using the command-line tools to send and receive a message to the same queue: qpid-send -a myqueue --reply-to "myqueue/mysubject;{node:{type:que

Re: default SASL mech in JMS examples (was Re: [VOTE] Release Qpid JMS client 0.10.0)

On 29/06/16 14:26, Robbie Gemmell wrote: On 29 June 2016 at 14:11, Gordon Sim wrote: On 29/06/16 13:43, Robbie Gemmell wrote: I personally dislike examples using ANONYMOUS, though I can see the appeal that it avoids particular credentials, and may be easier out the box for certain servers

Re: default SASL mech in JMS examples (was Re: [VOTE] Release Qpid JMS client 0.10.0)

On 29/06/16 16:52, Robbie Gemmell wrote: I think I misinterpreted your use of "predefined" earlier. I was only really considering whether I think it makes sense for a client example to use user credentials by default (I do, but also like the flexibility of your patch, so will overlook that :P), I

Re: Service Bus: unreceived messages stay locked (peek-and-lock)

On 29/06/16 12:39, Robbie Gemmell wrote: On 29 June 2016 at 11:08, Dale Green wrote: >> Closing the consumer explicitly didn't help (it's closed on session close anyway). I thought that could be the case, but just wanted you to check in case the server did something different with the explic

Re: default SASL mech in JMS examples (was Re: [VOTE] Release Qpid JMS client 0.10.0)

On 29/06/16 22:19, Robbie Gemmell wrote: As a bit of a tangent, I'm not actually the biggest fan of 'authenticatePeer: no' since it doesnt actually stop the router offering mechnisms that do authentication and then fail when used. Yes, 'requireSasl' might have been a bit more precise. Even if s

Re: Service Bus: unreceived messages stay locked (peek-and-lock)

On 29/06/16 21:50, Robbie Gemmell wrote: On 29 June 2016 at 19:43, Gordon Sim wrote: On 29/06/16 12:39, Robbie Gemmell wrote: On 29 June 2016 at 11:08, Dale Green wrote: Closing the consumer explicitly didn't help (it's closed on session close anyway). I thought that co

Re: Service Bus: unreceived messages stay locked (peek-and-lock)

On 30/06/16 15:42, Dale Green wrote: I can see that messageConsumer.close(); produces such log lines for the prefetched messages: SENT: Disposition{role=RECEIVER, first=7, last=7, settled=true, state=Released{}, batchable=false} But the same messages are still locked for the lock duration. Tha

Re: [VOTE] Release Qpid Proton 0.13.1

On 02/07/16 03:20, Justin Ross wrote: Hi, folks. Here is an RC for 0.13.1. Please test and place your vote. Source distribution: https://dist.apache.org/repos/dist/dev/qpid/proton/0.13.1-rc/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacheqpid-1082 Chang

Re: Service Bus: unreceived messages stay locked (peek-and-lock)

On 06/07/16 17:14, Dale Green wrote: I have an update on this issue. According to Microsoft, state=Released is supported and now I can confirm that this is true. If the message is released during the lifetime of the consumer (before Detach), the same message is immediately unlocked and is availa

Re: Service Bus: unreceived messages stay locked (peek-and-lock)

On 06/07/16 17:42, Gordon Sim wrote: On 06/07/16 17:14, Dale Green wrote: I have an update on this issue. According to Microsoft, state=Released is supported and now I can confirm that this is true. If the message is released during the lifetime of the consumer (before Detach), the same

Re: Service Bus: unreceived messages stay locked (peek-and-lock)

On 06/07/16 17:57, Gordon Sim wrote: On 06/07/16 17:42, Gordon Sim wrote: On 06/07/16 17:14, Dale Green wrote: I have an update on this issue. According to Microsoft, state=Released is supported and now I can confirm that this is true. If the message is released during the lifetime of the

Re: qpid-proton 0.12.2 connection_engine and ssl

On 19/07/16 10:58, Tobias Duckworth wrote: Thanks, wasn't aware of PN_TRACE_FRM, here's some output from connecting to Azure and attempting to open a receiver then sender with that tracing enabled: Address: https://TWDIoTHub.azure-devices.net:5671 [0x6dd470]: -> AMQP on_start [0x6dd470]:0 -> @

Re: [Performance] Benchmarking Qpid dispatch router 0.6.0 with Qpid Java Broker 6.0.0

On 02/08/16 18:29, Adel Boutros wrote: Were you able to check the below? Can it be some other resource is being congested in the code such as the mutex mechanism or the IO? When going through the router, all the messages will be transferred to the broker over a single connection. Are the mess

Re: [Performance] Benchmarking Qpid dispatch router 0.6.0 with Qpid Java Broker 6.0.0

On 02/08/16 19:44, Ted Ross wrote: 5.1K messages per second on a connection seems like a really low limit to me. As I recall, we were able to get closer to 80K to 100K per connection on qpidd. If these are persistent messages (which I think is the default for JMS) and the queue to which they

Re: [Performance] Benchmarking Qpid dispatch router 0.6.0 with Qpid Java Broker 6.0.0

On 02/08/16 20:18, Ted Ross wrote: Since this is synchronous and durable, I would expect the store to be the bottleneck in these cases and that for rates of ~7.5K, the router shouldn't be a factor. I don't know anything about the java broker internals, but when going through a router the messa

Re: [Performance] Benchmarking Qpid dispatch router 0.6.0 with Qpid Java Broker 6.0.0

On 02/08/16 20:25, Adel Boutros wrote: How about the tests we did with consumer/producers connected directly to the dispatcher without any broker where we had 16 000 msg/s with 4 producers. Is it also a very low value given that there is no persistence or storing here? It was also synchronous

Re: Seeing a Qpid C++ master build failure in AppVeyor

On 03/08/16 00:26, Justin Ross wrote: This problem remains for me. Unless this is shown to be my error, it blocks the C++ release. The problem appears related to code that was recently changed. https://gist.github.com/ssorj/44fcffd57075ad230ec8d221bca8e92a https://ci.appveyor.com/project/ssor

Re: Qpid dispatch router issue

On 03/08/16 13:45, eric73 wrote: Thank Ted. I set "standalone" mode for the router configuration. But now the dispatch router seems have problem when it try to connect to the broker. Indefinitely, there is a timeout error after connection: "local-idle-timeout expired". What broker are you using

Re: Qpid dispatch router issue

On 03/08/16 15:13, Robbie Gemmell wrote: ActiveMQ 5.9.0 is rather old and its AMQP 1.0 support was fairly recent at the time, its changed a lot since then. You'll want to try a newer version. 5.13.4 is the current, with 5.14.0 currently under vote for release. Yes, if I recall correctly 5.9 did

Re: Queries - Qpid Proton AMQP

On 03/08/16 12:40, Sasikumar Ramasamy wrote: Hi Folks, I am a new bee for messaging service. My need is to parse reactive messages through network using core java. I tried to implement Active-MQ and kafka, but i got messed up. I can't find semantic Tutorials/Demo regarding this. And now i just

Re: Dispatch: Default value of authenticatePeer

On 03/08/16 17:54, Robbie Gemmell wrote: On 3 August 2016 at 17:37, Jakub Scholz wrote: Hi, When I have listener configured like this: listener { role: normal host: 0.0.0.0 port: amqp saslMechanisms: PLAIN DIGEST-MD5 CRAM-MD5 linkCapacity: 1000 } Is it really expected tha

Re: Dispatch: Default value of authenticatePeer

On 03/08/16 18:23, Robbie Gemmell wrote: On 3 August 2016 at 18:08, Gordon Sim wrote: I think this is different from proton's behaviour (and from qpidd's) where the similar flags are false by default. (This is a distinct concern from the default sasl mechanisms enabled). Without

Re: Qpid dispatch router issue

On 04/08/16 07:33, eric73 wrote: Hi, Thanks, I updated my ActiveMQ broker with 5.12.3 version and it seems resolve the timeout problem. But I still have problem to send data on a topic of the broker. It worked correctly with a queue but not with a topic. - For the queue, the name is "test_queue".

Re: Dispatch: Default value of authenticatePeer

On 04/08/16 16:11, Robbie Gemmell wrote: Making authenticatePeer default to yes if a value isnt specified seems like a nice idea to me. Its specified as no in the default config file thats shipped so behaviour there wouldnt change, and having to specify it as no seems less likely to surprise folk

Re: Dispatch: Default value of authenticatePeer

On 04/08/16 21:49, Andrew Stitcher wrote: Incidentally any connection that bypasses authentication will be treated the same as if it connected using the ANONYMOUS mechanism and given user name "anonymous". I would expect that this should be used in any ACLs in force. The problem is that you mig

Re: Dispatch: Default value of authenticatePeer

On 05/08/16 19:39, Andrew Stitcher wrote: Also bear in mind that if require-auth is true then ANONYMOUS SASL will also not be allowed even if it is the negotiated mechanism. The proton code will go through the SASL negotiation and then notice that there is no authentication and close the connecti

Re: qpid-proton 0.12.2 python broker and SSL

On 08/08/16 17:37, Tobias Duckworth wrote: Hi, Quick question: Is it straightforward to run a python broker that can accept amqps (SSL/TLS) connections in qpid-proton 0.12.2? I've tried with the broker.py example, but get the following client side error on trying to connect to it: connection

Re: DISPATCH: Behavior on delivery failures

On 10/08/16 23:19, Day, Jem wrote: We’re running a dispatch-router cluster with mobile endpoints attached, the same endpoint address may be registered on multiple DR [Dispatch Router] nodes. We seem to be seeing situations where a message enters a particular DR but never gets delivered, this a

Re: SSL not working with EXTERNAL mechanism

On 11/08/16 16:24, eric73 wrote: Hi all, I’m working on a C++ project developed with Qpid libraries on Linux. I try to communicate between a qpid broker and a client base on the Qpid C++ messaging API (AMQP 1.0 protocol) with SSL connection. I use the libraries with the latest version available

Re: Is it normal to have to turn SASL off to get qpid-config and qpid-stat to work with SSL?

On 12/08/16 04:39, Jeff Donner wrote: Hi -- the only way I can get the tools qpid-config and qpid-stat to talk to qpidd (the broker) is to turn off SASL, which I do with qpidd --auth=no (.. other flags) Is it advisable / ok to do that, if you otherwise have a good, SSL dual-authentication c

Re: Is it normal to have to turn SASL off to get qpid-config and qpid-stat to work with SSL?

On 13/08/16 03:35, Jeff Donner wrote: # client ssl-best$ qpid-config --broker=amqps://jgd/donner@localhost:5671 --ssl-certificate=ssl_certs/client/tclient-certificate.pem --ssl-key=ssl_certs/tclient-unencrypted-private.key Failed: ConnectionError: connection-forced: Authentication failed(320)

Re: Is it normal to have to turn SASL off to get qpid-config and qpid-stat to work with SSL?

On 13/08/16 03:35, Jeff Donner wrote: # # Without SSL: [...] -- something's wrong with my SASL setup I feel sure, it's just whiffing at authenticating. I moved the sasldb from its original, qpid-specific location to the system's db (reflec

Re: Messenger API and ActiveMQ selector

On 14/08/16 12:10, Chenxiong Qi wrote: Hi, I'm using proton messenger API to connect ActiveMQ to produce and consumer messages. I notice that ActiveMQ supports a cool feature that is to select messages by a selector. After going through proton documentation of Python binding, I don't find inform

Re: About failover

On 15/08/16 15:52, Chenxiong Qi wrote: Hi all, I searched a lot to see if qpid.proton really does not support failover that I'm told. When I'm looking back to qpid.proton documentation, I find Container.connect method, there is a argument urls that accepts a sequence of broker urls. Is this for

Re: Exceptions at AMQP protocol

On 16/08/16 13:28, Artem wrote: I`am use Proton-J and i need to send for my client some exceptions from the AMQP server. How i can do it? I'm no expert on proton-j, but from the API doc I would suggest calling Endpoint.setCondition() then Endpoint.close() for the link/session/connection on wh

Re: Exceptions at AMQP protocol

On 16/08/16 14:20, Artem wrote: Thanks, but where user can see this ErrorCondition? That depends on the client library they are using. For example if they use qpid JMS client, or qpid.amqp_1_0.client ? I'm not very familiar with those, but the first thing I would check is that the correct

EXTERNAL not supported on windows? (was Re: SSL not working with EXTERNAL mechanism)

On 16/08/16 15:49, eric73 wrote: Hi Gordon, Thanks for you response, I have the following error: when I run the following command: Fyi, neither the command nor the error made it through in the mail I got. I was only able to read them by looking your mail up in nabble. Not sure how you are

Re: [qpdi-dispatch 0.6.0] No delivery settled or accepted when using proton-c 0.12.2

On 16/08/16 15:42, Adel Boutros wrote: Hello, It seems that when a proton::container connects to a broker to send message, 2 callbacks are called after the on_sendable sends a message "on_delivery_accept" and on_delivery_settle". When my container connects to the dispatch router which is in i

Re: SSL not working with EXTERNAL mechanism

On 16/08/16 18:04, Cliff Jansen wrote: I believe Gordon is right: only PLAIN and ANONYMOUS are supported SASL mechanisms on Windows at this time. See src/qpid/broker/windows/SaslAuthenticator.cpp Thanks for confirming, Cliff! ---

Re: SSL not working with EXTERNAL mechanism

On 17/08/16 07:21, eric73 wrote: If I want SSL with a login and a password encrypted for access, I understand that it is not possible with EXTERNAL option with QPID broker Just to clarify, EXTERNAL *is* supported on linux, just not yet on windows. but is it possible with PLAIN option ? Yes,

Re: [qpdi-dispatch 0.6.0] No delivery settled or accepted when using proton-c 0.12.2

On 17/08/16 08:18, Adel Boutros wrote: One more question: What is the equivalent in proton-c to JMS synchronous sending (MessageProducer.send())? * Is it on_sendable + on_delivery_accept? * Or on_sendable + on_delivery_accept + on_delivery_settle? In AMQP settled means the delivery is comple

Re: QPID C++ Broker and QPID Proton C++ Example interoperability problem

On 24/08/16 01:54, John McLaughlin wrote: QPID/AMPQ noob here, but I could use some help. I git-cloned the latest repos for qpid-cpp and qpid-proton. For each, I successfully built and "sudo installed" with CMake/Make using default configs. As a test, I wanted to run qpidd and an example clien

Re: Qpid dispatch router issue

On 24/08/16 12:49, lucas wrote: hi,Ted Ross. I have some questions about dispatch.I use it lasterday and I find that it's report error when I use ./qpidd and ./qdrouterd at the same time.Report As follow: warning Couldn't listen to: 0.0.0.0:5672: Can't bind to port 0.0.0.0:5672: Address a

Re: Qpid dispatch router issue

On 24/08/16 12:52, Gordon Sim wrote: On 24/08/16 12:49, lucas wrote: hi,Ted Ross. I have some questions about dispatch.I use it lasterday and I find that it's report error when I use ./qpidd and ./qdrouterd at the same time.Report As follow: warning Couldn't listen to: 0.

Re: heterogeneous federation (Qpid -> ActiveMQ)

On 25/08/16 13:07, Vince Cole wrote: Hi I'm new to Qpid and to this list, please be gentle :-) Is it possible to create a federation, in which a Qpid instance is the source broker and an ActiveMQ instance is the destination (on a remote host)? Out of the box, this doesn't appear possible becau

Re: Qpid Proton (Java) - send() method frequently hangs when sending to ActiveMQ queue

On 26/08/16 09:20, rlemmers wrote: I'm using Qpid Proton (proton-j-0.13.0) to send messages over AMQP to an ActiveMQ 5.12.0 queue. On a development machine, where ActiveMQ and the Java program run on the same machine, this is working fine. On a test environment, where ActiveMQ is running on a sep

Re: QPID C++ Broker and QPID Proton C++ Example interoperability problem

On 25/08/16 21:40, John McLaughlin wrote: I am not sure of the proper etiquette here, but I wanted to say thanks to Gordon. Most welcome, thanks for giving the QPid project a try! Building the C++ qpidd with "-Damqp_force=true" did, in fact, solve my problem. Great! --

Re: Using QPID behind HTTP proxy

On 26/08/16 11:13, rat...@web.de wrote: I am using the c++ messaging API which (I think) only supports 0-9? No, the c++ messaging API supports both 0-10 and 1.0. It does not at present support websockets however. Anyhow, it would require me to manually send the AMQP commands using websocket

Re: qpid-cpp and BerkeleyDB

On 26/08/16 12:06, Petr Kubat wrote: Hello everyone, with the license of Berkeley DB version 6 having changed to a more restrictive AGPL license, which is legally incompatible with most of the projects currently using BDB, Fedora's long term goal is to get rid of BDB completely. As qpid-cpp is o

Re: released outcome

On 26/08/16 18:50, Matt Broadstone wrote: Hi all, It was my understanding that if you replied to a received message with a `released` outcome, that the broker would attempt re-delivery to either the link that received it or some other attached link. Is that correct? That is correct. I'm not

Re: released outcome

On 26/08/16 20:18, Matt Broadstone wrote: it appears that `release` in the python client is in fact sending a `modified` outcome! Sorry! Attached is the fixed example with which I also see the expected behaviour: [0x5590136bb570]: -> SASL [0x5590136bb570]: <- SASL [0x5590136bb570]:0 <- @s

Re: released outcome

On 26/08/16 20:15, Matt Broadstone wrote: Oops you're sorry I forgot a crucial part there, here's the updated code: const amqp = require('amqp10'); let client = new amqp.Client(); client.connect('amqp://') .then(() => Promise.all([ client.createSender('test.queue'), client.createReceiv

Re: How to unbind queue and topic with C++ Message API

On 27/08/16 04:53, lucas wrote: Does "QMF framework" means qpid-config and qpid-route and so on? QMF is a management protocol layered on top of AMQP. Those tools use that protocol, but you can also sends and receive QMF messages directly from any client API. I never use anything about QMF

Re: [VOTE] Release Qpid C++ 1.35.0

On 27/08/16 00:18, Justin Ross wrote: The artifacts proposed for release: https://dist.apache.org/repos/dist/dev/qpid/cpp/1.35.0-rc/ Please indicate your vote below. If you favor releasing the 1.35.0 RC bits as 1.35.0 GA, vote +1. If you have reason to think the RC is not ready for release,

Re: released outcome

I've raised a JIRA[1] and committed a fix. Out of curiousity, what is your use case for consuming and releasing on an LVQ? [1] https://issues.apache.org/jira/browse/QPID-7406 - To unsubscribe, e-mail: users-unsubscr...@qpid

Re: released outcome

On 29/08/16 13:36, Matt Broadstone wrote: On Mon, Aug 29, 2016 at 8:31 AM, Gordon Sim wrote: I've raised a JIRA[1] and committed a fix. Oops, sorry about that. No problem, I got the JIRA just before yours, and you beat me to the list. I marked yours as a duplicate. Out of curio

Re: released outcome

On 29/08/16 13:45, Matt Broadstone wrote: Is there any chance this would make it into the release? That is a question for Justin, as the release manager. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For addition

Re: Qpid Proton (Java) - send() method frequently hangs when sending to ActiveMQ queue

On 28/08/16 19:53, rlemmers wrote: *jstack didn't help:* /usr/lib/jvm/java/bin/jstack -J-d64 -m 32444 Attaching to process ID 32444, please wait... Debugger attached successfully. Server compiler detected. JVM version is 24.91-b01 Exception in thread "main" java.lang.reflect.InvocationTargetExcep

Re: How to unbind queue and topic with C++ Message API

On 30/08/16 10:13, lucas wrote: Thank you very much!Sim. I have compiled and run your code and I find that working when I call function controller.bind(), but it seems doesn't work when I call controller.unbind(I qpif-config add a queue and exchange,then bind them.I want to see if controller.unbi

Re: How to unbind queue and topic with C++ Message API

On 30/08/16 10:40, lucas wrote: I am so sorry that I have annotated some code before when I test the unbind() function.It's work both now.Thank for your help and examples. Can you please tell me where can I find these information about "Variant::Map"、“encode”、“decode”? https://qpid.apache.org/r

Re: Qpid Proton (Java) - send() method frequently hangs when sending to ActiveMQ queue

On 30/08/16 16:19, rlemmers wrote: Regarding "Do you have to use the messenger API? Could you use JMS instead?" Would it be a better choice to use JMS, instead of the messenger API? In my opinion, yes, much better. If so, why would that be better? The proton based JMS client at Qpid is acti

Re: [VOTE] Release Qpid C++ 1.35.0

On 30/08/16 18:31, Chuck Rolke wrote: +1 with some reluctance. I had a hard time getting the self tests to pass. Using the same build with Proton 0.14 on Linux 4.6.7-200.fc23.x86_64. * Running from home office with VPN and kerberos 'make test' would run for hours and fail randomly. Several te

Re: Python support for AMQP 1.0?

On 31/08/16 18:00, Volker Diels-Grabsch wrote: Dear Qpid developers, My Python program needs to receive messages from an AMQP 1.0 server. Which library or combination of libraries do I need? In other words, how is a Python program meant to communicate with an AMQP 1.0 server? My first attempt

Re: Python support for AMQP 1.0?

On 31/08/16 18:26, Volker Diels-Grabsch wrote: Dear Qpid developers, My Python program needs to receive messages from an AMQP 1.0 server. Which library or combination of libraries do I need? In other words, how is a Python program meant to communicate with an AMQP 1.0 server? My first attempt

Re: Python support for AMQP 1.0?

On 01/09/16 09:29, Volker Diels-Grabsch wrote: So I have to switch from a pure-Python implementation to a C library with Python wrapper. This is inconvenient for deployment, but not a show stopper for me. I compiled qpid-proton on my own, where some questions arose: 1) Is it possible to build

Re: Python support for AMQP 1.0?

On 01/09/16 13:44, Ken Giusti wrote: - Original Message - From: "Gordon Sim" To: users@qpid.apache.org Sent: Thursday, September 1, 2016 8:32:15 AM Subject: Re: Python support for AMQP 1.0? On 01/09/16 09:29, Volker Diels-Grabsch wrote: So I have to switch from a p

Re: Questions: Next Receiver Functionality

On 01/09/16 17:52, Flores, Paul A. wrote: Hi, Working at a client site and have run into an interesting question. The current implementation plan is to use a unique "reply to" address (queue) to handle synchronous request reply. At this point we have a local broker so we have a single conne

Re: [VOTE] Release Qpid JMS client 0.11.0

On 05/09/16 16:47, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.11.0 Qpid JMS client release, please test it and vote accordingly. +1 (verified signature, compiled and ran tests, ran helloworld example against both brokers, the router and the proton python broker.py exam

Re: Question: Queue Disposition

On 07/09/16 16:00, Flores, Paul A. wrote: Circumstance: A process creates a queue with a unique address to mimic synchronous processing configuring the queue so it is deleted the instance the Receiver is closed, creates a Receiver for the specific queue, sends a message with the unique "reply

Re: Receiver fetch mybey block forever

On 09/09/16 06:39, 634749...@qq.com wrote: hello! I use the c++ broker and c++ client api(version 0.34);the broker running on centos,and the client on windows server 2008; if the network is not stability between client and broker , I found the receive fetch() function maybe block forever. eg：

Re: qpid session thread safe

On 12/09/16 13:41, 634749...@qq.com wrote: HI! Now I use the c++ API for version 0.34, but I have some questions about session; I create one receive and one sender by the same session,so is it thread safe to send message and fetch message in different thread? Yes.

Re: some questions about Receiver get() and fetch() function

On 09/09/16 06:36, 634749...@qq.com wrote: hello! I use the c++ broker and c++ client api(version 0.34),Now I have some question about Receiver funtion fetch and get; call example: Session session; Receiver receiver; receive = session.createReceiver(); receive.se

Re: SASL configuration from a string?

On 12/09/16 21:43, Alan Conway wrote: It looks like Proton requires SASL configuration to come from a named file. I believe that requirement comes from cyrus-sasl, rather than proton itself. This is bad, because it assumes a) there is a file system and b) the proton app deployer can modify it

Re: [QPID C++][Java JMS client] Data gets corrupted when sent to the server over SSL

On 16/09/16 12:39, Morgan Lindqvist wrote: Hi all, I have an issue that data gets corrupted if the size is 66068 but not if it is 65068 or smaller when using the JavaJMS client. The server is QPIC C++ and SSL encryption is used. If I instead use a Node JS based client I have no issues with the

Re: building qpid cpp 0.30 from source

On 19/09/16 16:08, Vince Cole wrote: Hi It fails, with the following error pn_delivery_tag_t has no member named ‘bytes’ I assume this is due to a version mismatch, between qpid 0.30 and some other installed library (I guess its likely to be proton-c or proton-cpp, or one of their devel packa

Re: building qpid cpp 0.30 from source

On 19/09/16 16:22, Robbie Gemmell wrote: The initial cmake step outputs a message if you are using a newer version of proton than was marked as tested at the time of the cpp bits being released, also detailing which version was. Given the age of the 0.30 release, it looks like it was Proton 0.7 i

Re: Help! ->qpid::Exception what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116)

On 19/09/16 21:51, Flores, Paul A. wrote: Hi, At client site. Performing unit tests and seeing: terminate called after throwing an instance of 'qpid::Exception' what(): Invalid argument (../include/qpid/sys/posix/Mutex.h:116) Aborted Pops up when ~Connection() is called. The destructo

Re: async send message blocked forever

On 20/09/16 09:04, 634749...@qq.com wrote: HI: I user the c++ broker(verison 0.34) and the c++ API on windows,but I found the send() function of sender maybe blocked forever, I did not start the flow stop,and send message async; example code: Sender sender = session.createSender(address

Re: async send message blocked forever

On 20/09/16 09:39, 634749...@qq.com wrote: thanks! the message is not large, the depth of the queue information flowed: The stack trace looks like the sender is waiting for confirmation of previously sent messages. As the broker is

Re: Dispatch Router "qdstat -a" clarifying the definition of "phs"

On 28/09/16 13:20, Adel Boutros wrote: Hello, In the output of qdstat when querying addresses (qdstat -a), there is a field called "phs". Checking the documentation it seems to be related to the phases of an address. If I understand correctly, there are 2 phases: * 0: For a consumer receivi

Re: link delivery priority

On 29/09/16 15:43, Matt Broadstone wrote: I'm trying to set up two concurrent receiver links on the same broker: one to listen to messages from a queue (e.g. `test.queue`) as a consumer/worker, another to listen to the same queue but with a distribution mode of `copy` in order to passively track

Re: [Dispatch router 0.6.1] Configuration bugs

On 30/09/16 08:59, Adel Boutros wrote: Hello, As a follow up to my previous thread, I am having some issues with the dispatch router. I will start with the first one here: It seems the "name" attribute doesn't work for all types of entities. So, I cannot delete them using the "name" attribu

Re: Qpid client 1.35 arm v7

On 06/10/16 16:57, xavier wrote: Hi all, I have a curious behavior, with qpid messaging + qpid proton (I used the latest version from https://launchpad.net/~qpid/+archive/ubuntu/testing) (built for debian by my obs) I use activemq (latest version 5.14) amqp 1.0. On my linux distribution (debian

Re: Qpid C++ broker - --no-data-dir and linearstore

On 07/10/16 15:29, Justin Ross wrote: https://gist.github.com/ssorj/d32f619dcf1cb0a462bf95a97b907cad I think this behavior is new since 0.34. It strikes me as wrong that the broker won't start - when I've explicitly selected --no-data-dir - if I have the linearstore module in the modules dir.

Re: High CPU usage (~100%) with Proton Python

On 24/10/16 23:44, Ryan Pessa wrote: I’m having issues with proton consuming a lot of CPU, at or close to 100% of a core. This is with an exchange which is mostly silent (1 health message, around 200-300 bytes, sent every 30 seconds), and happening with python-qpid-proton==0.14.0 on both OS X 10.

Re: qpid-cpp-1.35 broker crashed with resource-limit-exceeded

On 24/10/16 22:10, rammohan ganapavarapu wrote: Yes, looks like my system went out of memory and killed qpidd, i have restarted broker with trace log level, lets see if i can reproduce the issue. [45527559.740820] Out of memory: Kill process 8311 (qpidd) score 176 or sacrifice child [45527559.74

Re: How, from within a C++ application, is it possible to 'examine' and 'manage' a broker?

On 25/10/16 15:22, Flores, Paul A. wrote: Hi, As the subject line states: "How, from within a C++ application, is it possible to 'examine' and 'manage' a broker?" It depends which broker you are using. The c++ broker uses a message based management protocol (called QMF). The java broker has

Re: qpid monitoring tool in GO

On 28/10/16 16:56, Andrew Stitcher wrote: If you go to godoc.org and search for AMQP there, you won't find the electron library anywhere near the top of the list. If you search for AMQP 1.0 you get nothing, so we should add that to the text somehow. That way at least those who know about diffe

Re: Possible thread sync error in proton/qpid-cpp

On 02/11/16 19:38, Chris Richardson wrote: Hi, As per the subject I'm experiencing a crash which I am _reeaasonably_ sure I've pinpointed to a problem with one of the C/C++ Qpid client libraries. Of course I could also be doing something goofy in which case I apologise profusely! No, it is ind

Re: Possible thread sync error in proton/qpid-cpp

On 02/11/16 19:38, Chris Richardson wrote: As per the subject I'm experiencing a crash which I am _reeaasonably_ sure I've pinpointed to a problem with one of the C/C++ Qpid client libraries. I've checked in a couple of fixes that address the issues: https://issues.apache.org/jira/browse/QPID-

Re: Qpid Proton SSL and SNI

On 14/11/16 14:18, Ulf Lilleengen wrote: I've been playing around with setting Server Name Indication (SNI) when using the qpid proton python bindings. For configuring SSL, it seems to be expected that configuration parameters come from a SSLDomain python object, which maps to the underlying pn

Re: [VOTE] Release Qpid Dispatch Router 0.7.0 (RC2)

On 10/11/16 18:26, Ted Ross wrote: I have built RC2 for Qpid Dispatch Router 0.7.0. Please give it a test and cast your votes. The build artifacts can found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.7.0-rc2/ The list of issues resolved is here: +1 -

Re: Valid values for x-declare, x-subscribe, x-binding?

On 18/11/16 20:29, Gary Taylor wrote: In the docs, located at https://qpid.apache.org/releases/qpid-0.32/programming/book/section-addresses.html there are tables(for example: 2.3 - Link Properties) that have defintions for the items in $subject. One example: x-declare - A nested map whose values

Re: C++ Broker --worker-threads option

On 21/11/16 13:25, Gregory Simpson wrote: Hi, I am trying to get a better understanding of what the C++ broker --worker-threads option does. The Linux man pages says that this parameter "Sets the broker thread pool size" so I believed that when this is set to a higher number then performance sho

Re: Understanding Topics and Queues association with Exchanges

On 01/12/16 18:46, James Franco wrote: I am trying to wrap my head around the association of topics and queues with an exchange. Here is my understanding so far (please correct me if I am wrong). In the end I have a question . Point 1: Whenever we create a queue by default it is under the defaul

Re: Understanding Topics and Queues association with Exchanges

On 01/12/16 20:18, James Franco wrote: Thanks for the reply Gordon , so another question that I had regarding the same topic was about the hello world example and how it is functioning ? In that example , we have a message producer and a consumer the producer sends a message to the default topic

  1   2   3   4   5   6   7   8   9   10   >