Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 14 Jul 2016 07:42:20 +0000 (UTC)
From: "Anton Vinogradov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12917997.1449146213000.25575.1468482140763@Atlassian.JIRA>
In-Reply-To: <JIRA.12917997.1449146213000@Atlassian.JIRA>
References: <JIRA.12917997.1449146213000@Atlassian.JIRA> <JIRA.12917997.1449146213205@arcas>
Subject: [jira] [Comment Edited] (IGNITE-2079) GridCacheIoManager eats
 exception trail if it falls into the directed case
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 14 Jul 2016 07:42:22 -0000


    [ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376508#comment-15376508 ] 

Anton Vinogradov edited comment on IGNITE-2079 at 7/14/16 7:41 AM:
-------------------------------------------------------------------

Andrey,

1) Please follow https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules, eg {{GridKernalContext cont}} is not correct.
Please recheck all code
2) Some examples of wrong formating:
No new line required:
 {noformat}+            @Override public boolean apply(Event event) {
 +
 +                UnhandledExceptionEvent uex = (UnhandledExceptionEvent)event;{noformat}

New line required 
{noformat}   GridCacheQueryMetricsAdapter metr = (GridCacheQueryMetricsAdapter)jcache(0).queryMetrics();
 +                    return metr.fails() == 1 && metr.executions() == 1 && unhandledExceptionCounter.intValue() == 1;{noformat}
3) What's about 
{noformat}Possible, we have to add put from another node and handle it
jcache(1).put(testKey2, "value2");{noformat}? Can we do that?


was (Author: avinogradov):
Andrey,

1) Please follow https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules, eg {{GridKernalContext cont}} is not correct.
Please recheck all code
2) Some examples of wrong formating:
No new line required:
 {noformat}+            @Override public boolean apply(Event event) {
 +
 +                UnhandledExceptionEvent uex = (UnhandledExceptionEvent)event;{noformat}

New line required 
{nofornat}   GridCacheQueryMetricsAdapter metr = (GridCacheQueryMetricsAdapter)jcache(0).queryMetrics();
 +                    return metr.fails() == 1 && metr.executions() == 1 && unhandledExceptionCounter.intValue() == 1;{noformat}
3) What's about 
{noformat}Possible, we have to add put from another node and handle it
jcache(1).put(testKey2, "value2");{noformat}? Can we do that?


> GridCacheIoManager eats exception trail if it falls into the directed case
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-2079
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2079
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Anton Vinogradov
>            Assignee: Andrey Velichko
>              Labels: ignite-3424
>             Fix For: 1.7
>
>         Attachments: IgniteCacheP2pUnmarshallingContinuousQueryErrorTest.java
>
>
> During a recent test I have run into an issue where a storage disabled client of a Fabric that has services deployed for which the client does not have the fabric in the class path failed with the following exception:
> com.company.fabric.HelloWorldTest STANDARD_ERROR
> Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to process message [senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to node. Unsupported direct type [message=GridCacheQueryResponse [finished=true, reqId=5, err=null, fields=false, metadata=null]]
>  at org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
>  at org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
>  at org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
>  at org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
>  at org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
>  at org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
>  at org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
>  at org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
>  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  at java.lang.Thread.run(Thread.java:745)
> This unfortunately gives me 0 information to work on to resolve the issue, as the original unmarshalling exception (from the JdkMarshaller) was eaten as this is the code for the default process failed message:
>             default:
> throw new IgniteCheckedException("Failed to send response to node. Unsupported direct type [message="
> + msg + "]");
> }
> you should also include the original stack from msg.getError() in the newly thrown IgniteCheckedException


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)