[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1275#comment-1275 ] Dmitriy Govorukhin commented on IGNITE-2079: I see, thanks for review, in future i will try do not make mistakes in Codestyle. > 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: Dmitriy Govorukhin > Labels: ignite-3424 > Fix For: 1.8 > > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1192#comment-1192 ] Anton Vinogradov commented on IGNITE-2079: -- Dmitry, I've checked and refactored your changes (Codestyle fixed and Test refactored) Please review my changes. > 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: Dmitriy Govorukhin > Labels: ignite-3424 > Fix For: 1.8 > > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1186#comment-1186 ] Dmitriy Govorukhin commented on IGNITE-2079: [~avinogradov] Hi Anton, could you please review my changes. > 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: Dmitriy Govorukhin > Labels: ignite-3424 > Fix For: 1.8 > > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15430684#comment-15430684 ] Andrey Velichko commented on IGNITE-2079: - Please make review changes. Pull request https://github.com/apache/ignite/pull/940 > 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.8 > > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426636#comment-15426636 ] Anton Vinogradov commented on IGNITE-2079: -- 1) No need to add empty line at the method body after { (see test) 2) Seems, initialQuery should also contain fail("This line newer calls"), because this code should not be executed at expected scenario. 3) metr0 and metr1 - is thу same, but should be different :) 4) Need to check behaviour on backup key. 5) Need to check both metr0 and metr1 after each put. 6) We need to get rid of initialQuery if possible, because it can be reason of sometimes failing test in case initialQuery happens after put. > 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.8 > > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406887#comment-15406887 ] Denis Magda commented on IGNITE-2079: - [~AndreyVel], do you have any progress on this? When you expect to finish working on the issue? > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376508#comment-15376508 ] Anton Vinogradov commented on IGNITE-2079: -- 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376366#comment-15376366 ] Denis Magda commented on IGNITE-2079: - [~AndreyVel], If an UEX is not propagated to {{GridCacheIoManager.processFailedMessage}} like it happens in {{CacheContinuousQueryHandler.notifyCallback0}} then in must be processed there as well. Discuss and explain this to Anton as to the main reviewer of your changes. In regards to the metrics I think that UEX should be registered in ClusterMetrics. [~avinogradov] do you agree with this? > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374968#comment-15374968 ] Andrey Velichko commented on IGNITE-2079: - All comments done. Need ideas how reproduce unhandled exception for GridCacheIoManager.processFailedMessage. In this issue described case when original exception was lost, Anton corrected this bug. Next idea was creating listener for UEX (unhandled exception) + add counter QueryMetrics#fails. If we do global cache UEX processing better to user CacheMetrics counter. I have one unclear question what better method for registering UEX. One of points - method GridCacheIoManager.processFailedMessage in [case default] branch. In the attached example exception thrown in method CacheContinuousQueryHandler.notifyCallback0 in this point continuous query listener also has UEX, Anybody has ideas? > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373236#comment-15373236 ] Anton Vinogradov commented on IGNITE-2079: -- Andrey, 1) Did you check that original "Class can not be unmarshalled." are inside msg.classError()? 2) Each get should be cashed at local variable in case it used more than once, eg {{ctx.kernalContext(). ...}} 3) Please use {{GridTestUtils.waitForCondition -> unhandledExceptionCounter.get() == metr.executions() == metr.fails() == 1}} instead of {{unhandledExceptionDownLatch}} 4) Replace {{throw new IgniteException("This line newer calls");}} with fail(...). 5) Possible, we have to add put from another node and handle it {{jcache(1).put(testKey2, "value2");}} 6) Seems you duplicated line {{suite.addTestSuite(IgniteCacheContinuousQueryBackupQueueTest.class);}} > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373168#comment-15373168 ] Andrey Velichko commented on IGNITE-2079: - Anton I moved EVT_UNHANDLED_EXCEPTION from CacheContinuousQueryHandler to GridCacheIoManager the unit test work unstable, Server EVT_UNHANDLED_EXCEPTION from processFailedMessage often do not call. Maybe there are same features for writing unit test? > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372865#comment-15372865 ] Denis Magda commented on IGNITE-2079: - Please schedule tests validation on TC. > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372859#comment-15372859 ] Andrey Velichko commented on IGNITE-2079: - all comments done, 6 should be assertFalse(latch.await(1000, TimeUnit.MILLISECONDS)); > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372725#comment-15372725 ] Denis Magda commented on IGNITE-2079: - Agree with Anton on all the points. In regards to 4). Andrey I've analyzed the code one more time and looks like I was wrong. Please revert the original changes from there. No need to process {{GridCacheQueryResponse}}. > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372512#comment-15372512 ] Andrey Velichko commented on IGNITE-2079: - Event was renamed to UnhandledExceptionEvent, There are many types of exceptions, I think metrix for exceptions is new task. > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370648#comment-15370648 ] Denis Magda commented on IGNITE-2079: - In regards to 1. What if we create {{UnhandledExceptionEvent}} and register it as a part of the {{ClusterMetrics}} instead. Guys, any thoughts? > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370560#comment-15370560 ] Andrey Velichko commented on IGNITE-2079: - 1 CacheEvent is not convenient for error notification, there is no Exception field for sending for listener. 2 Done 3 In the code GridCacheQueryManager statsEnabled used only for CacheMetricsImpl if (statsEnabled) { CacheMetricsImpl metrics = cctx.cache().metrics0(); metrics.onRead(true); metrics.addGetTimeNanos(System.nanoTime() - start); } For QueryMetrics flag statsEnabled is not used, field QueryMetrics#fails incremented as public void onExecuted(boolean fail) { metrics.onQueryExecute(fail); } > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366095#comment-15366095 ] Denis Magda commented on IGNITE-2079: - [~AndreyVel], please do the following: - create a pull-request and move the ticket into "PATCH AVAILABLE" state; - validate your changes on public TC (http://149.202.210.143:8111). Make sure that you've added tests that validate your fixes; - ask for review. > 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: important > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366091#comment-15366091 ] Denis Magda commented on IGNITE-2079: - [~AndreyVel], please do the following: - create a pull-request and move the ticket into "PATCH AVAILABLE" state; - validate your changes on public TC (http://149.202.210.143:8111). Make sure that you've added tests that validate your fixes; - ask for review. > 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: important > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366068#comment-15366068 ] Andrey Velichko commented on IGNITE-2079: - Added processing of unhandled Exceptions for CacheContinuousQueryHandler - increment QueryMetrics#fails - register exception ctx.exceptionRegistry().onException(shortMsg, ex) - generate event type EVT_UNHANDLED_EXCEPTION notify using ctx.event().record(evt) Branch ignite-3424 > 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: important > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15363892#comment-15363892 ] Anton Vinogradov commented on IGNITE-2079: -- Alexey, We print the whole stack trace now. + 1 for EVT_UNHANDLED_EXCEPTION. > 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: important > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15363516#comment-15363516 ] Alexey Goncharuk commented on IGNITE-2079: -- Anton, Was the logging fixed so we print the whole stack trace? I like the idea of adding this exception to ExceptionRegistry. I would also create a local event, like EVT_UNHANDLED_EXCEPTION which can hold the exception. This event can be handled locally on server, or a client may subscribe to this event remotely if needed. So, I'm for #1 + a local event. > 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: important > 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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361418#comment-15361418 ] Andrey Velichko commented on IGNITE-2079: - If there are Exceptions inside notifyCallback0, we can lose event onUpdate for ContinuousQuery.setLocalListener see line 674 of CacheContinuousQueryHandler.notifyCallback0 There are same solutions 1 - (Anton Vinogradov) Add new metric to CacheMetrics - for example onUpdatedContinuousQueryFatal and register error using IgniteExceptionRegistry to allow user see exception details via Visor/VisorConsole. 2 - If has Exception, call method onUpdated(Iterableevts) add set evts == null 3 - Add method onError() to interface CacheEntryUpdatedListener or make abstract class for compatibility public interface CacheEntryUpdatedListener extends CacheEntryListener { void onError(IgniteCheckedException ex); void onUpdated(Iterable var1) throws CacheEntryListenerException; } > 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: important > 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.workday.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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274152#comment-15274152 ] Anton Vinogradov commented on IGNITE-2079: -- Found that unmarshalling issue cause no actions except error at logs. So, user will newer know why he is loosing Query updates untill he read logs. I think, we have to increment org.apache.ignite.cache.query.QueryMetrics#fails in case of unmarshalling problem and add corresponding exception to org.apache.ignite.internal.util.IgniteExceptionRegistry to allow user see exception details via Visor/VisorConsole. Thoughts? > 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: Anton Vinogradov > Labels: important > Fix For: 1.6 > > > 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.workday.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)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[ https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037797#comment-15037797 ] Anton Vinogradov commented on IGNITE-2079: -- Hotfix applied. Left: add GridCacheQueryResponse unmarshalled fail handling & test on GridCacheQueryResponse & GridCacheQueryRequest > 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: Anton Vinogradov > > 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.workday.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)