On 09/22/2011 01:23 AM, Daryoush Mehrtash wrote:
Does this means, even if I install the store module, I would not be able to
send a reliable message (as in exactly once).
Correct, at present there is no built in support for exactly-once
guarantees. You can get at-least-once and then
Do I need to have the store module installed to get the at-least-once
behavior?
daryoush
On Thu, Sep 22, 2011 at 12:20 AM, Gordon Sim g...@redhat.com wrote:
On 09/22/2011 01:23 AM, Daryoush Mehrtash wrote:
Does this means, even if I install the store module, I would not be able
to
send a
On 09/22/2011 08:34 AM, Daryoush Mehrtash wrote:
Do I need to have the store module installed to get the at-least-once
behavior?
Depends on what sorts of failures you wish to tolerate. If you want to
be able to recover a crashed broker including all durable
messages/queues, then yes.
On 09/22/2011 05:07 AM, Brandon Pedersen wrote:
So I got NSS working correctly now and have imported the CA
certificate used for the servers cert into the database. However, when
I start up the broker I still get an error initializing the plugin:
Failed to load certificate 'hostname'
I guess
So the only two choices I have are unreliable vs at-least-once. Would
choosing one or the other influence the network traffic?I like to know
whether I will see more or less packets on the wire if I choose
at-least-once vs unreliable? If so, any idea how much that overhead might
be?
Thanks,
Hmmm... RHEL 5 is g++ 4.1.2. Maybe there's a 4.3.4 issue with boost - I
haven't had cause to investigate that before.
Maybe it would be a good idea to open a jira for this and place needed info
there, as well as any patches needed.
-Steve
-Original Message-
From: Ohme, Gregory (GE
- In C++ it is fairly common to use std::string as a container for
binary
data. I would not say it is wrong to do that.
I agree with all your points here.
OK guys I see I appear to be in a minority here, so please indulge me.
What's the case for saying that using std::string as a
Hi David,
I think it's only the Java broker that exposes JMX attributes at the
moment.
When I (eventually - hopefully next couple of weeks if I don't get
distracted!!) get the Java QMF2 API done I'm hoping that'll be a good
starting point for exposing QMF2 Management Objects as MBeans.
I
On Sep 22, 2011 7:37 PM, Fraser Adams fraser.ad...@blueyonder.co.uk
wrote:
What's the case for saying that using std::string as a container for
binary data is a good idea? Just because it's common doesn't make
necessarily make it a great thing. To me it seems inappropriate and there
are other
I had the same problem, and then I realized I wasn't linking against to
necessary boost libraries. Remember, qpid relies on boost libraries, so
every time you compile a Qpid program, it's likely that you'll also link it
against the boost libraries, not just qpid libraries. Hopefully that's the
10 matches
Mail list logo
