Connection Binding

This lists all the files that need modified, as well as changes to the database, if an anthillpro server is set to bind to an IP, and that IP changes on the host machine. PLEASE NOTE that all testing performed on a 3.7.1_53990 server, and this guide will likely differ for newer versions of anthill, especially ones part of the 3.8 branch! If the bind is incorrect from the current IPs available to the server, an error message will appear most likely stating Cannot assign requested address: JVM Bind.

Changing IPs of the anthillpro server

If a server is bound by an IP address, and is not considering all IP addresses for communication, the following will need to be changed:

  • %SERVER_HOME%\conf\server\
  • installed.properties
  • Find the line that says 'install.server.web.ip' and change it to '0.0.0.0'
  • activemq.xml
  • Find the line that starts '<transportConnector uri=...' and change ONLY the IP address portion to '0.0.0.0'. Leave ports and closing tag intact.
  • %SERVER_HOME%\opt\tomcat\conf\
  • server.xml
  • Make sure that the 'address' section is set to "0.0.0.0"
  • Finally, update the database
  • Retrieve current info from the database
  • SELECT DATA FROM SINGLETON WHERE ID=1 AND CLASS LIKE '%ServerSettings'
    
  • Set new information in the database
  • UPDATE SINGLETON SET DATA='...' WHERE ID=1 AND CLASS LIKE '%ServerSettings'
    
Change ONLY the bind-ip and the connector-ip in the XML that is in the DATA CLOB.

Please keep in mind that it is never a good idea to bind to anything other than 0.0.0.0; this way the server will accept any new IP address and steps like this can be avoided in the future.