We have not yet compiled proton with libuv so I might not be that straightforward for us.
I hope the new I/O will work easily because I have already around 7 patches for 0.7.0 and I am at 27% compilation. Regards, Adel ________________________________ From: Ted Ross <tr...@redhat.com> Sent: Friday, January 20, 2017 3:58:51 PM To: users@qpid.apache.org Subject: Re: [Dispatch Router] Unexpected behavior when starting the same dispatch router twice You should be aware that Alan Conway is working on converting the Dispatch I/O layer to use Proton proactor and libuv. This might make the port to Solaris (and Windows) much easier. -Ted On 01/20/2017 09:54 AM, Adel Boutros wrote: > I hope by that time I will have finished porting Dispatch Router to Solaris > and submitted my patches. There have been a lot of changes since the last > time we tried to compile 0.5 on Solaris :( > > > Regards, > > Adel > > ________________________________ > From: Ted Ross <tr...@redhat.com> > Sent: Friday, January 20, 2017 2:50:49 PM > To: users@qpid.apache.org > Subject: Re: [Dispatch Router] Unexpected behavior when starting the same > dispatch router twice > > Actually, we haven't settled on a schedule for 0.8.0 yet. There are 90 > issues assigned to 0.8.0 with 11 currently not resolved. > > I think mid-to-late February would be a good timeframe for this release. > > -Ted > > On 01/20/2017 08:39 AM, Ganesh Murthy wrote: >> 0.8 is expected to come out around mid February. >> >> ----- Original Message ----- >>> From: "Adel Boutros" <adelbout...@live.com> >>> To: users@qpid.apache.org >>> Sent: Friday, January 20, 2017 8:31:40 AM >>> Subject: Re: [Dispatch Router] Unexpected behavior when starting the same >>> dispatch router twice >>> >>> Thanks Ted! >>> >>> >>> Is 0.8 expected to come out soon? >>> >>> >>> Regards, >>> >>> Adel >>> >>> ________________________________ >>> From: Ted Ross <tr...@redhat.com> >>> Sent: Friday, January 20, 2017 2:06:24 PM >>> To: users@qpid.apache.org >>> Subject: Re: [Dispatch Router] Unexpected behavior when starting the same >>> dispatch router twice >>> >>> Adel, >>> >>> This was raised as a Jira >>> (https://issues.apache.org/jira/browse/DISPATCH-55) and has been >>> resolved for 0.8.0. There's some discussion captured on that issue. >>> >>> The short answer is: Yes, the second start should fail. >>> >>> -Ted >>> >>> On 01/20/2017 03:45 AM, Adel Boutros wrote: >>>> Hello, >>>> >>>> >>>> I was messing around with the Dispatch Router and noticed a weird behavior. >>>> >>>> >>>> If I start the dispatch router with a config file a first time, the broker >>>> is started correctly and is available. >>>> >>>> If I start the same dispatch router a second time with the same config >>>> file, it doesn't fail but in the logs it says the address is already bound >>>> but it continues processing the config file. >>>> >>>> >>>> Do you confirm that the second start should crash the dispatch router? >>>> >>>> >>>> Logs on starting second dispatch router >>>> >>>> ---------------------------------------------------- >>>> >>>> Fri Jan 20 09:40:58 2017 DRIVER (error) bind: Address already in use >>>> Fri Jan 20 09:40:58 2017 AGENT (debug) Add entity: >>>> ListenerEntity(addr=0.0.0.0, authenticatePeer=False, cost=1, >>>> host=127.0.0.1, identity=listener/127.0.0.1:10501, idleTimeoutSeconds=16, >>>> maxFrameSize=16384, port=10501, requireEncryption=False, requireSsl=False, >>>> role=normal, saslMechanisms=ANONYMOUS, stripAnnotations=both, >>>> type=org.apache.qpid.dispatch.listener) >>>> Fri Jan 20 09:40:58 2017 POLICY (info) Policy configured >>>> maximumConnections: 0, policyFolder: '', access rules enabled: 'false' >>>> Fri Jan 20 09:40:58 2017 AGENT (debug) Add entity: >>>> Entity(defaultApplication=, defaultApplicationEnabled=False, >>>> enableAccessRules=False, maximumConnections=0, policyFolder=, >>>> type=org.apache.qpid.dispatch.policy) >>>> .... >>>> >>>> >>>> Regards, >>>> >>>> Adel >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org >>> For additional commands, e-mail: users-h...@qpid.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org >> For additional commands, e-mail: users-h...@qpid.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
