Alex,
Any reason your running the install goal? You really don't need to.
Regarding the permgen: Can you show your maven options? You can
improve the situation by setting a larger heap size, however this is
an unfortunate thing that just goes along with jetty and maven.
HTH
Cheers, Tim
On Oct 8, 7:10 pm, Alex Black <a...@alexblack.ca> wrote:
> I've encountered this error 3 times, running Jetty and Maven, just
> trying out Lift scala with a hello-world like website.
>
> I have to kill the JVM with "kill -9" and restart things to fix it,
> any ideas?
> - Command line: "mvn install jetty:run"
> - I'm using Lift 1.0, Scala 2.7.6 final, 64bit JDK1.6.0_16, on Ubuntu
> Desktop x64.
> - My app is trivial, no comet or actors or mapping, one view, one
> class, lists records out of a postgres database table (which has 2
> records in it, 2 columns)
>
> Here are the errors from the terminal running jetty, I am not sure if
> the actor/SessionMaster errors are related to the memory errors.
>
> ERROR - Couldn't start SessionMaster ping
> net.liftweb.util.ActorPingException: net.liftweb.http.SessionMaster
> $checkandpur...@7130bd0a could not be scheduled on
> net.liftweb.http.sessionmast...@36cb1594
> at net.liftweb.util.ActorPing$.schedule(ActorPing.scala:51)
> at net.liftweb.http.SessionMaster$.net$liftweb$http$SessionMaster$
> $doPing(LiftSession.scala:209)
> at net.liftweb.http.SessionMaster$$anonfun$act$1$$anonfun$apply
> $1.apply(LiftSession.scala:200)
> at net.liftweb.http.SessionMaster$$anonfun$act$1$$anonfun$apply
> $1.apply(LiftSession.scala:169)
> at scala.actors.Reaction.run(Reaction.scala:78)
> at scala.actors.FJTask$Wrap.run(Unknown Source)
> at scala.actors.FJTaskRunner.scanWhileIdling(Unknown Source)
> at scala.actors.FJTaskRunner.run(Unknown Source)
> Caused by: java.util.concurrent.RejectedExecutionException
> at java.util.concurrent.ThreadPoolExecutor
> $AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1760)
> at java.util.concurrent.ThreadPoolExecutor.reject
> (ThreadPoolExecutor.java:767)
> at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute
> (ScheduledThreadPoolExecutor.java:216)
> at java.util.concurrent.ScheduledThreadPoolExecutor.schedule
> (ScheduledThreadPoolExecutor.java:379)
> at java.util.concurrent.Executors
> $DelegatedScheduledExecutorService.schedule(Executors.java:654)
> at net.liftweb.util.ActorPing$.schedule(ActorPing.scala:49)
> ... 7 more
> INFO - Service request (GET) / took 1411 Milliseconds
> INFO - Service request (GET) /classpath/jquery.js took 7 Milliseconds
> [INFO] restarting
> org.mortbay.jetty.plugin.jetty6pluginwebappcont...@5dbb6a69{/,/home/
> alex/dev/poc/src/main/webapp}
> 2009-10-08 14:06:44.221::WARN: Error for /ajax_request/liftAjax.js
> java.lang.OutOfMemoryError: PermGen space
> 2009-10-08 14:06:47.424::WARN: failed LiftFilter:
> java.lang.OutOfMemoryError: PermGen space
> 2009-10-08 14:06:48.053::WARN: failed servlethand...@4838ddcc:
> java.lang.OutOfMemoryError: PermGen space
> 2009-10-08 14:06:48.053::WARN: failed securityhand...@d69a11f:
> java.lang.OutOfMemoryError: PermGen space
> 2009-10-08 14:06:48.053::WARN: failed sessionhand...@11d1011a:
> java.lang.OutOfMemoryError: PermGen space
> 2009-10-08 14:06:48.053::WARN: failed
> org.mortbay.jetty.plugin.jetty6pluginwebappcont...@5dbb6a69{/,/home/
> alex/dev/poc/src/main/webapp}: java.lang.OutOfMemoryError: PermGen
> space
> 2009-10-08 14:06:48.053::WARN: EXCEPTION
> java.lang.OutOfMemoryError: PermGen space
> Exception in thread "Timer-1" java.lang.OutOfMemoryError: PermGen
> space
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
