Start/Stop Adeptia Services

Owned by Subrat Sandilya
Last updated: Aug 22, 2024 by Rajeev Rai
2 min read

Issue

Cause

Diagnosis

Resolution

If you are using Adeptia Connect or Suite and unable to start Kernel due to the below error/exception related to hazelcast.xml file.

This issue occurs when the property 'abpm.connect.cache.enable' is set to yes in server-configure.properties file.

INFO: Configuring Hazelcast from 'D:\Program Files\Adeptia\AdeptiaSuite-6.9\AdeptiaServer\ServerKernel\etc\hazelcast.xml'.
2020-09-01 13:33:05 Sep 01, 2020 1:33:05 PM com.hazelcast.config.AbstractXmlConfigHelper
2020-09-01 13:33:05 WARNING: Name of the hazelcast schema location is incorrect, using default
2020-09-01 13:33:05 Exception in thread "Adeptia Suite 6.7 Kernel Thread" java.lang.NoClassDefFoundError: org/apache/log4j/Priority
2020-09-01 13:33:05 at com.hazelcast.logging.Log4jFactory.createLogger(Log4jFactory.java:30)
2020-09-01 13:33:05 at com.hazelcast.logging.LoggerFactorySupport$1.createNew(LoggerFactorySupport.java:32)
2020-09-01 13:33:05 at com.hazelcast.logging.LoggerFactorySupport$1.createNew(LoggerFactorySupport.java:30)
2020-09-01 13:33:05 at com.hazelcast.util.ConcurrencyUtil.getOrPutIfAbsent(ConcurrencyUtil.java:125)
2020-09-01 13:33:05 at com.hazelcast.logging.LoggerFactorySupport.getLogger(LoggerFactorySupport.java:38)
2020-09-01 13:33:05 at com.hazelcast.logging.Logger.getLogger(Logger.java:77)
2020-09-01 13:33:05 at com.hazelcast.logging.Logger.getLogger(Logger.java:64)
2020-09-01 13:33:05 at com.hazelcast.internal.config.ConfigValidator.<clinit>(ConfigValidator.java:89)
2020-09-01 13:33:05 at com.hazelcast.instance.Node.<init>(Node.java:209)
2020-09-01 13:33:05 at com.hazelcast.instance.HazelcastInstanceImpl.createNode(HazelcastInstanceImpl.java:161)
2020-09-01 13:33:05 at com.hazelcast.instance.HazelcastInstanceImpl.<init>(HazelcastInstanceImpl.java:131)
2020-09-01 13:33:05 at com.hazelcast.instance.HazelcastInstanceFactory.constructHazelcastInstance(HazelcastInstanceFactory.java:229)
2020-09-01 13:33:05 at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(HazelcastInstanceFactory.java:208)
2020-09-01 13:33:05 at com.hazelcast.instance.HazelcastInstanceFactory.newHazelcastInstance(HazelcastInstanceFactory.java:158)
2020-09-01 13:33:05 at com.hazelcast.core.Hazelcast.newHazelcastInstance(Hazelcast.java:57)
2020-09-01 13:33:05 at com.adeptia.indigo.storage.HazelcastManager.<init>(HazelcastManager.java:70)
2020-09-01 13:33:05 at com.adeptia.indigo.storage.HazelcastManager.getInstance(HazelcastManager.java:119)
2020-09-01 13:33:05 at com.adeptia.indigo.IndigoKernel.initializeHazelcastServer(IndigoKernel.java:1153)
2020-09-01 13:33:05 at com.adeptia.indigo.IndigoKernel.boot(IndigoKernel.java:457)
2020-09-01 13:33:05 at com.adeptia.indigo.IndigoKernel.main(IndigoKernel.java:315)
2020-09-01 13:33:05 Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Priority
2020-09-01 13:33:05 at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
2020-09-01 13:33:05 at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
2020-09-01 13:33:05 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
2020-09-01 13:33:05 at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
2020-09-01 13:33:05 ... 20 more

 

 

This is an obsolete property and isn't needed. Once this property is disabled or set to no then this issue will be resolved and you shall be able to start Adeptia Services.

https://support.adeptia.com/attachments/token/OJJW5qMJjhpHb3jkonbb2AWJ1/?name=inline1544690228.png

Adeptia Services takes 10-15 mins at Startup

This is an environment-specific issue and some customers face this issue when their Linux servers face trouble while generating Random numbers, when the Adeptia tries to generate a random number but JVM is unable to generate the number and gets stuck there for 12-15 minutes.

Our servers where Adeptia Connect/Adeptia Suite is installed don't have Internet Connectivity due to which server is not able to connect the Adeptia license server and gets stuck on the below message for around 10-15 minutes but after the wait Adeptia starts successfully.
Error while checking License status
2020-07-27 12:20:21 java.net.SocketException: Network is unreachable (connect failed): License server cannot be reached

JVM is using file /dev/random by default. If we change it to /dev/urandom for generating random numbers then the issue will be resolved and Adeptia will start in acceptable times within a minute or a two.
Here is a reference URL that helped to resolve this issue:
https://stackoverflow.com/questions/137212/how-to-deal-with-a-slow-securerandom-generator
We need to add Property -Djava.security.egd=file:/dev/../dev/urandom in the launcher.properties file present inside for the kernel to resolve this issue. The same property can be also used in Webrunner/AI startup parameters.
https://support.adeptia.com/hc/en-us/article_attachments/360071274751/1f071bfde8061262b6a27921d2f8dad1e9de9ffa0f04f614dcb3cd17f56d1a21.png

Trouble starting Adeptia Kernel in Linux

Within the config.log identify the error "../../jre/bin/java: Permission denied".

Check the logs and if the following error message is displayed:

MGMSP2DG64:/usr/local/bin/AdeptiaSuite/AdeptiaSuite-5.3/AdeptiaServer/ServerKernel # ./startup.sh
Note: If you need to contact Tech Support, please email the following file: /usr/local/bin/AdeptiaSuite/AdeptiaSuite-5.3/AdeptiaServer/ServerKernel/config.log

Starting Kernel......
error starting kernel

Since it can be a permission issue please provide all the permissions to the folder and the sub-folders of AdeptiaSuite-5.3 .Also do check if all the permissions are provided to the bin folder located at "/AdeptiaSuite/AdeptiaSuite-5.3/jre/".