Received: (qmail 98575 invoked by uid 501); 10 Aug 2000 21:59:19 -0000 Message-Id: <20000810215919.98574.qmail@locus.apache.org> Date: 10 Aug 2000 21:59:19 -0000 From: Bernhard Haumacher Reply-To: hauix@gmx.de To: submit@bugz.apache.org Subject: Fault tolerance when initializing servlet zones in the servlet engine X-Send-Pr-Version: 3.110 >Number: 6406 >Category: mod_jserv >Synopsis: Fault tolerance when initializing servlet zones in the servlet engine >Confidential: no >Severity: critical >Priority: medium >Responsible: jserv >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: apache >Arrival-Date: Thu Aug 10 15:00:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: hauix@gmx.de >Release: Apache/1.3.12 (Unix) ApacheJServ/1.1.2 >Organization: apache >Environment: SunOS i41fs3 5.7 Generic_106541-12 sun4u sparc SUNW,Ultra-1 >Description: If there is an error in a single servlet zone initialization file, or if the classpath directory of one zone is not available, the servlet engine does not start. This is not tolerable in an environment where many users are responsible for their own servlet zones. If one of them corrupts its servlet zone properties file or deletes the classpath of his servlet zone, he corrupts the whole servlet engine. Such a scenario will make the server administrator mad. >How-To-Repeat: Add a servlet zone to jserv.properties with a properties file that does not exist, or create a zone properties file with a classpath directory that does not exist. >Fix: The servlet zones must be initialized lazily upon a request for that zone is discovered. If this initialization fails, the request fails, but other zones that are okay will still work. A nice additional feature in such a lazy zone initialization scenario would be a servlet zone status page that tells the administrator which zones are actually up and working. I'm willing to help implementing/fixing that, but I not sure, where to start. The handling of the servlet zones is handled in Java in ApacheJServ.jar? I would appreciate some advice or comment. Maybe if have overlooked something or this approach might entail some other problems. >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]