[jira] [Created] (IGNITE-13240) JVM Cashes on .NET Node (EXCEPTION_ACCESS_VIOLATION)
Chris Paraskeva created IGNITE-13240: Summary: JVM Cashes on .NET Node (EXCEPTION_ACCESS_VIOLATION) Key: IGNITE-13240 URL: https://issues.apache.org/jira/browse/IGNITE-13240 Project: Ignite Issue Type: Bug Affects Versions: 2.8.1 Environment: OS: Windows 10 JRE version: Java(TM) SE Runtime Environment (11.0.5+10) (build 11.0.5+10-LTS) Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0.5+10-LTS, mixed mode, tiered, compressed oops, g1 gc, windows-amd64) Reporter: Chris Paraskeva After some time of Apache Ignite is up & running using a sinle .NET Core node is crashing because of JAVA EXCEPTION_ACCESS_VIOLATION -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13199) Apache Ignite Binary Serialization between .NET Core and Java is not working
[ https://issues.apache.org/jira/browse/IGNITE-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Paraskeva resolved IGNITE-13199. -- Fix Version/s: (was: 2.9) Resolution: Not A Problem > Apache Ignite Binary Serialization between .NET Core and Java is not working > > > Key: IGNITE-13199 > URL: https://issues.apache.org/jira/browse/IGNITE-13199 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.8.1 > Environment: * OS: Windows 10 10.0 amd64 > * VM information: Java(TM) SE Runtime Environment 11.0.5+10-LTS Oracle > Corporation Java HotSpot(TM) 64-Bit Server VM 11.0.5+10-LTS > * Apache Ignite 2.8.1 version >Reporter: Chris Paraskeva >Priority: Critical > > I have run into issue where I use a group of Apache Ignite (2.8.1) server > nodes in .NET core to create a data grid and run queries to the grid via an > Apache ignite java client. I have not problem at all writing data in binary > mode to the grid and ask queries via the think layer provided. I use DBeaver > to run queries and everything is fine as expected. The issue rise while I am > trying to query data from a java client which complains about a conflict in > cache ": Conflicts during configuration merge for cache MY_CAHE". Find the > error message below: > > Caused by: class org.apache.ignite.spi.IgniteSpiException: Conflicts during > configuration merge for cache 'DOTNET_BINARY_CACHE' : > TRADE conflict: > keyType is different: local=Apache.Ignite.Core.Cache.Affinity.AffinityKey, > received=org.apache.ignite.cache.affinity.AffinityKey > valType is different: > local=Servicing.Agent4.Service.Implementation.Misc.Ignite.Trade, > received=Servicing.Agent4.Core.Java.Models.Trade > > More info can be found on stackoverflow > [https://stackoverflow.com/questions/62675059/apache-ignite-binary-serialization-between-net-core-and-java-is-not-working] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13199) Apache Ignite Binary Serialization between .NET Core and Java is not working
[ https://issues.apache.org/jira/browse/IGNITE-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152695#comment-17152695 ] Chris Paraskeva commented on IGNITE-13199: -- It seems the issue was a misconfiguration between .NET and Java, closing issue. > Apache Ignite Binary Serialization between .NET Core and Java is not working > > > Key: IGNITE-13199 > URL: https://issues.apache.org/jira/browse/IGNITE-13199 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.8.1 > Environment: * OS: Windows 10 10.0 amd64 > * VM information: Java(TM) SE Runtime Environment 11.0.5+10-LTS Oracle > Corporation Java HotSpot(TM) 64-Bit Server VM 11.0.5+10-LTS > * Apache Ignite 2.8.1 version >Reporter: Chris Paraskeva >Priority: Critical > Fix For: 2.9 > > > I have run into issue where I use a group of Apache Ignite (2.8.1) server > nodes in .NET core to create a data grid and run queries to the grid via an > Apache ignite java client. I have not problem at all writing data in binary > mode to the grid and ask queries via the think layer provided. I use DBeaver > to run queries and everything is fine as expected. The issue rise while I am > trying to query data from a java client which complains about a conflict in > cache ": Conflicts during configuration merge for cache MY_CAHE". Find the > error message below: > > Caused by: class org.apache.ignite.spi.IgniteSpiException: Conflicts during > configuration merge for cache 'DOTNET_BINARY_CACHE' : > TRADE conflict: > keyType is different: local=Apache.Ignite.Core.Cache.Affinity.AffinityKey, > received=org.apache.ignite.cache.affinity.AffinityKey > valType is different: > local=Servicing.Agent4.Service.Implementation.Misc.Ignite.Trade, > received=Servicing.Agent4.Core.Java.Models.Trade > > More info can be found on stackoverflow > [https://stackoverflow.com/questions/62675059/apache-ignite-binary-serialization-between-net-core-and-java-is-not-working] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13199) Apache Ignite Binary Serialization between .NET Core and Java is not working
[ https://issues.apache.org/jira/browse/IGNITE-13199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Paraskeva updated IGNITE-13199: - Description: I have run into issue where I use a group of Apache Ignite (2.8.1) server nodes in .NET core to create a data grid and run queries to the grid via an Apache ignite java client. I have not problem at all writing data in binary mode to the grid and ask queries via the think layer provided. I use DBeaver to run queries and everything is fine as expected. The issue rise while I am trying to query data from a java client which complains about a conflict in cache ": Conflicts during configuration merge for cache MY_CAHE". Find the error message below: Caused by: class org.apache.ignite.spi.IgniteSpiException: Conflicts during configuration merge for cache 'DOTNET_BINARY_CACHE' : TRADE conflict: keyType is different: local=Apache.Ignite.Core.Cache.Affinity.AffinityKey, received=org.apache.ignite.cache.affinity.AffinityKey valType is different: local=Servicing.Agent4.Service.Implementation.Misc.Ignite.Trade, received=Servicing.Agent4.Core.Java.Models.Trade More info can be found on stackoverflow [https://stackoverflow.com/questions/62675059/apache-ignite-binary-serialization-between-net-core-and-java-is-not-working] was: I have run into issue where I use a group of Apache Ignite (2.8.1) server nodes in .NET core to create a data grid and run queries to the grid via an Apache ignite java client. I have not problem at all writing data in binary mode to the grid and ask queries via the think layer provided. I use DBeaver to run queries and everything is fine as expected. The issue rise while I am trying to query data from a java client which complains about a conflict in cache ": Conflicts during configuration merge for cache MY_CAHE". Find the error message below: Caused by: class org.apache.ignite.spi.IgniteSpiException: Conflicts during configuration merge for cache 'DOTNET_BINARY_CACHE' : TRADE conflict: keyType is different: local=Apache.Ignite.Core.Cache.Affinity.AffinityKey, received=org.apache.ignite.cache.affinity.AffinityKey valType is different: local=Servicing.Agent4.Service.Implementation.Misc.Ignite.Trade, received=Servicing.Agent4.Core.Java.Models.Trade > Apache Ignite Binary Serialization between .NET Core and Java is not working > > > Key: IGNITE-13199 > URL: https://issues.apache.org/jira/browse/IGNITE-13199 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.8.1 > Environment: * OS: Windows 10 10.0 amd64 > * VM information: Java(TM) SE Runtime Environment 11.0.5+10-LTS Oracle > Corporation Java HotSpot(TM) 64-Bit Server VM 11.0.5+10-LTS > * Apache Ignite 2.8.1 version >Reporter: Chris Paraskeva >Priority: Critical > Fix For: 2.9 > > > I have run into issue where I use a group of Apache Ignite (2.8.1) server > nodes in .NET core to create a data grid and run queries to the grid via an > Apache ignite java client. I have not problem at all writing data in binary > mode to the grid and ask queries via the think layer provided. I use DBeaver > to run queries and everything is fine as expected. The issue rise while I am > trying to query data from a java client which complains about a conflict in > cache ": Conflicts during configuration merge for cache MY_CAHE". Find the > error message below: > > Caused by: class org.apache.ignite.spi.IgniteSpiException: Conflicts during > configuration merge for cache 'DOTNET_BINARY_CACHE' : > TRADE conflict: > keyType is different: local=Apache.Ignite.Core.Cache.Affinity.AffinityKey, > received=org.apache.ignite.cache.affinity.AffinityKey > valType is different: > local=Servicing.Agent4.Service.Implementation.Misc.Ignite.Trade, > received=Servicing.Agent4.Core.Java.Models.Trade > > More info can be found on stackoverflow > [https://stackoverflow.com/questions/62675059/apache-ignite-binary-serialization-between-net-core-and-java-is-not-working] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13199) Apache Ignite Binary Serialization between .NET Core and Java is not working
Chris Paraskeva created IGNITE-13199: Summary: Apache Ignite Binary Serialization between .NET Core and Java is not working Key: IGNITE-13199 URL: https://issues.apache.org/jira/browse/IGNITE-13199 Project: Ignite Issue Type: Bug Components: binary Affects Versions: 2.8.1 Environment: * OS: Windows 10 10.0 amd64 * VM information: Java(TM) SE Runtime Environment 11.0.5+10-LTS Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 11.0.5+10-LTS * Apache Ignite 2.8.1 version Reporter: Chris Paraskeva Fix For: 2.9 I have run into issue where I use a group of Apache Ignite (2.8.1) server nodes in .NET core to create a data grid and run queries to the grid via an Apache ignite java client. I have not problem at all writing data in binary mode to the grid and ask queries via the think layer provided. I use DBeaver to run queries and everything is fine as expected. The issue rise while I am trying to query data from a java client which complains about a conflict in cache ": Conflicts during configuration merge for cache MY_CAHE". Find the error message below: Caused by: class org.apache.ignite.spi.IgniteSpiException: Conflicts during configuration merge for cache 'DOTNET_BINARY_CACHE' : TRADE conflict: keyType is different: local=Apache.Ignite.Core.Cache.Affinity.AffinityKey, received=org.apache.ignite.cache.affinity.AffinityKey valType is different: local=Servicing.Agent4.Service.Implementation.Misc.Ignite.Trade, received=Servicing.Agent4.Core.Java.Models.Trade -- This message was sent by Atlassian Jira (v8.3.4#803005)
