{"id":1705,"date":"2021-06-23T08:16:07","date_gmt":"2021-06-23T08:16:07","guid":{"rendered":"https:\/\/smartfoxserver.com\/blog\/?p=1705"},"modified":"2022-04-12T14:30:19","modified_gmt":"2022-04-12T14:30:19","slug":"running-multiple-sfs2x-instances-tomcat-edition","status":"publish","type":"post","link":"https:\/\/smartfoxserver.com\/blog\/running-multiple-sfs2x-instances-tomcat-edition\/","title":{"rendered":"Running multiple SFS2X instances (Tomcat edition)"},"content":{"rendered":"\n

For those interested in running multiple SFS2X instances on the same machine we have a short guide on how to setup each server correctly avoiding port conflicts.<\/p>\n\n\n\n

In particular since SFS2X 2.14<\/strong> we have switched from Jetty<\/strong> to Tomcat<\/strong> for the HTTP-related services and our previous article<\/a> on the same topic no longer applies.<\/p>\n\n\n\n\n\n\n\n

\u00bb SmartFoxServer’s ports<\/h3>\n\n\n\n

SmartFoxServer binds port 9933<\/strong> for both TCP<\/strong> and UDP<\/strong> so all we need is to use a different port value for every instance we intend to run on the same machine.<\/p>\n\n\n\n

Typically we recommend incrementing by one the port number: 9933, 9934, 9935 etc. So it’s easy to remember which port to use for each instance.<\/p>\n\n\n\n

\u00bb Tomcat’s ports<\/h3>\n\n\n\n

Tomcat uses a number of different ports:<\/p>\n\n\n\n

  • 8080<\/strong> for HTTP and WS (websocket)<\/li>
  • 8443<\/strong> for HTTPS and WSS (secure websocket)<\/li>
  • 8005<\/strong> which is referred to as the Shutdown port<\/em> and is only bound locally (not exposed outside)<\/li><\/ul>\n\n\n\n

    Here we need a bit more planning to make sure that every instance is using unique port values for these services. Once again incrementing every port by one can be a simple system to manage these parameters.<\/p>\n\n\n\n

    \u00bb How to proceed<\/h3>\n\n\n\n

    Launching the first instance doesn’t pose any issues as you can leave all default port values and the server will run just fine. However, when it’s time to launch the second instance you will need to manually edit a few files to configure the ports differently.<\/p>\n\n\n\n

    SmartFoxServer<\/strong><\/p>\n\n\n\n

    Navigate your file system and locate the SmartFoxServer installation folder. From there open the server.xml<\/strong> file located under SFS2X\/config\/<\/strong><\/p>\n\n\n\n

    At the top of the file you will find this section:<\/p>\n\n\n\n

    <socketAddresses>\n     <socket address=\"0.0.0.0\" port=\"9933\" type=\"TCP\"\/>\n     <socket address=\"127.0.0.1\" port=\"9933\" type=\"UDP\"\/>\n<\/socketAddresses><\/pre>\n\n\n\n
    where you can configure the port numbers to your needs.<\/p>\n\n\n\n
    Tomcat<\/strong><\/p>\n\n\n\n
    The configuration file to open is located under SFS2X\/lib\/apache-tomcat\/conf<\/strong> and is called, unsurprisingly, server.xml<\/strong><\/p>\n\n\n\n
    Here you will have to look for all the uncommented <Connector …<\/strong> blocks that can be found. Here’s how they look like:<\/p>\n\n\n\n
    <Connector connectionTimeout=\"20000\" port=\"8080\" protocol=\"HTTP\/1.1\" redirectPort=\"8443\"\/><\/pre>\n\n\n\n
    Out of the box you will find two, one set on TCP port 8080<\/strong>  for HTTP and another one set on TCP port 8443<\/strong> for HTTPS.<\/p>\n\n\n\n
    Also notice how the redirectPort<\/em> attribute references the HTTPS port value.  Make sure to change this as well, reflecting the new port numbers.<\/p>\n\n\n\n
    Finally look for this XML snippet:<\/p>\n\n\n\n
    <Server port=\"8005\" shutdown=\"SHUTDOWN\"><\/pre>\n\n\n\n
    This is the aforementioned Shutdown port<\/em> which also requires its unique value.<\/p>\n\n\n\n
    Now it is time to save the config and start the second SmartFoxServer instance. <\/p>\n\n\n\n
    If you need to run even more instances on the same local machine you will just need to repeat this process once again choosing more unique port values.<\/p>\n\n\n\n
    \u00bb Firewall Notes<\/h3>\n\n\n\n
    Running multiple server instances on the same machine doesn’t pose particular issues in terms of firewall rules, if you plan to also test locally (i.e. on the same machine).<\/p>\n\n\n\n
    However if you need external clients to reach the servers then make sure that all ports in use by all instances are configured in your firewall rules.<\/p>\n\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    For those interested in running multiple SFS2X instances on the same machine we have a short guide on how to setup each server correctly avoiding port conflicts. In particular since SFS2X 2.14 we have switched from Jetty to Tomcat for the HTTP-related services and our previous article on the same topic no longer applies.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[23],"tags":[66,7,116],"_links":{"self":[{"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/posts\/1705"}],"collection":[{"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/comments?post=1705"}],"version-history":[{"count":19,"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/posts\/1705\/revisions"}],"predecessor-version":[{"id":2237,"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/posts\/1705\/revisions\/2237"}],"wp:attachment":[{"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/media?parent=1705"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/categories?post=1705"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartfoxserver.com\/blog\/wp-json\/wp\/v2\/tags?post=1705"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}