Ok, I have no real answers, but this is just an observation i've seen
sometimes on my mac(s) when doing dev with jetty (unrelated to lift).
Sometimes, and just sometimes it appears to get itself it a total melt
down and says its exited but checking the activity monitor shows that
it really is still running (or at least the java process is) and that
its eating a shed load of memory. A hasty force quit sorts it out
tho ;-)

BTW, are you using JavaRebel? If so, how have you got this setup?

Thanks

Tim

PS: Regarding DPP's comments, its nearly impossible to get on here
before he does... swear to god he must be loitering in the browser
window refreshing every couple of mins to keep it up ;-)

On May 26, 9:06 pm, David Pollak <[email protected]>
wrote:
> On Tue, May 26, 2009 at 12:08 PM, Joe Wass <[email protected]> wrote:
>
> > FWIW, it's a Mac Mini Intel Core 2 Duo with 2GB RAM @ 2GHz on Mac OS X
> > 10.5.6 running Ubuntu Server 9.04 in Sun VirtualBox.
>
> > I'm virtualising because production will be an Ubuntu VM and I prefer
> > to work with VMs for dev. IIRC the CPU isn't working hard inside or
> > outside of the VM when it takes a long time to load.
>
> > Running mvn jetty:run often takes a few seconds but once time in ten
> > it's out for a few minutes.
>
> Sounds to me like opening port 8080 is taking a lot of time.  That's be my
> guess.
>
>
>
> > As I'm working from the standard generated project layout I imagine
> > there's nothing extra to needs that I can disable?
>
> > I'll report back when it happens next.
>
> > (it's exciting to be working with such a great framework having the
> > BDFL replying personally -- thank you!)
>
> Glad you like it and it's pretty hard to shut me up on this list, so you're
> likely to get answers from me unless one of the other fine folks on the list
> beats me to the punch. ;-)
>
>
>
>
>
>
>
> > Joe
>
> > On May 26, 7:31 pm, David Pollak <[email protected]>
> > wrote:
> > > Hmmm...
>
> > > This all sounds odd.  In general, mvn jetty:run (if all the Scala classes
> > > are compiled) takes about 3 or 4 seconds, even on my slow box.
>
> > > Is your CPU at 100%?
>
> > > What kind of machine is hosting your ubuntu VM?
>
> > > On Tue, May 26, 2009 at 11:18 AM, Joe Wass <[email protected]>
> > wrote:
>
> > > > I've been looking at lift since yesterday morning (and scala for a
> > > > week or so) and I'm very pleased with what I see. I'm a little
> > > > frustrated though, Jetty appears to be breathtakingly slow to start
> > > > and stop occasionally. Sometimes the pause before this:
>
> > > > [INFO] Started Jetty Server
> > > > [INFO] Starting scanner at interval of 5 seconds.
>
> > > > is several minutes. Stopping Jetty can also be slow, with an equally
> > > > unsatisfactory pause. Sometimes it's instantaneous with no delay.
>
> > > > I'm running on Ubuntu Server on a virtual machine with ~700MB memory.
> > > > I'm not doing anything more complicated than that detailed in
> > > > tutorials.
>
> > > > Am I doing something wrong or is Jetty really this slow? It's only
> > > > running a few K of code...
>
> > > > I'm aware of the continual compilation option, but I'm editing
> > > > remotely and my editor appears to touch files more often than I save
> > > > (i.e. I'd like to be able to control when I compile).
>
> > > > Cheers
>
> > > > Joe
>
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > Follow me:http://twitter.com/dpp
> > > Git some:http://github.com/dpp
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to