On Windows QPID uses Microsoft SChannel, and you can manage the available
protocols on a system-wide basis through the registry. You should disable
SSLv3 and enable TLS 1.1 and 1.2 to defend against POODLE attack...
On Fri, Mar 20, 2015 at 9:02 AM, Filipe Santos
wrote:
> Hi everyone
>
> Does an
Thx, I was using the 0.24 tag, should have checked trunk. Appreciate the
help, I'll ping if I run into any issues!
On Thu, Nov 21, 2013 at 12:59 PM, Andrew Stitcher wrote:
> On Thu, 2013-11-21 at 12:37 -0600, Kerry Bonin wrote:
> > I didn't see
> /home/gordon/projects/
I didn't see
/home/gordon/projects/qpid-svn-trunk/cpp/src/qpid/broker/management-schema.xml
in the svn repo, where else could I look for it? thx...
On Wed, Nov 20, 2013 at 8:05 AM, Gordon Sim wrote:
> On 11/20/2013 01:33 PM, Kerry Bonin wrote:
>
>> Thanks! I'm absolu
ok for the best
documentation that does exist?
On Wed, Nov 20, 2013 at 4:19 AM, Gordon Sim wrote:
> On 11/19/2013 11:09 PM, Kerry Bonin wrote:
>
>> Hello! I was just about to look them over, as I need access to queue
>> loads
>> on the brokers. If you are considering
Hello! I was just about to look them over, as I need access to queue loads
on the brokers. If you are considering deprecating them, what would be the
recommended way to access QMF data from the broker in a C++ client app?
Kerry Bonin
On Tue, Nov 19, 2013 at 3:08 PM, Ken Giusti wrote:
>
I was just considering wasting a bunch of time (building test frameworks)
to figure out an answer to this same question - I'm hoping someone has a
good answer!
On Fri, Jun 14, 2013 at 1:22 PM, Connor Poske <
connor.po...@onrampwireless.com> wrote:
> I have a tangential question(s) regarding perf
On Windows machines, the broker looks for a certificate with the FQDN of
the server machine, by default in the "my" store under the LocalSystem
account. If the machine is on a domain, this will include the full domain
name. The clients MUST use this same FQDN to connect to the broker (as the
unde
Hello Hamid! Just a note on this, as I'm using Windows + SSL. At the
least you'll want to apply the patch in QPID-4257 <
https://issues.apache.org/jira/browse/QPID-4257> - use the later version by
Chuck Rolke as it fixes a case I missed in my first patch. We're still
seeing some issues in our la
We haven't seen this on any other of the ~ 60 other machines we're testing
on yet, I posted my comment only after noticing someone else reporting an
unexpected SSL error a few hours apart from my unexpected SSL error, but
we're working on other issues and monitoring carefully to see if this
appears
I just saw SSL stop working on one of my dev systems which is set to
automatically install updates.
MMC shows my server cert as valid in the "my" store, QPIDD comes up without
error and states its listening for SSL, but clients trying to connect via
SSL now hang and the broker reports "2012-08-29
We're using it in several enterprise class projects over several product
lines. Unfortunately we primarily deploy only on Windows platforms, which
are treated as something of a second class citizen in the current (*nix
dominated) developer community. Our biggest problems were broker fault
toleran
Actually, using an explicit call to Session::hasError() is the only way I've
found to expose some client library state data. I wish the library had
callbacks for message receipt and state changes (broker connection lost,
broker failover to <>), coupled with a nice signal-slot library we could
simp
We are experiences some issues with failover (reports that not all clients
are failing over on primary broker failure), and would like to know if there
is any way from the client library API to know when a failover occurs and to
which broker the failover has occurred?
On a related note, is there a
FWIW, we have a group here using it (the Python API) in a production
system (along with the C++ API), although they did have various
complaints, primarily around the lack of an callback model for the
messaging API.
On Thu, Jul 15, 2010 at 5:03 AM, Chris Howard
wrote:
> Thanks for the information
14 matches
Mail list logo
