From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Sun Paul <paulrbk@gmail.com>
Cc: linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Address already in use problem
Date: Wed, 21 Sep 2016 14:04:26 +0000 [thread overview]
Message-ID: <20160921140426.GE9323@localhost.localdomain> (raw)
In-Reply-To: <CAFXGft+39Ed=6MDu6E9twGfhRu1yw4b=E5C8QNMQ-trxXVx08Q@mail.gmail.com>
Hi,
On Wed, Sep 21, 2016 at 09:44:30PM +0800, Sun Paul wrote:
> Hi
>
> we have an SCTP application running in JAVA. and we found that there
> is a problem when we as a client trying to connect to a remote IP
> address.
>
> If the remote IP address is not accessible, our application will keep
> retrying to connect using a self-defined local port address, says
> 51001,
>
> We found that after sometimes, says 2 hrs, this port 51001 is never
> able to bind to us again. even we tried to restart the application.
>
> Is there anyone know how we can resolve this?
Which kernel are you using? Depending on it, that may be fixed by a
recent patchset from Xin Long, 'sctp: fix the transmit err process'
patchset more exactly.
Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Sun Paul <paulrbk@gmail.com>
Cc: linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Address already in use problem
Date: Wed, 21 Sep 2016 11:04:26 -0300 [thread overview]
Message-ID: <20160921140426.GE9323@localhost.localdomain> (raw)
In-Reply-To: <CAFXGft+39Ed=6MDu6E9twGfhRu1yw4b=E5C8QNMQ-trxXVx08Q@mail.gmail.com>
Hi,
On Wed, Sep 21, 2016 at 09:44:30PM +0800, Sun Paul wrote:
> Hi
>
> we have an SCTP application running in JAVA. and we found that there
> is a problem when we as a client trying to connect to a remote IP
> address.
>
> If the remote IP address is not accessible, our application will keep
> retrying to connect using a self-defined local port address, says
> 51001,
>
> We found that after sometimes, says 2 hrs, this port 51001 is never
> able to bind to us again. even we tried to restart the application.
>
> Is there anyone know how we can resolve this?
Which kernel are you using? Depending on it, that may be fixed by a
recent patchset from Xin Long, 'sctp: fix the transmit err process'
patchset more exactly.
Marcelo
next prev parent reply other threads:[~2016-09-21 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 13:44 Address already in use problem Sun Paul
2016-09-21 13:44 ` Sun Paul
2016-09-21 14:04 ` Marcelo Ricardo Leitner [this message]
2016-09-21 14:04 ` Marcelo Ricardo Leitner
2016-09-21 14:15 ` Sun Paul
2016-09-21 14:15 ` Sun Paul
2016-09-21 14:21 ` Marcelo Ricardo Leitner
2016-09-21 14:21 ` Marcelo Ricardo Leitner
2016-09-21 17:28 ` Xin Long
2016-09-21 17:28 ` Xin Long
2016-09-21 15:43 ` Neil Horman
2016-09-21 15:43 ` Neil Horman
2016-09-21 15:56 ` David Laight
2016-09-21 16:12 ` Neil Horman
2016-09-21 16:12 ` Neil Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160921140426.GE9323@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=paulrbk@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.