Our live servers were at version 2.20 recently I patched them to 2.20.3 and it overrode server.xml and jks file. it is not problem though I fixed them reset the ports. But at every sfs server runs with the test server in the same machine so we use test server to test changes. we put jars to test server and quickly test it. test server ports different in order to work side by side with live server. we increased every port +1 for example shutdown port is 8006 at test server 8005 at live server. after 2.20.3 upgrade when I stop (./sfs2x-service stop) test smartfox instance live server also stops. actually only tomcat stops websockets closes. That is kind of nightmare I switched both 8005 to 8008 and 8007 because there might be default shut down port. maybe that fixes problem but I can not test it. Because I already shut down live server couple of times unintentionally.
Thanks
Smartfox 2.20.3 upgrade tomcat configuration problem
Re: Smartfox 2.20.3 upgrade tomcat configuration problem
It would be best to run tests on a different machine than the live server.
As regards the sfs2x-service launcher, that is not affected by any of the update patches of the 2.20.x series, including 2.20.3 so I can't see a reason why the patch would have changed its behavior.
The script tracks the server's pid in the system, depending on how your system is configured it might be that on stop the script detects the wrong pid... I can't say for sure without knowing all the details. Additionally the launcher script is not done by us, it is auto-created by the third-party installer application we use (Install4J).
If you don't have any other choice but running the live and test servers on the same machine I'd recommend not to use the same script to launch the test server. Instead use the sfs2x.sh for example which does not depend on the application pid.
Cheers
As regards the sfs2x-service launcher, that is not affected by any of the update patches of the 2.20.x series, including 2.20.3 so I can't see a reason why the patch would have changed its behavior.
The script tracks the server's pid in the system, depending on how your system is configured it might be that on stop the script detects the wrong pid... I can't say for sure without knowing all the details. Additionally the launcher script is not done by us, it is auto-created by the third-party installer application we use (Install4J).
If you don't have any other choice but running the live and test servers on the same machine I'd recommend not to use the same script to launch the test server. Instead use the sfs2x.sh for example which does not depend on the application pid.
Cheers