Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
From: Niclas Hedhman <niclas@hedhman.org>
To: "Apache Directory Developers List" <directory-dev@incubator.apache.org>
Subject: Re: [GUMP@brutus]: Project apseda (in module apseda) failed
Date: Mon, 31 Jan 2005 22:39:59 +0800
User-Agent: KMail/1.7.1
References: 
 <20050131094010.CWRC2041.imf15aec.mail.bellsouth.net@minotaur.apache.org>
 <41FE3685.8000309@bellsouth.net>
In-Reply-To: <41FE3685.8000309@bellsouth.net>
Cc: bodewig@apache.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200501312239.59748.niclas@hedhman.org>

On Monday 31 January 2005 21:45, Alex Karasulu wrote:

> In the meantime, I want to try to get GUMP all cleared up.  It's
> starting to become irritating but then again that's its job :).  In the
> worst case we can just blow away the darn test case but before we do
> that let's see if this can be fixed.

Full testcase output is found here.
http://brutus.apache.org/gump/public/apseda/apseda/gump_file/TEST-org.apache.apseda.examples.DiscardProtocolProviderTest.txt.html

ConnectException: Connection Refused


Unfortunately, I don't have root access to Brutus, so I don't know if there 
are any iptables restrictions at the port level. (Stefan might be able to 
check, or know who can check?)


Cheers
Niclas