OrientDB service fails to start after clean install of CA TDM or update to 4.10.X from 4.9.X
Article ID: 221912
Updated On:
Products
Issue/Introduction
Hi,
I had portal version 4.9.66 installed on a server and patched up to version 4.9.335
Although, after trying to make our new java plugin for encryption keys to work with this latest version,
we had to start from a clean install of the CA TDM portal at some point to see what is the difference between patching and a clean install.
I have tried installing version 4.9.335 from scratch but now the OrientDB service fails to start and always gives this error:
INFO|wrapper|21-08-05 13:38:59|start delay: 0
INFO|wrapper|21-08-05 13:38:59|started process with pid 4468
INFO|4468/0|21-08-05 13:38:59|error finding main method in class: com.orientechnologies.orient.server.OServerMain : com.orientechnologies.orient.server.OServerMain
INFO|4468/0|21-08-05 13:38:59|java.lang.ClassNotFoundException: com.orientechnologies.orient.server.OServerMain
INFO|4468/0|21-08-05 13:38:59|no java main method found -> aborting
INFO|4468/0|21-08-05 13:38:59| at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
INFO|4468/0|21-08-05 13:38:59| at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
INFO|4468/0|21-08-05 13:38:59| at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
INFO|4468/0|21-08-05 13:38:59| at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
INFO|4468/0|21-08-05 13:38:59| at org.rzo.yajsw.app.WrapperManagerImpl.init(WrapperManagerImpl.java:335)
INFO|4468/0|21-08-05 13:38:59| at org.rzo.yajsw.app.WrapperManagerProxy.getWrapperManager(WrapperManagerProxy.java:53)
INFO|4468/0|21-08-05 13:38:59| at org.rzo.yajsw.app.AbstractWrapperJVMMain$1.run(AbstractWrapperJVMMain.java:65)
INFO|4468/0|21-08-05 13:38:59| at java.security.AccessController.doPrivileged(Native Method)
INFO|4468/0|21-08-05 13:38:59| at org.rzo.yajsw.app.AbstractWrapperJVMMain.preExecute(AbstractWrapperJVMMain.java:57)
INFO|4468/0|21-08-05 13:38:59| at org.rzo.yajsw.app.WrapperJVMMain.main(WrapperJVMMain.java:41)
INFO|wrapper|21-08-05 13:39:00|restart process due to default exit code rule
INFO|wrapper|21-08-05 13:39:00|restart internal RUNNING controller killed restart handler
INFO|wrapper|21-08-05 13:39:00|stopping process with pid/timeout 4468 315000
INFO|wrapper|21-08-05 13:39:01|process exit code: 999
I also tried 2 other previous versions 4.9.333 and 4.9.291 but I still get these errors and OrientDB service fails to start
Cause
The client had manually set environment variables on the target machine.
The environment variables had path statements with incorrect Case>
Currently, we use a third-party application which is a yajsw wrapper that is case sensitive.
We are not able to control this behavior and should make sure that env variables are created by the installer or make sure that the customer uses the correct case.
Environment
TDM 4.9.1
Component: TDM Web Portal
Windows Server 2016 Standard (Version 10.0.14393).
Resolution
Currently, we use a third-party application which is a yajsw wrapper that is case sensitive.
We are not able to control this behavior and should make sure that env variables are created by the installer or make sure that the customer uses the correct case.
Additional Information
- Service OrientDB won't start
CATDMWEB_HOME: D:\APPS\CA\CA Test Data Manager Portal\
ORIENTDB_HOME: D:\APPS\CA\CA Test Data Manager Portal\orientdb\
- Service OrientDB OK
CATDMWEB_HOME: D:\Apps\CA\CA Test Data Manager Portal\
ORIENTDB_HOME: D:\Apps\CA\CA Test Data Manager Portal\orientdb\
NOTE: in 4.10 version the ending \ MUST be removed to have orientDB start
In 4.10 also remove the ending \ from CATDMWEB_APPDATA
Attachments
Feedback
