Re: two processes listening on same port

[Trustin Lee <tr...@gmail.com>]

On 8/28/07, Adam Fisk <a...@lastbamboo.org> wrote:
> Linux should do the same thing, and it's actually a very important feature.
> A lot of protocols rely on this behavior, such as both TCP and UDP NAT
> traversal.
>
> That said, I'm unclear why so many of the examples use setReuseAddress,
> although I think I remember Trustin saying it improved performance in his
> tests.  Not sure why that would be the case, but it could be the reason.

It was because there was a critical bug related with setReuseAddress
in MINA.  It's been resolved, so any call to setReuseAddress should be
removed.  It's not related with performance but related with failing
tests due to the reuse address bug.  We couldn't figure out why the
tests are failing, so simply enabled reuseAddress.  Now we don't need
to do so, either.

The bottom line is that any unnecessary setReuseAddress(true) should
be removed from  MINA source code repository.

Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6

Re: two processes listening on same port

[Mark <el...@gmail.com>]

I updated the quick start guide.  Updates should be visible in the next hour
or so.

On 9/5/07, hezjing <he...@gmail.com> wrote:
>
> Do you think we should remove setReuseAddress(true) from the Quick Start
> Guide?
> see http://mina.apache.org/quick-start-guide.html
>
> On 9/3/07, Trustin Lee <tr...@gmail.com> wrote:
> > On 8/28/07, Adam Fisk <a...@lastbamboo.org> wrote:
> > > Linux should do the same thing, and it's actually a very important
> feature.
> > > A lot of protocols rely on this behavior, such as both TCP and UDP NAT
> > > traversal.
> > >
> > > That said, I'm unclear why so many of the examples use
> setReuseAddress,
> > > although I think I remember Trustin saying it improved performance in
> his
> > > tests.  Not sure why that would be the case, but it could be the
> reason.
> >
> > It was because there was a critical bug related with setReuseAddress
> > in MINA.  It's been resolved, so any call to setReuseAddress should be
> > removed.  It's not related with performance but related with failing
> > tests due to the reuse address bug.  We couldn't figure out why the
> > tests are failing, so simply enabled reuseAddress.  Now we don't need
> > to do so, either.
> >
> > The bottom line is that any unnecessary setReuseAddress(true) should
> > be removed from  MINA source code repository.
> >
> > Trustin
> > --
> > what we call human nature is actually human habit
> > --
> > http://gleamynode.net/
> > --
> > PGP Key ID: 0x0255ECA6
> >
>
>
> --
>
> Hez
>



-- 
..Cheers
Mark

Re: two processes listening on same port

[hezjing <he...@gmail.com>]

Do you think we should remove setReuseAddress(true) from the Quick Start Guide?
see http://mina.apache.org/quick-start-guide.html

On 9/3/07, Trustin Lee <tr...@gmail.com> wrote:
> On 8/28/07, Adam Fisk <a...@lastbamboo.org> wrote:
> > Linux should do the same thing, and it's actually a very important feature.
> > A lot of protocols rely on this behavior, such as both TCP and UDP NAT
> > traversal.
> >
> > That said, I'm unclear why so many of the examples use setReuseAddress,
> > although I think I remember Trustin saying it improved performance in his
> > tests.  Not sure why that would be the case, but it could be the reason.
>
> It was because there was a critical bug related with setReuseAddress
> in MINA.  It's been resolved, so any call to setReuseAddress should be
> removed.  It's not related with performance but related with failing
> tests due to the reuse address bug.  We couldn't figure out why the
> tests are failing, so simply enabled reuseAddress.  Now we don't need
> to do so, either.
>
> The bottom line is that any unnecessary setReuseAddress(true) should
> be removed from  MINA source code repository.
>
> Trustin
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
> --
> PGP Key ID: 0x0255ECA6
>


-- 

Hez