www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kris Kocan <kris_ko...@ibm.net>
Subject mod_jserv/5447: JServ does not shutdown when using bind address other than 127.0.0.1
Date Thu, 09 Dec 1999 20:18:21 GMT

>Number:         5447
>Category:       mod_jserv
>Synopsis:       JServ does not shutdown when using bind address other than 127.0.0.1
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Dec  9 12:20:01 PST 1999
>Last-Modified:
>Originator:     kris_kocan@ibm.net
>Organization:
apache
>Release:        1.3.9 + 1.1b3
>Environment:

Problem occurs both on:
Redhat 6.1 and Blackdown JDK 1.2.2 AND 
NT 4.0 with Sun JDK 1.2.2 
>Description:

The signal() method in JServ.java always attempts to connect to JServ
at 127.0.0.1 and does not use the address specified in the configuration
file.

A server in manual mode listening on another address cannot be
shutdown.  When the shutdown command is issued, the program
running the shutdown command throws an exception (JServ.java:485)
because it cannot connect to the server at that address.

A workaround, of course, is to use 127.0.0.1 as the bind address but
this isn't practical for all environments.
connet

>How-To-Repeat:

Reproduce the problem by starting a JServ server on an address other
than 127.0.0.1 and have the server in Manual mode.

Try issuing the shutdown command and notice the exception thrown.
>Fix:

On line 487 of JServ.java we have:
  socket = new AuthenticatedSocket("127.0.0.1", port, new MD5(), s
ecret);

And on line 493 we have:
  socket = new AuthenticatedSocket("127.0.0.1", port);

For both cases, I believe we need to replace "127.0.0.1" with
defaultHostName where
       String defaultHostName = confs.getString("bindaddress"); 
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]




Mime
View raw message