From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S934338AbcIUO10 (ORCPT <rfc822;w@1wt.eu>);
        Wed, 21 Sep 2016 10:27:26 -0400
Received: from mx1.redhat.com ([209.132.183.28]:42415 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1755099AbcIUO1Z (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 21 Sep 2016 10:27:25 -0400
Date: Wed, 21 Sep 2016 11:21:22 -0300
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
Message-ID: <20160921142122.GF9323@localhost.localdomain>
References: <CAFXGft+39Ed=6MDu6E9twGfhRu1yw4b=E5C8QNMQ-trxXVx08Q@mail.gmail.com>
 <20160921140426.GE9323@localhost.localdomain>
 <CAFXGft+AYwN4zkLD3d2xa=zbdj9YtRsTei6-Q+zvHFSqFqXbng@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAFXGft+AYwN4zkLD3d2xa=zbdj9YtRsTei6-Q+zvHFSqFqXbng@mail.gmail.com>
User-Agent: Mutt/1.7.0 (2016-08-17)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Wed, 21 Sep 2016 14:21:25 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Sep 21, 2016 at 10:15:43PM +0800, Sun Paul wrote:
> Hi
> 
> we are using redhat 2.6.32-642.4.2.el6.x86_64
> 
> On Wed, Sep 21, 2016 at 10:04 PM, Marcelo Ricardo Leitner
> <marcelo.leitner@gmail.com> wrote:
> > 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

Ah no, then that's another thing. If you cannot test/use an upstream
kernel, then I'd recommend you to open a support case/bug with them.

Thanks,
Marcelo