Environment variables and parameters of the start are set in the
setenv.sh script. In this script you can se use additional parameters for WCS Core and WCS Manager. Also, here you can set the parameter that prevent memory leaks on multi-CPU systems:
In some cases, for example, if the server won't start and does not produce any errors, you may need to start the server with direct logging to the '
stdout' console. Direct output to
stdout cannot be used in production, because the server will be stopped if the console is closed or the SSH connection is lost. That is why we recommend using
stdout output only for debug purposes.
cd /usr/local/FlashphonerWebCallServer/bin sudo ./webcallserver start standalone
Starting with JVM output redirection to a log file
Since build 5.2.1562 WCS may be launched with JVM output redirected to a file like direct
sudo ./webcallserver start --java-log
In this case, all Java output will be redirected to the
/usr/local/FlashphonerWebCallServer/logs/java.log file. The feature should be used for debugging purposes only but not in production, because the resulting file size may be too large.
Launching with different user permissions