I think that is a good idea ... but it's a little tricky to implement. The place where we throw these exceptions is holding locks that would prevent closing the cache - so we would need to through the exception and then handle it higher up in all of the APIs that could trigger a this exception.
Practically speaking I think users won't be handling these exceptions - they will occur as part of starting up the cache server process. That process will exit as soon as the cache is closed. [ Full content available at: https://github.com/apache/geode/pull/3145 ] This message was relayed via gitbox.apache.org for [email protected]
