rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marlon Pierce <marpi...@iu.edu>
Subject Re: Default tomcat6x timeout too low?
Date Fri, 13 Apr 2012 20:15:11 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Would it be better to use mvn cargo:run? This may need an upgrade to
cargo.


Marlon


On 4/13/12 3:41 PM, Jacob Hilker wrote:
> 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.
> 
> 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
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPiIlPAAoJEEfVXEODPFIDtBMIAICYOvgCMq3IDle8Y+HOSd6p
Y4aymH5MUpAt+S1rjFdGyUfrfgAp9ct3HdhDoJtHB2izggLSePzGAY7x0Xh+EFDP
eHLtUixLLvaBZugyD/nRLpfeCi4L8E0CusO/t0xjXg4hXjzifuJ1LiQ0gkaFZkpS
YW5/vBln8/OD4o+6a4CHmHFI2cqXLhEhCdt53Lkx5V2G8pSjXXIPL7eH6RCPU4e0
IyWSiPPmB2n4AytM3mCUt6/fsyY4yEPdMAJXQI6y5cGxZP/0Uza+gZfXW9RJYrMi
xFLYZYz/pjbn4BX/t735K7Ol6Tj94MUFoU5wTc4xbIvbT3H0h9IkI0dpAJjx6mg=
=LwoZ
-----END PGP SIGNATURE-----

Mime
View raw message