From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757393AbcIUOEc (ORCPT ); Wed, 21 Sep 2016 10:04:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47256 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755967AbcIUOE3 (ORCPT ); Wed, 21 Sep 2016 10:04:29 -0400 Date: Wed, 21 Sep 2016 11:04:26 -0300 From: Marcelo Ricardo Leitner To: Sun Paul Cc: linux-sctp@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Address already in use problem Message-ID: <20160921140426.GE9323@localhost.localdomain> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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.25]); Wed, 21 Sep 2016 14:04:29 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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