The core node you are trying to access is permanently deleted.
Hello, we are using ArcGis Enterprise and additional Server together with GeoEvent are installed on separate machine (Windows Server 2016, processor Intel Xeon E5-2673 v4 @ 2.30GHz). Last week, we upgraded all the Enterprise components from 10.5.1 to 10.6. After couple of days, machine started using almost 100% CPU all the time. In task manager it shows that application responsible for usage is Java (TM) Platform SE binary. When I stop the whole GeoEvent Server, CPU starts working fine. So I suspect the problem is somewhere behind GeoEvent. I tried to analyse log files but I do not really know what should I search for. Did anyone experience similar problem? I will appreciate any help.
We have the exact same problem. However our configuration is slightly different:
Windows 2012, 4 CPU, 16 GB RAM - HyperV virtualisation.
ArcGIS Server 10.5.1 and GeoEvent 10.5.1
The same problem occurs - Java (in the ArcGIS Server folder) consumes all the CPU (99-100%) rendering the machine unresponsive. One the machine is restarted it will work again.
I think it might be related to the NMEA events that we receive as I started seeing these errors in the GeoEvent Server log files:
An unexpected error has occurred while translating a NMEA message. Error: Failed to create new GeoEvent: GeoEvent Definition for GUID(39ec2c55-5d51-43ee-a8ce-5f7d8904abd8) does not exist..
Failed to create new GeoEvent: GeoEvent Definition for GUID(39ec2c55-5d51-43ee-a8ce-5f7d8904abd8) does not exist. com.esri.ges.messaging.MessagingException: Failed to create new GeoEvent: GeoEvent Definition for GUID(39ec2c55-5d51-43ee-a8ce-5f7d8904abd8) does not exist. at com.esri.ges.messaging.jms.GeoEventCreatorImpl.create(GeoEventCreatorImpl.java:32)[112:com.esri.ges.framework.messaging.jms-messaging:10.5.1] at com.esri.geoevent.adapter.nmea.NmeaInboundAdapter$GeoEventProducer.run(NmeaInboundAdapter.java:81)[422:com.esri.geoevent.adapter.nmea-adapter:10.5.1] at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
My suspicion is that GeoEvent does not really like to be upgraded and needs to be completely removed before installing a new version. Just a hunch tho.
br,
Rasmus