On 16 April 2012 14:21, Ciancetta, Jesse E. <[email protected]> wrote: > >-----Original Message----- > >From: Jacob Hilker [mailto:[email protected]] > >Sent: Friday, April 13, 2012 3:42 PM > >To: [email protected] > >Subject: Default tomcat6x timeout too low? > > > >Hi All, > > > >While helping set up a local instance of rave on one of my co-workers > >machines, we ran into an issue where using mvn cargo:start was taking > >longer than 3 minutes, the default timeout, and thus failing. > > > >The fix was simple enough, as we just up'ed the timeout period, and as > >such, he successfully deployed rave in approximately 4.5 minutes. > > Do you know what it was that was taking so long to initialize? > > That seems like a really long time for a webapp to initialize -- maybe we > could change something to shorten the time it takes? >
I can imagine it takes a long time the first time when you haven't used cargo before and need to download the maven plugin + dependencies over a slow connection. Is it faster the second time? Do you have a virusscanner that checks what happens in the local maven repository and the rave checkout? This may also slow down the startup. Jasha > > >However this raises the question of if a preemptive fix for other new > users > >should be added to the rave codebase, upping the default timeout period to > >5 minutes, or even higher? I'm sure there will be other users with slower > >than average machines attempting to deploy rave. > > > >rave-portal/pom.xml line 195: <timeout>180000</timeout> > > > >Thanks, > > > >Jacob Hilker >
