Re: QPID QMF and QPID-TOOLS

2016-01-20 Thread Stein Wang
Thank you so much, Ted! I tried your instruction this morning, and I got most of the information I need. I haven't got all the methods I can call on these objects, and I have to explore more. If you have some tutorials on this, it would be great!:) Do you have any idea about my other questions? I

Re: spurious ABRT in qpidd

2016-01-20 Thread Matt Broadstone
On Wed, Jan 20, 2016 at 9:58 PM, Matt Broadstone wrote: > On Wed, Jan 20, 2016 at 8:31 PM, Matt Broadstone > wrote: > >> On Wed, Jan 20, 2016 at 6:52 PM, Matt Broadstone >> wrote: >> >>> On Wed, Jan 20, 2016 at 6:10 PM, Matt Broadstone >>> wrote: >>> On Tue, Jan 12, 2016 at 8:39 AM, Matt

Re: spurious ABRT in qpidd

2016-01-20 Thread Matt Broadstone
On Wed, Jan 20, 2016 at 8:31 PM, Matt Broadstone wrote: > On Wed, Jan 20, 2016 at 6:52 PM, Matt Broadstone > wrote: > >> On Wed, Jan 20, 2016 at 6:10 PM, Matt Broadstone >> wrote: >> >>> On Tue, Jan 12, 2016 at 8:39 AM, Matt Broadstone >>> wrote: >>> On Tue, Jan 12, 2016 at 5:08 AM, Gordo

Re: spurious ABRT in qpidd

2016-01-20 Thread Matt Broadstone
On Wed, Jan 20, 2016 at 6:52 PM, Matt Broadstone wrote: > On Wed, Jan 20, 2016 at 6:10 PM, Matt Broadstone > wrote: > >> On Tue, Jan 12, 2016 at 8:39 AM, Matt Broadstone >> wrote: >> >>> On Tue, Jan 12, 2016 at 5:08 AM, Gordon Sim wrote: >>> On 01/11/2016 09:29 PM, Matt Broadstone wrote:

Re: spurious ABRT in qpidd

2016-01-20 Thread Matt Broadstone
On Wed, Jan 20, 2016 at 6:10 PM, Matt Broadstone wrote: > On Tue, Jan 12, 2016 at 8:39 AM, Matt Broadstone > wrote: > >> On Tue, Jan 12, 2016 at 5:08 AM, Gordon Sim wrote: >> >>> On 01/11/2016 09:29 PM, Matt Broadstone wrote: >>> Looks like I did just get a valid assertion, but I'm not eve

Re: spurious ABRT in qpidd

2016-01-20 Thread Matt Broadstone
On Tue, Jan 12, 2016 at 8:39 AM, Matt Broadstone wrote: > On Tue, Jan 12, 2016 at 5:08 AM, Gordon Sim wrote: > >> On 01/11/2016 09:29 PM, Matt Broadstone wrote: >> >>> Looks like I did just get a valid assertion, but I'm not even clear >>> anymore >>> whether this is related to the initially rep

Re: Setting log level on running broker

2016-01-20 Thread Chris Richardson
Hi Chuck, Unfortunately that's only partially true - while the Logger.cpp changes were indeed released in qpid-cpp-0.34, the python file changes are key to this functionality and are part of the qpid-tools package, which has not been released since version 0.32. What I'm after is a 0.34 release of

Re: Setting log level on running broker

2016-01-20 Thread Gordon Sim
On 01/20/2016 09:39 PM, Chuck Rolke wrote: Alan's commit db7b30e was released in qpid-cpp-0.34 July, 2015. That didn't include the tools though, I don't think. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For a

Re: Setting log level on running broker

2016-01-20 Thread Chuck Rolke
Alan's commit db7b30e was released in qpid-cpp-0.34 July, 2015. Further improvements to that file by Ken are in commit 2d9f712 on trunk. They have not been in a formal release. - Original Message - > From: "Chris Richardson" > To: "users" > Sent: Wednesday, January 20, 2016 12:21:41 PM

Re: Setting log level on running broker

2016-01-20 Thread Chris Richardson
That looks perfect (and much more aesthetically pleasing than my version). Can we have an official release soon? On 20 January 2016 at 17:12, Gordon Sim wrote: > On 01/20/2016 05:05 PM, Chris Richardson wrote: > >> Hi, >> >> It would be really nice to have a command-line method for setting the >

Re: Setting log level on running broker

2016-01-20 Thread Gordon Sim
On 01/20/2016 05:05 PM, Chris Richardson wrote: Hi, It would be really nice to have a command-line method for setting the log level on a running broker (c++), as discussed here: http://grokbase.com/t/qpid/users/11bxbmbxq3/set-log-level The suggested solution with qpid-ctrl tool does work, but s

Setting log level on running broker

