eserver.cfg AutoRun and RunFirst Processes (OEngine Server)
At 27 SEP 2022 10:13:15AM Donald Bakke wrote:
I'm trying to get the AutoRun and RunFirst working. The StartupProc and TimerProc processes are working just fine, but they only require the name of the procedure whereas AutoRun and RunFirst require the procedure name, app name, user name, and password.
When AutoRun is configured, I get this in the console:
About to stop our listener socket About to stop our utf listener socket About to kill all existing connections (0) About to kill all phantom connections (0) About to stop any cached engines In OEngineFactory:CleanupTask - Running used engine cleanup About to kill any existing command channels About to stop our main OEngine All shut down - terminatingWhen RunFirst is configured, I get this in the console:
Exception in thread "OEEngineServerThread" java.lang.ArrayIndexOutOfBoundsException: 3 at com.revelation.oesocketserver.EngineServerProtocol.startProcess(EngineServerProtocol.java:708) at com.revelation.oesocketserver.EngineServerProtocol.commonInit(EngineServerProtocol.java:63) at com.revelation.oesocketserver.EngineServerProtocol.<init>(EngineServerProtocol.java:36) at com.revelation.oesocketserver.OEEngineServerThread.run(OEEngineServerThread.java:75)Any ideas of what I'm doing wrong?
At 27 SEP 2022 12:10PM Donald Bakke wrote:
I'm trying to get the AutoRun and RunFirst working. The StartupProc and TimerProc processes are working just fine, but they only require the name of the procedure whereas AutoRun and RunFirst require the procedure name, app name, user name, and password.
When AutoRun is configured, I get this in the console:
About to stop our listener socket About to stop our utf listener socket About to kill all existing connections (0) About to kill all phantom connections (0) About to stop any cached engines In OEngineFactory:CleanupTask - Running used engine cleanup About to kill any existing command channels About to stop our main OEngine All shut down - terminatingWhen RunFirst is configured, I get this in the console:
Exception in thread "OEEngineServerThread" java.lang.ArrayIndexOutOfBoundsException: 3 at com.revelation.oesocketserver.EngineServerProtocol.startProcess(EngineServerProtocol.java:708) at com.revelation.oesocketserver.EngineServerProtocol.commonInit(EngineServerProtocol.java:63) at com.revelation.oesocketserver.EngineServerProtocol.<init>(EngineServerProtocol.java:36) at com.revelation.oesocketserver.OEEngineServerThread.run(OEEngineServerThread.java:75)Any ideas of what I'm doing wrong?
For the sake of closing this thread, Bryan reached out to me offline so I could give him a copy of my eserver.cfg to review. Here is the outcome:
AutoRun and RunFirst require the proc name, app name, username, and password to be identified via a comma delimited string. I did this, but my user didn't have a password. I ended my string with and without a training comma to no avail. I then added two quotes and this resolved that issue. In the end, however, Bryan figured out that these settings would not do what I was hoping they would do, which is to run a procedure on a periodic basis simply by launching the OEngineServer. They only work with engines that spin up as a result of the OECGI or other stateless processes. Instead, he pointed me to the SystemMonitor and SystemMonitorTime settings. These will allow me to identify one or more procedures to run automatically and on a periodic basis simply by launching the OEngineServer. There are some details one needs to know to use this correctly, but I refer you to version 3 of the OpenInsight OEngineServer Configuration.pdf documentation.