mod_jserv/5092: JServServletManager defaults not conform zone.properties + log bug + fixes

[Aart de Vries <ad...@iae.nl>]

>Number:         5092
>Category:       mod_jserv
>Synopsis:       JServServletManager defaults not conform zone.properties + log bug + fixes
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Oct  2 01:50:00 PDT 1999
>Last-Modified:
>Originator:     advries@iae.nl
>Organization:
apache
>Release:        1.3.9 + 1.1b1
>Environment:
Suse Linux 6.1, kernel 2.1.12 Java: blackdown 1.2pre1
>Description:
All bugs in this report are in file JServServletManager. Fixes are included, and
indicated per row as rXXX
**************
To start with the log bug:
r260: "jserv.log.log(CH_INFO,"Destroy timeout: "+this.initTimout+...."
should be this.destroyTimeout!!!
**************
Timout defaults for init and destroy according to zone.properties defaults
should be 10 secs. In JservServletManager they default to 7 secs.
Change 7000 -> 10000 (and 7 secs. to 10 secs. in comment) in rows:
r96, r103, r247, r248
**************
I also encountered a more serious bug:
In one of my servlet zones I have a startup servlets that really takes long to
init. So I set the init.timeout to 30secs. In JServServletManager I saw that
the init.timeout still has to be implemented (r544 on your TODO). But 
implementing this won't help. I tracked down the java-side of JServ, and 
currently due to the TODO there is no timeout. However my servlets gets inited
about every 10 secs. I suspect that the c-side gets impationed and restarts
the JServ java side every 10 secs. or so. I'm not a C programmer, and I can 
only spent some time next week on this problem (and on a suggestion for the
TODO).
>How-To-Repeat:
No need to repeat, bugs found in source, see "Full description"
>Fix:
Description given in "Full description".
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@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!     ]