commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Griffiths (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DAEMON-177) Allow fail during init
Date Sat, 09 Oct 2010 11:18:31 GMT

     [ https://issues.apache.org/jira/browse/DAEMON-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nick Griffiths updated DAEMON-177:
----------------------------------

    Attachment: remove-fail-available-check.diff

removes the check for isAvailable in fail, to allow failing during init.

> Allow fail during init
> ----------------------
>
>                 Key: DAEMON-177
>                 URL: https://issues.apache.org/jira/browse/DAEMON-177
>             Project: Commons Daemon
>          Issue Type: Improvement
>    Affects Versions: 1.0.3
>         Environment: linux
>            Reporter: Nick Griffiths
>            Priority: Minor
>             Fix For: 1.0.4
>
>         Attachments: remove-fail-available-check.diff
>
>
> It would be handy to be able to fail with a nice message during init, such as 'database
not available' or 'no config file found' or whatever.
> At the moment, if you try that during init, you get an IllegalStateException.  I've attached
a patch which removes this restriction in DaemonLoader, but failing at this stage doesn't
stop the c code from calling start.  I could work around this in the DaemonLoader, but not
sure that is the right approach.  I'll have a go at doing a patch for the c-code, but I'm
not a confident in my c skills...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message