[jira] [Closed] (JAMES-2996) Guice end up in zombie state when start fail

["Benoit Tellier (Jira)" <se...@james.apache.org>]

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

Benoit Tellier closed JAMES-2996.
---------------------------------
    Fix Version/s: 3.5.0
       Resolution: Won't Fix

If start fails, calling stop might generate more error and makes diagnostic harder.

That is dcalling context responsibility in case of error to sigterm James.

> Guice end up in zombie state when start fail
> --------------------------------------------
>
>                 Key: JAMES-2996
>                 URL: https://issues.apache.org/jira/browse/JAMES-2996
>             Project: James Server
>          Issue Type: Bug
>          Components: guice
>    Affects Versions: 3.4.0
>            Reporter: Benoit Tellier
>            Priority: Major
>             Fix For: 3.5.0
>
>
> Currently when an error arise:
>  - the exception is not catched and logged in stderr
>  - James is started despite some failed components, and the initialization is not completed
> I would expect:
>  - that an error upon start leave the app in a clean stopped state
>  - that the error is logged using slf4j in order to be caught by proper monitoring tools



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org