cancel
Showing results for 
Search instead for 
Did you mean: 

studio.war takes a long time to deploy in 3.2 CE

nadaoneal
Champ in-the-making
Champ in-the-making
I've had to restart my fresh installation of the 3.2 Community Edition several times, and I've noticed that studio.war takes about 3 minutes to deploy… does anyone know why it's doing that, and/or what I can do to make it speedier? Is studio.war a necessary component?

09:49:33,118  INFO  [web.site.FrameworkHelper] Successfully Initialized Web Framework
Jul 17, 2009 9:49:33 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive share.war
09:49:36,256  INFO  [web.site.FrameworkHelper] Successfully Initialized Web Framework
Jul 17, 2009 9:49:36 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive studio.war
09:52:39,613  INFO  [web.site.FrameworkHelper] Successfully Initialized Web Framework
Jul 17, 2009 9:52:39 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jul 17, 2009 9:52:39 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
Jul 17, 2009 9:52:39 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 261210 ms

(261210ms=4.3 minutes, 3 minutes of which are studio.war)

I noticed one other board post where someone was having problems with studio.war taking a long time to start up - also about 3 minutes in their case. They're on a windows machine; I'm on RHEL 5.3, 32-bit, with the latest Sun java, Alfresco-embedded tomcat 6.0.18.
1 REPLY 1

kevinr
Star Contributor
Star Contributor
You can safely remove the studio.war if you are not using the WebStudio features (if you don't know what they are, then you are not using them Smiley Happy

Cheers,

Kev