Thanks guys for the helpful feedback.
I am not sure if my latest corrupted markup bug could be a biproduct of this
memory mauling.
yes I am in development mode on a live deployment under tomcat and mysql jetty
jdbc
it happened on the live server... so I was cussin a few over it
Here is a blip of my plugin config in my pom.xml
Do you think this is insufficient? Do I need to ass a permgen thing?
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.6</source>
<target>1.6</target>
<optimize>true</optimize>
</configuration>
</plugin>
<!-- Run the application using "mvn jetty:run" -->
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>${jetty-maven-plugin-version}</version>
<dependencies>
<dependency>
<groupId>${mysql.groupId}</groupId>
<artifactId>${mysql.artifactId}</artifactId>
<version>${mysql.jConnect.JDBC.version}</version>
<scope>compile</scope>
<!--
<systemPath>${env.MYSQL_CONNECTOR_HOME}/mysql-connector-java-5.0.4-bin.jar</systemPath>
-->
</dependency>
</dependencies>
<configuration>
<jvmArgs>-Xss131072</jvmArgs>
<jvmArgs>-Xms40m</jvmArgs>
<jvmArgs>-Xmx1024</jvmArgs>
<jettyXml>${basedir}/src/main/resources/jetty-env.xml</jettyXml>
<webXml>${basedir}/src/main/webapp/WEB-INF/web.xml</webXml>
<jettyEnvXml>${basedir}/src/main/resources/jetty-env.xml</jettyEnvXml>
