Hello Pankaj. Could you please clarify, what JDK do you use? In such cases (when a class does not have a default constructor), Ignite creates a default constructor via sun.reflect.ReflectionFactory. But this feature is available/tested only in SUN JDK's [1].
Thus I have a question, what JDK do you use? [2] https://github.com/apache/ignite/blob/ignite-2.10/modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java#L1628 --------------------- Ilya вт, 31 авг. 2021 г. в 15:05, Pankaj Kumar Bhadani < pankaj.kumar.bhad...@ericsson.com>: > Hi Team, > > I am facing some issue with setting up apache ignite-core 2.10.0 in java > 11 environment. > > I am getting the below exception, when I am trying to start ignite Using > Ignition start method. > > {"version": "0.2.0", "timestamp": "2021-08-18T08:08:51.363Z", "severity": > "error", "service_id": "eric-bss-cpm-app", "metadata" : {"category": > "CPM"}, "message": "Exception during start processors, node will be > stopped and close connections"} > org.apache.ignite.binary.BinaryObjectException*: Failed to find empty > constructor for class: > org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult* > at > org.apache.ignite.internal.binary.BinaryClassDescriptor.constructor(BinaryClassDescriptor.java:1088) > at > org.apache.ignite.internal.binary.BinaryClassDescriptor.<init>(BinaryClassDescriptor.java:309) > > > > As a work around temporarily I created the default constructer in the > org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult.java > class and build the jar from source code. This solved my problem and I was > able to proceed with my POC. I now need a solution to this problem, so that > when I integrate Ignite io build the solution I don’t have to make this > change. > > > > Also wanted to appraise you that this is being used in the containerized > product which uses java11 and ignite cluster would be started in the same > JVM > > > > Thanks, > > Pankaj Bhadani >
