I was able to fix the OOM issue in Tapestry by bumping up the memory for
Maven by just a bit. For example, it'll fail no matter what I set JAVA_OPTS
to, but if I change MAVEN_OPTS from "" to "
--
View this message in context:
http://www.nabble.com/Memory-issues-with-Tape
ger, if I start up my app using "mvn jetty:run", browse a
>>> couple
>>> pages and hit Ctrl+C, it doesn't kill the process. I have to forcefully
>>> kill
>>> the process in order to shut down Jetty. This doesn't happen with the
>>> other
>>&g
kill
>> the process in order to shut down Jetty. This doesn't happen with the
>> other
>> web frameworks I'm using, so I'm confident it's caused by Tapestry 4.1.2.
>>
>> Thanks,
>>
>> Matt
>> --
>> View this message in context:
the
> other
> web frameworks I'm using, so I'm confident it's caused by Tapestry 4.1.2.
>
> Thanks,
>
> Matt
> --
> View this message in context:
> http://www.nabble.com/Memory-issues-with-Tapestry-4.1.x-tf4387514.html#a12508911
> Sent from the Tapestry - User
hanks,
Matt
--
View this message in context:
http://www.nabble.com/Memory-issues-with-Tapestry-4.1.x-tf4387514.html#a12508911
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTE
