We're encountering a problem mainly on Athena. We're using specific ports, and calling the close(socketID); when the socket is not needed anymore. We where getting problems when for example .. loading the server, closing it, and then loading it again getting a bind error. So we ran netstat -an and found out that the port was still visible there marked as 'TIME_WAIT'.
Is someone encountering the same problem? And if yes, what are we doing wrong, and how should we fix it?
Hi, I was discussing the same problem with other people. It seems that when you close a port, it still remains 'activated' for a short amount of time (it's something regarding the TCP/IP connection). Best thing to do,if you used for eample port 1,change the ne*t try to port 2.Don't rely on my post though, cause I am just replying what they told me and I may have misunderstood their answer.
Hi guys... this is a limitation of sockets... if you want to make the socket instantly available again, change the socket options to with the REUSADDR option set to 1.
It's covered in APUE
On 13/05/07, agius....@gmail.com <agius....@gmail.com> wrote:
> Hi, > I was discussing the same problem with other people. It seems that > when you close a port, it still remains 'activated' for a short amount > of time (it's something regarding the TCP/IP connection). Best thing > to do,if you used for eample port 1,change the ne*t try to port > 2.Don't rely on my post though, cause I am just replying what they > told me and I may have misunderstood their answer.
> Hi guys... this is a limitation of sockets... if you want to make the > socket instantly available again, change the socket options to with > the REUSADDR option set to 1.
> It's covered in APUE
> On 13/05/07, agius....@gmail.com <agius....@gmail.com> wrote:
> > Hi, > > I was discussing the same problem with other people. It seems that > > when you close a port, it still remains 'activated' for a short amount > > of time (it's something regarding the TCP/IP connection). Best thing > > to do,if you used for eample port 1,change the ne*t try to port > > 2.Don't rely on my post though, cause I am just replying what they > > told me and I may have misunderstood their answer.
> On May 13, 8:12 pm, "Stefan Camilleri" <szc...@gmail.com> wrote: > > Hi guys... this is a limitation of sockets... if you want to make the > > socket instantly available again, change the socket options to with > > the REUSADDR option set to 1.
> > It's covered in APUE
> > On 13/05/07, agius....@gmail.com <agius....@gmail.com> wrote:
> > > Hi, > > > I was discussing the same problem with other people. It seems that > > > when you close a port, it still remains 'activated' for a short amount > > > of time (it's something regarding the TCP/IP connection). Best thing > > > to do,if you used for eample port 1,change the ne*t try to port > > > 2.Don't rely on my post though, cause I am just replying what they > > > told me and I may have misunderstood their answer.
> > On May 13, 8:12 pm, "Stefan Camilleri" <szc...@gmail.com> wrote: > > > Hi guys... this is a limitation of sockets... if you want to make the > > > socket instantly available again, change the socket options to with > > > the REUSADDR option set to 1.
> > > It's covered in APUE
> > > On 13/05/07, agius....@gmail.com <agius....@gmail.com> wrote:
> > > > Hi, > > > > I was discussing the same problem with other people. It seems that > > > > when you close a port, it still remains 'activated' for a short amount > > > > of time (it's something regarding the TCP/IP connection). Best thing > > > > to do,if you used for eample port 1,change the ne*t try to port > > > > 2.Don't rely on my post though, cause I am just replying what they > > > > told me and I may have misunderstood their answer.
|
