When one of the files in the tomcat "work" directory gets locked by another process (for example by not fully stopped tomcat instance), Configurator fails to proceed with copying webapp contexts files. This may lead to issues with Tomcat without any indication of the problem in Configurator.
The following errors may occur if SBM is started while the SBM database is not accessible. If you start SBM while the SBM database is not running or is not accessible but later make it accessible the normal user interface will be fine because IIS is able to recover gracefully. Tomcat on the other hand isn't able to recover from this and you will consequently see the following issues until the Tomcat service is restarted while the database is available.
The following error may appear in the configurator log file:10/02/2015 00:08:23 Error Failed to remove temp directory before starting 'SbmTomcat' service. System.IO.IOException: The process cannot access the file 'axis26783005866019009068addressing-1.6.1.mar' because it is being used by another process.
to {SBM Dir}\Common\tomcat\server\default\webapps\commonsvc\payload when it doesn't have to. While it's important to have the SLS information in the database, this copying action should occur only with a new database, and not when the database has already been initialized.
This will typically happen when there is another application such as Version Manager occupying Tomcat's SHUTDOWN port 8005. In such a case modify either the SBM Tomcat SHUTDOWN port or the SHUTDOWN port of the other product to something else so that there is no conflict. The SHUTDOWN port is configured in ...\Tomcat 7.0\server\default\conf\server.xml file.
The most common place to look for errors related to JBoss or Tomcat having a hard time communicating with the database server is to look in the server.log. You will most likely see the following errors when these services start .
