Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
install:guides:linux [2019/09/24 17:00]
doc
install:guides:linux [2020/02/26 20:22]
doc
Line 106: Line 106:
  
 <​code>​ <​code>​
 +  export CLASSPATH="/​opt/​omnidex/​lib/​Omnidex.jar:​$CLASSPATH"​
   export LD_LIBRARY_PATH="​opt/​omnidex/​lib:​$LD_LIBRARY_PATH"​   export LD_LIBRARY_PATH="​opt/​omnidex/​lib:​$LD_LIBRARY_PATH"​
-  export ​CLASSPATH="/​opt/​omnidex/​lib/​Omnidex.jar:​$CLASSPATH"+  export ​LD_PRELOAD="<see below>"
 </​code>​ </​code>​
  
 To use OdxSQL as a Java client for testing purposes, you also must add the directory containing libjvm.so to LD_LIBRARY_PATH. To use OdxSQL as a Java client for testing purposes, you also must add the directory containing libjvm.so to LD_LIBRARY_PATH.
  
-IMPORTANT: Note that Java can have compatibility issues with signal handling with other applications,​ including Omnidex. ​ This can cause unexplained aborts of the JVM when connecting to Omnidex processes, such as when setting up application pooling using DBCP.  ​Oracle and Java recommend that you set the LD_PRELOAD environment ​variable ​if you encounter this problem, as described in the following ​article:+Additionally,​ it is recommended to set LD_PRELOAD to Java's libjsig.so library due to known compatibility issues with Java'​s ​signal handling with other applications,​ including Omnidex. This is necessary to avoid unexplained aborts of the JVM when connecting to Omnidex processes, such as when setting up application pooling using DBCP. Instructions for setting this variable ​can be found at the following ​link:
  
 https://​docs.oracle.com/​javase/​8/​docs/​technotes/​guides/​vm/​signal-chaining.html https://​docs.oracle.com/​javase/​8/​docs/​technotes/​guides/​vm/​signal-chaining.html
- 
- 
  
  
Line 126: Line 125:
  
 <​code>​ <​code>​
-  ​service ​omnidexd ​start        ​(start omnidex as a service) +  ​systemctl start omnidexd ​        ​(start omnidex as a service) 
-  ​service ​omnidexd ​stop         (stop omnidex as a service) +  ​systemctl stop omnidexd ​         (stop omnidex as a service) 
-  ​service ​omnidexd ​restart ​     ​(restart omnidex as a service) +  ​systemctl restart ​omnidexd ​      ​(restart omnidex as a service) 
-  ​service ​omnidexd ​status ​      (check if omnidex is running as a service)+  ​systemctl status ​omnidexd ​       (check if omnidex is running as a service)
 </​code>​ </​code>​
  
 
Back to top
install/guides/linux.txt · Last modified: 2021/08/26 21:36 by doc