Re: The un-reactor

2015-10-26 Thread Ken Giusti
- Original Message - > From: "aconway" > To: users@qpid.apache.org > Sent: Monday, October 26, 2015 12:23:01 PM > Subject: Re: The un-reactor > > On Thu, 2015-10-22 at 22:03 -0700, Cliff Jansen wrote: > > I'm not sure if this exactly fits your question (especially the > > multi-threaded

Re: The un-reactor

2015-10-26 Thread Gordon Sim
On 10/26/2015 04:23 PM, aconway wrote: Proton is an AMQP protocol engine it is not a general purpose IO and event handling framework. I see the value of proton providing a simple IO framework for isolated proton projects when there is nothing else available. But if you already use tornado, epoll,

Re: Error recovery in qpidd / proton communication

2015-10-26 Thread aconway
On Thu, 2015-10-22 at 22:20 +0300, Michael Ivanov wrote: > Thanks for the advice, > > I am using messenger in passive mode integrating it into select > -driven > event loop. Mayxbe reactor would be more appropriate, but I have > checked > the proton api documentation and al reactor functions are r

Re: The un-reactor

2015-10-26 Thread aconway
On Thu, 2015-10-22 at 22:03 -0700, Cliff Jansen wrote: > I'm not sure if this exactly fits your question (especially the > multi-threaded part), but the python tornado loop examples run a > regular reactor set of events and collectors but driven by the > external loop. > > pn_iohandler is replaced

Re: Broker federation with SSL client auth and SASL EXTERNAL

2015-10-26 Thread Chris Richardson
On 19 October 2015 at 15:37, Gordon Sim wrote: > On 10/17/2015 01:36 AM, Chris Richardson wrote: > >> Hi, >> >> I'm attempting to set up a broker federation topology using purely SSL >> client authentication and the EXTERNAL SASL mechanism on qpid-cpp 0.34. >> This seems to be within an iota of w

Re: Qpid JMS - Idle timeout / inactivity handling

2015-10-26 Thread Robbie Gemmell
On 26 October 2015 at 10:44, Erik Aschenbrenner wrote: > Ok, so sending heartbeats from the client is working automatically when the > broker requested it. > > Thanks, > Erik > Yes thats correct, if the broker advertises an idle-timeout value to the client then it will automatically send heartbea

Re: Qpid JMS - Idle timeout / inactivity handling

2015-10-26 Thread Erik Aschenbrenner
Ok, so sending heartbeats from the client is working automatically when the broker requested it. Thanks, Erik -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-Idle-timeout-inactivity-handling-tp7632838p7632840.html Sent from the Apache Qpid users mailing list archive

Re: Qpid JMS - Idle timeout / inactivity handling

2015-10-26 Thread Robbie Gemmell
On 26 October 2015 at 10:14, Erik Aschenbrenner wrote: > Dear Qpid-Users, > > I'm using the Qpid JMS (0.6.0). The provider of the service my client > application connects to has informed me that it has changed it's message > plattform from JBoss A-AMQ 6.1 to A-MQ 6.2: > > /Please note AMQ 6.2 come

Qpid JMS - Idle timeout / inactivity handling

2015-10-26 Thread Erik Aschenbrenner
Dear Qpid-Users, I'm using the Qpid JMS (0.6.0). The provider of the service my client application connects to has informed me that it has changed it's message plattform from JBoss A-AMQ 6.1 to A-MQ 6.2: /Please note AMQ 6.2 comes with an automatic heartbeat / connectivity monitoring built in [h