You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Mikhail Cherkasov (JIRA)" <ji...@apache.org> on 2018/07/26 17:45:00 UTC

[jira] [Created] (IGNITE-9099) IgniteCache java doc does not cover all possible exceptions

Mikhail Cherkasov created IGNITE-9099:
-----------------------------------------

             Summary: IgniteCache java doc does not cover all possible exceptions
                 Key: IGNITE-9099
                 URL: https://issues.apache.org/jira/browse/IGNITE-9099
             Project: Ignite
          Issue Type: Bug
            Reporter: Mikhail Cherkasov


IgniteCache java doc does not cover all possible exceptions.

 

For example on if try to close cache after node stop there would be the following exception:

 
org.apache.ignite.IgniteException: Failed to execute dynamic cache change request, node is stopping.
        at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:986)
        at org.apache.ignite.internal.util.future.IgniteFutureImpl.convertException(IgniteFutureImpl.java:168)
        at org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:137)
        at org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.close(GatewayProtectedCacheProxy.java:1346)
 
However, API for close method doesn't mention any exception at all.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)