DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34199.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34199
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID |
--- Additional Comments From [EMAIL PROTECTED] 2005-04-21 09:42 ---
Thank you for showing me the option -nodetach.
Unfortunately I cannot use this in a normal startup script because as you write,
jsvc is then not started as a deamon. Therefore I have to re-open this bug.
What would be required, and that is what I perceive the same as what Apache
httpd provides (I may be wrong), is this:
Under RedHat Linux, if Apache httpd has an error on startup, then it returns
with a return code != 0.
If it doesn't have an error, then it returns with a return code = 0.
And this all happens while the httpd blocks until the startup is completed and
at the same time httpd is started as a daemon.
I don't know whether this is possible with jsvc. jsvc returns correct codes, for
example, with an invalid command line parameter. But it does not return correct
codes if the Java program crashes on initialisation. I would think that jsvc
should return errors for anything that goes wrong until the end of the
initialisation. I understand that the purpose of jsvc is to start a java program
and when it is started, to call its init() method. So there are two
opportunities for failure, and in both cases, error codes should be returned.
As far as I can guess, jsvc returns too early before the init() method is
completed, which complicates the matter (separate bug 34140).
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
