ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kukushkin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-10074) Structured Exception information is lost when Ignite .NET client calls Ignite Java service
Date Tue, 30 Oct 2018 23:45:00 GMT
Alexey Kukushkin created IGNITE-10074:

             Summary: Structured Exception information is lost when Ignite .NET client calls
Ignite Java service
                 Key: IGNITE-10074
                 URL: https://issues.apache.org/jira/browse/IGNITE-10074
             Project: Ignite
          Issue Type: Improvement
          Components: platforms
    Affects Versions: 2.6
            Reporter: Alexey Kukushkin

Suppose an Ignite service in Java throws *new ModelVerificationException(“ERROR!”)* to
signal about a failure.

An Ignite.NET client of such a Java service would receive this exception:

 * *Message*: Proxy method invocation failed with an exception. Examine InnerException for
 * *InnerException*: Apache.Ignite.Core.Common.IgniteException

o   *Message*: ERROR!

o   *InnerException*: Apache.Ignite.Core.Common.JavaException
 * *JavaClassName*: class org.apache.ignite.IgniteCheckedException
 * *JavaMessage*: ERROR!
 * *InnerException*: null
 * *Message*: class org.apache.ignite.IgniteCheckedException: ERROR!
               at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7332)
               at org.apache.ignite.internal.processors.platform.services.PlatformServices$ServiceProxyHolder.invoke(PlatformServices.java:589)
               at org.apache.ignite.internal.processors.platform.services.PlatformServices.processInObjectStreamOutObjectStream(PlatformServices.java:289)
               at org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inObjectStreamOutObjectStream(PlatformTargetProxyImpl.java:172)
Caused by: ModelVerificationException: ERROR!
               at ... 

Ignite service wraps the custom ModelVerificationException in a IgniteCheckedException,
which we get information for on the client side. There is no structured information about
the custom exception in the client.

We need to have information about the custom exception on the client.

This message was sent by Atlassian JIRA

View raw message