Thanks, Steve! It works now. Much appreciated!
Calvin
--
View this message in context:
http://n2.nabble.com/SSL-and-C-client-anyone-have-a-complete-example-tp4030718p4724859.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
-
Ah, looks like this is fixed on the trunk already.
Though looking at that code it fails to throw an error if
all sessions have been used and simply silently goes on.
- Ron
Friday, March 12, 2010, 2:28:28 PM, you wrote:
> Okay, I've found the bug. It's a wrap around issue.
> void ConnectionImp
Okay, I've found the bug. It's a wrap around issue.
void ConnectionImpl::addSession(const boost::shared_ptr& session,
uint16_t channel)
{
Mutex::ScopedLock l(lock);
session->setChannel(channel ? channel : nextChannel++);
boost::weak_ptr& s = sessions[session->getChannel()];
boost:
Hi Calvin,
The Windows SSL support is via built-in SSL support in Windows, not via
NSS as the Linux version is. So the Windows certificate handling is
used.
Try this...
On your Windows system, start IE (not another browser) and connect to
:5671 (assuming your broker is listening for SSL on
port
If I am not mistaken, SSL support is still being developed on the windows side.
Steve Huston who is working on that could provide you with a more
detailed update.
On Fri, Mar 12, 2010 at 3:15 PM, Calvin Lee <73bo...@riva-networks.com> wrote:
>
> Hi,
>
> I am trying to build my c++ windows client w
Hi,
I am trying to build my c++ windows client with ssl using qpid 0.7. And I
am getting this NSS 5938 error from the qpidd daemon. I was able to get the
c++ client on Linux to work. I just have to specify ssl-cert-db in the
qpidc.conf file. What is the equivalent on Windows? Does anyone hav
If you give me a patched build in RPM form I'll test it for you.
On Mar 12, 2010, at 11:50 AM, Kim van der Riet wrote:
Thanks for the detail. I had thought that you had suffered a recover
failure in which a phase 1 recover had failed - ie the ability of the
store to analyze the stored messages
Thanks for the detail. I had thought that you had suffered a recover
failure in which a phase 1 recover had failed - ie the ability of the
store to analyze the stored messages from the disk owing to some sort of
disk corruption or similar. But much of the detail here is as you have
already describe
Sure. As I mentioned, I was running a test where I shut down the
consumers and enqueued large amounts of data. I was running these
tests in ec2 in a store and forward (src-local queue route) topology.
The local s&f broker had a small-ish (10 GB) store and a single
durable queue with a de
Kim,
Thank you for your detailed follow up. Sounds like qpid basically
does what I want. We have no such inter-queue dependencies.
Actually, I think I read somewhere that this question about how to
handle policy when a message is delivered across multiple queues was
the result of a gap
Guys,
I've been using QPID successfully for a few months now, however once
in a while my program terminates with this exception:
terminate called after throwing an instance of
'qpid::framing::SessionBusyException'
what(): session-busy: Channel 3 attached to
guest.50e08be0-d1f6-4c43-8b81-
Hi,
I'm working on the Windows installer for Qpid 0.6. During the 0.5 -> 0.6
development cycle the build system changed to cmake-generated projects
and along with that I put the additions in place to generate the Windows
installer via Cpack which has built-in support for NSIS-based
installers. The
On Thu, 2010-03-11 at 18:53 -0800, Charles Woerner wrote:
> Wow, and nevermind. As I wrote that the queue stats updated and
> apparently the link was re-established and the entire contents of the
> store and forward queue were now flushed to the destination broker
> properly. Seems to work
On Thu, 2010-03-11 at 13:13 -0800, Charles Woerner wrote:
> Thanks Kim,
>
> 1) I'm using qpid from RedHat MRG 0.5.752581-34 for i386 and the store
> module is RHM 0.5.3206-27, also for i386.
Thanks, this is the most recent set.
>
> 2) Yes, my messages are persistent. I am aware that transien
14 matches
Mail list logo
