s,
>
>
>
> Dennis Qin
>
>
>
> *From:* Lahiru Gunathilake [mailto:glah...@gmail.com]
> *Sent:* Thursday, December 09, 2010 6:56 PM
> *To:* users@qpid.apache.org
> *Cc:* Faruqui, Faisal; Ramalingam, Saravanan; Kuo, Jennshi; Harpalani,
> Manish; Qin, Dennis
&g
cember 09, 2010 6:56 PM
To: users@qpid.apache.org
Cc: Faruqui, Faisal; Ramalingam, Saravanan; Kuo, Jennshi; Harpalani, Manish;
Qin, Dennis
Subject: Re: qpid C++ memory leak
Hi Dennis,
First it was a mistake I mention about Java broker, I am talking about C++
broker. You can easily monitor wheth
Hi Dennis,
First it was a mistake I mention about Java broker, I am talking about C++
broker. You can easily monitor whether messages are consuming or not by
using python tools[1] provided in qpid and see whether incoming messages are
consumed.
[1]
http://www.lahiru.org/2010/12/how-to-monitor-and
Hi Lahiru,
Thanks for the reply. But I was just using the examples code coming from
qpid package. Also I was running against C++ broker, not Java. For your
convenience, I have attached the source code of the server and client
programs with this email. They are located in the
"qpidc-0.8/examples/r
Hi Dennis,
As far as I can see you are simply sending large number of messages to Qpid
Java broker but not consuming any of the messages. So obviously memory will
grow unless you consume those messages since you are running without
persistent storage.
I recently did stress test with Qpid C++ brok
Hi All,
I have downloaded the Linux version of qpid C++ broker 0.8 on my Linux
appliance. I ran some stress tests on this broker server and found memory
leaks. Here is the simple test I did.
1. Launch the C++ broker using the following CLI,
./src/qpid --daemon
2. Launch the serve
