Speed-up share restart

[jackjm]

Hello all

I have noticed more than a couple instances where contributors like Jeff Potts and other Alfresco bloggers mention a setup where 'share can restart quickly' when they a run things in a particular fashion. Can anyone please suggest how this can be done and provide some details? I spend quite some time waiting every time I am working on customizing share and even a few seconds every re-start can help a lot during a day's work

Any feedback will be greatly appreciated.

Thanks a lot

[jpotts]

Here is my setup.

The repository and the Alfresco webapp runs on Tomcat on port 8080. That Tomcat lives in /opt/apache/tomcat/apache-tomcat-6.0.32. This tomcat has only the alfresco.war deployed to it. If you are running solr, it would be deployed here as well.

The Share webapp runs on a second instance of Tomcat on port 8081. That Tomcat lives in /opt/apache/tomcat81/apache-tomcat-6.0.32. This tomcat has only the share.war deployed to it. If you are running Web Quick Start, you might have your WQS-based WARs deployed here as well.

You can Google the directions for running two tomcats, but it basically involves making sure you don't have any port conflicts. So you could copy your repo Tomcat's configuration and then edit conf/server.xml to change:
- 8080 to 8081
- 8005 to 8006 (Shutdown port)
- 8009 to 8010 (AJP Connector port)

If you are using SSL you'll have to change those ports.

If you are doing remote debugging from Eclipse you'll have to make sure not to run jpda in both Tomcats simultaneously (or else adjust the JPDA ports accordingly).

Now you start both Tomcats up. When you want to do stuff on the repo you use 8080. When you want to hit Share you go to 8081. And when you need to restart to pick up a change on the Share tier, you restart only the 8081 Tomcat, which will restart very quickly.

Jeff

[jackjm]

Jeff

Thank you very much for this info; it is very helpful and does save a lot of time incrementally

best regards