Hello Angelo
Yes, I use 1.6 64 bits for development in SL, however I normally let CI
servers generate the artifacts that are deployed and they have do have the
same virtual machine as the target servers.
In theory running something in a different Virtual Machine should work (at
least that's one
This works. SL's default java is 1.6 and 64 bits, are you using the default
for development of T5 apps?
Alejandro Scandroli wrote:
>
> I did have "heap out of memory" issues with SL. To workaround them we
> use this system properties.
>
> For embedded jetty (mvn jetty:run): export MAVEN_OPTS="
Hi Juan,
finally i found out the problem, i defined the memory size in JAVA_OPTS, it
does not pick up by jetty, setting it in MAVEN_OPTS solves the problem.
A related question, if we use JAVA 6 64 bits, can it be deployed in a 64 bit
linux server?
Thanks,
Angelo
Juan E. Maya wrote:
>
> Ang
I did have "heap out of memory" issues with SL. To workaround them we
use this system properties.
For embedded jetty (mvn jetty:run): export MAVEN_OPTS="-Xms256m
-Xmx1024m -XX:PermSize=1024m -XX:MaxPermSize=1024m"
For tomcat: export JAVA_OPTS="-Xms1024m -Xmx1024m -XX:MaxPermSize=256m
-XX:+CMSClass
Angelo, i have been working with Snow Leopard and Tapestry since SL came out
and never have i ever encounter a compatibility problem. I think as u
pointed out the problem might be related with JAI not with tapestry.
On Tue, Apr 13, 2010 at 9:08 AM, Angelo Chen wrote:
>
> Hi,
>
> I moved recently
