Following "Removing the 'crowd' Context from the Application URL" documentation may lead to two Crowd applications deployed on same Tomcat instance.
The problem is with the 4th step of the instruction
Rename the crowd.xml file in <Crowd-Install>/apache-tomcat/conf/Catalina/localhost to crowdbackup.xml to prevent Tomcat from loading the /crowd context.
as it may suggest leaving the descriptor xml in the <Crowd-Install>/apache-tomcat/conf/Catalina/localhost.
Having both crowdbackup.xml in the <Crowd-Install>/apache-tomcat/conf/Catalina/localhost and the:
in the <Crowd-Install>/apache-tomcat/conf/server.xml may lead to two Crowd deployments on the same tomcat instance connected to the same database.
This in turns may cause unexpected Crowd behaviour and race conditions.
It would be best to backup the descriptor outside of the <Crowd-Install>/apache-tomcat/conf/Catalina/localhost.
1. Run jconsole and connect to Tomcat javaprocess.
2. In Catalina / WebModule subtree you should be able to see deployed applications with their context path
3. Make sure that there is no crowdbackup or any other module that points to Crowd webapp files like in the following example:
One may also check for the following log entries:
and another one some time later
which are then then followed up with two log entires such as:
occurring shortly after each other (there are no entries about Crowd being stopped in between).
Please note that running
will yield only one result