I tried to restart my server (linux suse pro 8.2) through the webpage admin pages.
I received the message ‘Servoy Application Server is now restarting…’ and waited a while but didn’t see my server come up again.
Looking in the console of the machine showed me that the server was plain down…
how did you start the server?
which shells script dit you use?
Can you post the contents of that script
From within the servoy root I started the server as a foreground process with ./servoy_server.sh
The script has default settings.
as i asked.. i need to see the contents of that sh file (to see if you have a updated/good one for restart support)
ah ok, I understand. Here it is:
java -Djava.awt.headless=true -classpath .:lib/commons-collections.jar:lib/commons-dbcp.jar:lib/commons-pool.jar:lib/activation.jar:lib/antlr.jar:lib/j2db.jar:lib/j2dbdev.jar:lib/compat141.jar:lib/jh.jar:lib/jndi.jar:lib/js.jar:lib/jta.jar:lib/mail.jar:lib/jug.jar:lib/jdbc2_0-stdext.jar:lib/naming-common.jar:lib/naming-resources.jar:lib/servlet.jar:lib/xerces.jar:lib/server-bootstrap.jar:lib/commons-fileupload-1.0.jar:lib/commons-logging.jar:lib/hibernate2.jar com.servoy.j2db.server.ApplicationServer
and that is the wrong file
(don’t know exactly if that file is being updated with the auto-update)
it should be this:
#!/bin/sh
while true
do
java -Djava.awt.headless=true -classpath .:lib/commons-collections.jar:lib/commons-dbcp.jar:lib/commons-pool.jar:lib/activation.jar:lib/antlr.jar:lib/j2db.jar:lib/j2dbdev.jar:lib/compat141.jar:lib/jh.jar:lib/jndi.jar:lib/js.jar:lib/jta.jar:lib/mail.jar:lib/jug.jar:lib/jdbc2_0-stdext.jar:lib/naming-common.jar:lib/naming-resources.jar:lib/servlet.jar:lib/xerces.jar:lib/server-bootstrap.jar:lib/commons-fileupload-1.0.jar:lib/commons-logging.jar:lib/hibernate2.jar com.servoy.j2db.server.ApplicationServer
EXITCODE=$?
if [ “$EXITCODE” != 99 ]; then exit $EXITCODE; fi
done
Ah, in that case I think the file was not updated with the auto-update process… All testing I do is with systems running with 2.0rc9.