I assume it is Tomcat that is running out of memory. You will need to
increase the heap size when running Tomcat. To do this set the environment
variable CATALINA_OPTS to contain:
-Xms64m -Xmx512m
The above values are examples - feel free to change the numbers as suits.
See the following thread
I tried to deploy the same project to tomcat using the default maven plugin
by doing
mvn tomcat:deploy and it runs out of java heap memory space. I am not sure
where I can increase the heap size now. Why would it run out of heapspace.
This is the ONLY app it has in tomcat.
Thanks for your help
No need to build a whole new project! It is possible to configure Maven to
switch from using Jetty to using Tomcat, but before going down that route I
would suggest trying to deploy your project to Tomcat manually to see if it
solves the problem. If it does, the switch can be made.
To do a manual
Thanks, Mike.
I do have the jar files containing these classes in the WEB-INF/lib
directory.
It looks like jetty is invoking this webappclassloader right. Pentaho is a
reporting application I am invoking.
How do I switch from using Jetty to Tomcat using the appfuse-struts m4 basic
project. I
Very easily I'm afraid. The call stack is unrelated to the classloading
mechanism. I am also unable to see the same class appearing in the call
stack - it complains it is missing
com.pentaho.repository.subscribe.SubscriptionHibernateHandler whereas the
class in your call stack is
com.pentaho.repos
Hi Matt et al,
I have a strange class loading problem when running with mvn jetty. The
webapplication framework is based on appfuse and I am trying to get another
standalone application running in it. Please ignore for now that
application. The strange problem is that jetty webappclassloader is
