[
https://issues.apache.org/jira/browse/GEODE-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787890#comment-16787890
]
ASF subversion and git services commented on GEODE-6492:
--------------------------------------------------------
Commit 008930774c2479cc460dfee91cf131c7908d0eff in geode's branch
refs/heads/develop from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0089307 ]
GEODE-6492: Ensure that starting HttpService can fail gracefully in the face of
errors (#3275)
- If the HttpService (or war deployment) fails, simply log a warning
message and continue.
- Add a simple gradle building test which ensures that 'geode-core' is
the only module required to start a basic Cache.
> Geode should fail gracefully if the HttpService cannot be started
> -----------------------------------------------------------------
>
> Key: GEODE-6492
> URL: https://issues.apache.org/jira/browse/GEODE-6492
> Project: Geode
> Issue Type: Bug
> Components: configuration, management
> Reporter: Jens Deppe
> Assignee: Jens Deppe
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Previously, starting our various webapps, would simply be dependent on the
> presence of the .war file. Anyone building and testing a Geode would
> typically not care whether theses additional services were available and
> would not notice their absence.
> Now we have a new {{HttpService}} which will attempt to start regardless of
> the presence of any .war files. This now also implies that various jetty jars
> need to be available. When building with maven or gradle, the necessary
> dependencies are marked as {{optional}} which means that a vanilla built app
> (configured without those optional dependencies) will not start.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
