Received: (qmail 12833 invoked from network); 16 Jan 1999 23:14:43 -0000
Message-Id: <36A11D5D.3132C3A5@snet.net>
Date: Sat, 16 Jan 1999 18:14:37 -0500
From: Nick Brazziel <dbrazziel@snet.net>
To: Apache Bugs <apbugs@Apache.Org>
Subject: Subject: JServ 1.0b1 not (fully) running.

>Number:         3694
>Category:       pending
>Synopsis:       Subject: JServ 1.0b1 not (fully) running.
>Confidential:   yes
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Class:          sw-bug
>Submitter-Id:   unknown
>Arrival-Date:   Sat Jan 16 15:20:00 PST 1999
>Last-Modified:  Sat Jan 16 17:32:15 PST 1999
>Originator:     
>Organization:
>Release:        
>Environment:
>Description:
>How-To-Repeat:
>Fix:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Sat Jan 16 17:32:15 PST 1999
State-Changed-Why:
Closing misfiled PR; you need to use the same subject
as the original when following up.
>Unformatted:
The workaround is to start JServ manually (set ApjServManual on in
httpd.conf).
It seems that the ServerSocket construction doesn't specify an IP
address even if
the default (localhost) is in effect for ApjServDefaultHost.  This
causes the IP address for the socket to be 0.0.0.0.  I don't know where
the SocketException is coming from, but I looked at
AuthenticatedServerSocket, which seems to be called by
Jserv, which actually seems to be issuing the error message.