Apache ignite .net core server node fails to start with the below error, any idea what could be the reason?
Apache.Ignite.Core.Common.IgniteException
HResult=0x80131500
Message=Java exception occurred [class=java.lang.ExceptionInInitializerError, message=]
Source=Apache.Ignite.Core
StackTrace:
at Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
at IgniteShared.Cache.CacheService.<Start>b__3_0() in C:\Users\user\IgnitePoc\IgniteShared\Cache.cs
This exception was originally thrown at this call stack:
[External Code]
Inner Exception 1:
JavaException: java.lang.ExceptionInInitializerError
at org.apache.ignite.internal.processors.platform.memory.PlatformAbstractMemory.<clinit>(PlatformAbstractMemory.java:27)
at org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.init(PlatformAbstractBootstrap.java:54)
at org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:65)
Caused by: java.lang.RuntimeException: java.nio.DirectByteBuffer.address field is unavailable.
at org.apache.ignite.internal.util.GridUnsafe$2.run(GridUnsafe.java:1570)
at org.apache.ignite.internal.util.GridUnsafe$2.run(GridUnsafe.java:1557)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at org.apache.ignite.internal.util.GridUnsafe.bufferAddressOffset(GridUnsafe.java:1557)
at org.apache.ignite.internal.util.GridUnsafe.<clinit>(GridUnsafe.java:109)
... 3 more
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field long java.nio.Buffer.address accessible: module java.base does not "opens java.nio" to unnamed module #69663380
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:172)
at org.apache.ignite.internal.util.GridUnsafe$2.run(GridUnsafe.java:1562)
... 7 more
Apache Ignite requires Java 8 or Java 11.
Java 17 is not yet supported.
https://ignite.apache.org/docs/latest/quick-start/dotnet
(update: Java 17 support is coming soon: IGNITE-16622)
I faced a similar issue when launching Ignite from a java application (the start-up script ignite.sh wasn't used); with Java 17.0.3 and Ignite 2.13.0. At that time, the documentation only described the required JVM options for running Ignite with Java 11 (Running Ignite with Java 11). So, I found the necessary JVM options for running Ignite with Java 17 in the source code (jvmdefaults.sh).
Related
Error: Could not find or load main class
Caused by: java.lang.ClassNotFoundException:
this is happening in intellij for spring boot project.
i have tried to change project settings too.
using java 11
I'm trying to launch Apache Twill application from hadoop cluster, the cluster is recently upgraded from HDP 2.2 to HDP 2.5 but I'm getting llegalAccessError for RequestHedgingRMFailoverProxyProvider class . This class is part of org.apache.hadoop.yarn.client package. I'm getting this error in the Application Master. The job status goes directy to 'not running state' right after 'accepted state'.
Exception in thread "Hadoop22YarnAMClient STARTING" Exception in thread "YarnAMClientService STARTING" java.lang.IllegalAccessError: tried to access method org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider.getProxyInternal()Ljava/lang/Object; from class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
at org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider.init(RequestHedgingRMFailoverProxyProvider.java:75)
at org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:163)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.serviceStart(AMRMClientImpl.java:186)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at org.apache.twill.internal.yarn.Hadoop21YarnAMClient.startUp(Hadoop21YarnAMClient.java:77)
at com.google.common.util.concurrent.AbstractIdleService$1$1.run(AbstractIdleService.java:43)
at java.lang.Thread.run(Thread.java:745)
com.google.common.util.concurrent.ExecutionError: java.lang.IllegalAccessError: tried to access method org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider.getProxyInternal()Ljava/lang/Object; from class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
at com.google.common.util.concurrent.Futures.wrapAndThrowUnchecked(Futures.java:1008)
at com.google.common.util.concurrent.Futures.getUnchecked(Futures.java:1001)
at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:220)
at com.google.common.util.concurrent.AbstractIdleService.startAndWait(AbstractIdleService.java:106)
at org.apache.twill.internal.appmaster.ApplicationMasterMain$YarnAMClientService.startUp(ApplicationMasterMain.java:221)
at com.google.common.util.concurrent.AbstractIdleService$1$1.run(AbstractIdleService.java:43)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalAccessError: tried to access method org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider.getProxyInternal()Ljava/lang/Object; from class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
at org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider.init(RequestHedgingRMFailoverProxyProvider.java:75)
at org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:163)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.serviceStart(AMRMClientImpl.java:186)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at org.apache.twill.internal.yarn.Hadoop21YarnAMClient.startUp(Hadoop21YarnAMClient.java:77)
... 2 more
In general when you see IllegalAccessError this means you have a runtime incompatibility between compiled and runtime code. In this case,
the getProxyInternal() method of ConfiguredRMFailoverProxyProvider is now private. You need to recompile your client code and/or use updated hadoop client libraries to connect to your cluster.
Any one met exceptions below when startup JDeveloper 12.1.3 with SOA suite ? this lead to I can not save the workspace, very bad. actually, I was wondering if there is anyone like JDeveloper, but I have to use it. :(
JDeveloper version: Build JDEVADF_12.1.3.0.0_GENERIC_140521.1008.S
Jdk version: java version "1.7.0_80"
stack trace as below:
SEVERE:
javax.naming.NamingException [Root exception is java.lang.NullPointerException]
at oracle.adf.share.jndi.ContextImpl.throwNamingException(ContextImpl.java:671)
at oracle.adf.share.jndi.ContextImpl.saveDocument(ContextImpl.java:968)
at oracle.adf.share.jndi.ContextImpl.save(ContextImpl.java:986)
at oracle.adf.share.dt.ConnectionNsChangeListener.refreshInternal(ConnectionNsChangeListener.java:242)
at oracle.adf.share.dt.ConnectionNsChangeListener.refresh(ConnectionNsChangeListener.java:180)
at oracle.adf.share.dt.ConnectionNsChangeListener.objectAdded(ConnectionNsChangeListener.java:43)
...
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Caused by: java.lang.NullPointerException
at oracle.jdevimpl.jps.JpsConfigUtilsImpl.getDefaultJpsContext(JpsConfigUtilsImpl.java:722)
at oracle.jdevimpl.jps.JpsConfigUtilsImpl.getCredentialStoreLocation(JpsConfigUtilsImpl.java:1407)
at oracle.adf.share.dt.security.providers.jps.CSFDTCredentialStore.checkInitCSFStore(CSFDTCredentialStore.java:333)
at oracle.adf.share.dt.security.providers.jps.CSFDTCredentialStore.fetchCredential(CSFDTCredentialStore.java:588)
at oracle.adf.share.dt.security.providers.jps.CSFDTCredentialStore.fetchCredential(CSFDTCredentialStore.java:578)
at oracle.adf.share.security.credentialstore.CredentialStore.fetchCredential(CredentialStore.java:187)
at oracle.adf.share.jndi.CredentialStoreHelper.fetchCredential(CredentialStoreHelper.java:104)
at oracle.adf.share.jndi.ReferenceStoreHelper.saveCredentialsInternal(ReferenceStoreHelper.java:520)
at oracle.adf.share.jndi.ReferenceStoreHelper.saveCredentials(ReferenceStoreHelper.java:476)
at oracle.adf.share.jndi.ContextImpl.saveDocument(ContextImpl.java:957)
... 123 more
this caused by 3 files below missing, usually it will not happen
src/META-INF/cwallet.sso
src/META-INF/cwallet.sso.lck
src/META-INF/jps-config.xml
please also refer to https://community.oracle.com/thread/3870268?sr=stream
I have faced a problem like Mobilefirst server not starting until i
edit the JVM.options (-DOS.name = Windows 8) in the eclipse.
I need to do the above step manually whenever i create a new workspace
Is there
any other way to completely resolve this problem.
Note : I am using Windows 8.1
Error Log
Listening for transport dt_socket at address: 10777
CWWKE0005E: The runtime environment could not be launched.
CWWKE0018E: An exception occurred while launching the runtime environment: java.lang.IllegalArgumentException: WebSphere-DefaultExtension-windowsnt(unknown)
com.ibm.ws.kernel.boot.LaunchException: Caught unexpected exception java.lang.IllegalArgumentException: WebSphere-DefaultExtension-windowsnt(unknown)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.rethrowException(KernelBootstrap.java:418)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.go(KernelBootstrap.java:183)
at com.ibm.ws.kernel.boot.Launcher.createPlatform(Launcher.java:131)
at com.ibm.ws.kernel.boot.Launcher.main(Launcher.java:55)
at com.ibm.ws.kernel.boot.cmdline.EnvCheck.main(EnvCheck.java:52)
Caused by: java.lang.IllegalArgumentException: WebSphere-DefaultExtension-windowsnt(unknown)
at java.util.jar.Attributes$Name.<init>(Unknown Source)
at java.util.jar.Attributes.getValue(Unknown Source)
at com.ibm.ws.kernel.boot.internal.BootstrapManifest.getOSExtensionDefinition(BootstrapManifest.java:157)
at com.ibm.ws.kernel.boot.internal.KernelBootstrap.go(KernelBootstrap.java:123)
... 3 more
Try adding that option to the eclipse.ini file located in your Eclipse installation folder, instead of in the JVM.options of your workspace.
when I am starting glass fish server through command prompt I am getting an
error. I am using jdk 1.5 and jdk1.6 also. Due to java version am I getting that error or any other reason.
I am using two tomcat server also that port no is 8080 and 8081.
For glass fish-domain purpose I am using 4545 port number.
Error starting domain mydomain1.
The server exited prematurely with exit code 1.
Before it died, it produced the following output:
FATAL ERROR in native method: processing of -javaagent failed
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:133)
Exception in thread "main"
This is the important bit.
java.lang.UnsupportedClassVersionError: Bad version number in .class file
It means that the class loader does not understand the version number of one of the ".class" files that it is trying to load.
The most likely explanation is that you are trying to load classes that have been compiled on a Java 7 development platform on an earlier (e.g. Java 5 or Java 6) JRE / JVM installation. You either need to upgrade your execution platform to Java 7 (best option), or downgrade your development platform to Java 5 or Java 6 (or whatever you are using).
Note that both Java 5 and Java 6 have reached "end of life", and there will not be any more patch releases available ... unless you take out an Oracle Java support contract.