2016-01-20 Thread Chris Richardson
Hi, It would be really nice to have a command-line method for setting the log level on a running broker (c++), as discussed here: http://grokbase.com/t/qpid/users/11bxbmbxq3/set-log-level The suggested solution with qpid-ctrl tool does work, but since this is, as mentioned in the article, a test

Re: Several issues with the Java Broker

2016-01-20 Thread Rob Godfrey
On 20 January 2016 at 13:33, Gordon Sim wrote: > On 01/20/2016 12:53 PM, Rob Godfrey wrote: > >> There is no single point where "it is fully configured for use" in the >> case >> of HA a virtual host may transition from a REPLICA state to a MASTER state >> (or vice versa) at any time, >> > > In t

Re: QPID QMF and QPID-TOOLS

2016-01-20 Thread Ted Ross
On 01/20/2016 09:25 AM, Stein Wang wrote: Hi, I am trying to get some information from the broker via either QMF or qpid-tools. The broker is established with ssl requirement and client authentication requirement, with three files, namely, a certificate file, a key file, and a trust file. Here

QPID QMF and QPID-TOOLS

2016-01-20 Thread Stein Wang
Hi, I am trying to get some information from the broker via either QMF or qpid-tools. The broker is established with ssl requirement and client authentication requirement, with three files, namely, a certificate file, a key file, and a trust file. Here are the questions I have when I tried to get

Re: Several issues with the Java Broker

2016-01-20 Thread Gordon Sim
On 01/20/2016 12:53 PM, Rob Godfrey wrote: There is no single point where "it is fully configured for use" in the case of HA a virtual host may transition from a REPLICA state to a MASTER state (or vice versa) at any time, In the case of transferring from MASTER to REPLICA, simply dropping the

Re: getTtl() behaviour (C++ messaging API)

2016-01-20 Thread Gordon Sim
On 01/20/2016 12:29 PM, Toralf Lund wrote: On 19/01/16 17:01, Gordon Sim wrote: The value reported for received messages is that value that was written to the wire by the peer (e.g. the broker). The receiving client does not reduce this value in anyway after the message has been decoded. So, in

Re: Several issues with the Java Broker

2016-01-20 Thread Rob Godfrey
On 20 January 2016 at 12:11, Gordon Sim wrote: > On 01/20/2016 10:48 AM, Rob Godfrey wrote: > >> What I get from this is that the C++ client gives up retrying when it gets >> a 320 (connection forced) reply from the broker. >> > > Indeed, the retry gives up when it gets an explicit close rather t

Re: getTtl() behaviour (C++ messaging API)

2016-01-20 Thread Toralf Lund
On 19/01/16 17:01, Gordon Sim wrote: On 01/19/2016 02:19 PM, Toralf Lund wrote: Hi, I have some questions about the value from qpid::messaging::Message::getTtl() on received messages; based on testing, I've concluded that 1. The value returned represents the time that remains of the time-to

Re: Several issues with the Java Broker

2016-01-20 Thread Gordon Sim
On 01/20/2016 10:48 AM, Rob Godfrey wrote: What I get from this is that the C++ client gives up retrying when it gets a 320 (connection forced) reply from the broker. Indeed, the retry gives up when it gets an explicit close rather than the socket failing. As Keith mentioned earlier, the er

Re: Heartbeating - Java broker

2016-01-20 Thread Rob Godfrey
Can you send a protocol trace? Thx, Rob On 20 January 2016 at 11:03, rat...@web.de wrote: > Hi, > I'm having a problem to find out how heartbeating exactly works for the > java > broker (or how to enable it). > Via the http management I configured the broker to have a "heartbeat delay" > of 5s

Re: Several issues with the Java Broker

2016-01-20 Thread Rob Godfrey
On 18 January 2016 at 22:59, Keith W wrote: > Hello > > On 17 January 2016 at 18:34, rat...@web.de wrote: > > << snip >> > > > 2.) Message user-Id > > Using the java broker, the client seems to be able to set any user id. > > However, the broker does not seem to reject messages with wrong user

Heartbeating - Java broker

2016-01-20 Thread rat...@web.de
Hi, I'm having a problem to find out how heartbeating exactly works for the java broker (or how to enable it). Via the http management I configured the broker to have a "heartbeat delay" of 5s (this was the only option I could find to somehow enable heartbeating). My test client connects also with

Re: Several issues with the Java Broker

2016-01-20 Thread Rob Godfrey
What I get from this is that the C++ client gives up retrying when it gets a 320 (connection forced) reply from the broker. As Keith mentioned earlier, the error message is basically saying "Yes, the broker is up... but it isn't fully configured yet", and the 320 error code (as defined by the AMQP

Re: Several issues with the Java Broker

2016-01-20 Thread rat...@web.de
Ok, I was able to produce a protocol trace with trace+ The situation is as follows: First the client is started. The broker is not active and thus the client is trying to reconnect. Then, after a while, I start the broker. When the broker is almost booted completely, the client receives the corresp