On 01/08/2015 03:06 PM, Gordon Sim wrote:
On 01/08/2015 02:56 PM, Hamid.Shahid wrote:
Thanks Gordon,
But is it better to use /message.setContent(msgString)/ or to use
/message.setContentObject(msgString)/?
Use Message::setContentObject(). If you use setContent() the data will
be sent as a seq
On Mon, Jan 12, 2015 at 01:34:03PM -0500, Ken Giusti wrote:
>
> +1
>
> Built/installed/ran unit tests on Centos 7 x64.
> Set up a two node configuration and sent oslo.messaging traffic over it - all
> good.
I created DISPATCH-96 for the install issue I've come across.
--
Darryl L. Pierce, Sr
Strange,
I just changed the timeout from Duration::FOREVER to Duration(4000)
but it still waits for the message forever, no exception is thrown
in 4 seconds...
> Hallo,
>
> I am reading the messages from the queue as follows:
>
>Receiverr(_session.nextReceiver());
>Message messa
Hallo,
I am reading the messages from the queue as follows:
Receiverr(_session.nextReceiver());
Message message(r.fetch(Duration::FOREVER d));
At some moment I want to interrupt the receiver using some signal.
>From signal handler I invoke pthread_kill(SIGUSR1, pthread_self())
but
+1
Built/installed/ran unit tests on Centos 7 x64.
Set up a two node configuration and sent oslo.messaging traffic over it - all
good.
- Original Message -
> From: "Ted Ross"
> To: users@qpid.apache.org
> Sent: Friday, January 9, 2015 1:19:18 PM
> Subject: [VOTE] Approve Qpid Dispatch
dispatch_0_3 ++ ; // ship it!
I am using this candidate with my Topologist
client -- sending management queries to get all
topology info for the network. And -- it's working!
- Original Message -
For folks who have tested the release candidate for Qpid Dispatch Router at
