Copying and renaming a webapp may result in a failure to start the Sage CRM webapps. If a webapp is to be backed up (prior to amending settings, for example), the backup should not be stored in the ..\CRM\tomcat\webapps directory.


The Tomcat catalina.log may indicate that the Tomcat web server is attempting to deploy an unfamiliar webapp:

INFO: Deploying web application directory C:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmjOLD
SEVERE: Error listenerStart

The ..\CRM\tomcat\logs\localhost.log shows the following:

SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.util.Log4jConfigListener
java.lang.IllegalStateException: Web app root system property already set to different value: 'crmj' = [C:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmj\] instead of [C:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmjOLD\] - Choose unique values for the 'webAppRootKey' context-param in your web.xml files!
 at org.springframework.web.util.WebUtils.setWebAppRootSystemProperty(
 at org.springframework.web.util.Log4jWebConfigurer.initLogging(
 at org.springframework.web.util.Log4jConfigListener.contextInitialized(
 at org.apache.catalina.core.StandardContext.listenerStart(
 at org.apache.catalina.core.StandardContext.startInternal(
 at org.apache.catalina.util.LifecycleBase.start(
 at org.apache.catalina.core.ContainerBase.addChildInternal(
 at org.apache.catalina.core.ContainerBase.addChild(
 at org.apache.catalina.core.StandardHost.addChild(
 at org.apache.catalina.startup.HostConfig.deployDirectory(
 at org.apache.catalina.startup.HostConfig$
 at java.util.concurrent.Executors$ Source)
 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 at Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$ Source)
 at Source)



This is expected behaviour - Tomcat will attempt to deploy and execute any webapp found in the ..\CRM\tomcat\webapps directory. the duplicate webapp will cause an error when it loads. Copies of the webapp directories or WAR files should not be stored in this directory.


Removing the backup webapp resolves the issue.