• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • kkannaiy
  • Reporter: teck
  • July 23, 2009
  • 0
  • Watchers: 0
  • February 12, 2013
  • July 24, 2009

Description

If you use the tc-maven-plugin and set (to say adjust the heap for the L2 created with tc:start), when we run boot jar tool the same heap settings are used. This was annoying where the same pom was being used to start a server with 6GB heap, but running boot jar tool on machines that did not have that amount of memory (and boot jar tool failed in that case)

org.terracotta.maven.plugins tc-maven-plugin ${tc-maven-plugin.version} -Xms1g -Xmx1g

Comments

Kalai Kannaiyan 2009-09-14

I can reproduce the issue with tc-maven-plugin release-1.3.1,

Steps:

  1. svn co https://svn.terracotta.org/repo/forge/projects/tc-maven-plugin/tags/release-1.3.1
  2. edit the pom.xml from release-1.3.1/examples/tc-maven-plugin-sample -> to set -Xms8g -Xmx8g
  3. run mvn tc:start from release-1.3.1/examples/tc-maven-plugin-sample

Actual: Failed to start DSO server with message “Invalid initial heap size”

  1. run mvn tc:bootjar from release-1.3.1/examples/tc-maven-plugin-sample

Actual: Boot jar tool failed to create boot jar with message “Invalid initial heap size”

with tc-maven-plugin release-1.4.1, the boot jar tool creates the boot jar ignores the jvmargs, when it is set. i.e., it is working as expected.

Steps:

  1. svn co svn checkout \ http://svn.terracotta.org/svn/forge/projects/tc-maven-plugin/tags/release-1.4.1 \ tc-maven-plugin-1.4.1
  2. edit the pom.xml from tc-maven-plugin-1.4.1/examples/tc-maven-plugin-sample -> to set -Xms8g -Xmx8g
  3. run mvn tc:start from tc-maven-plugin-1.4.1/examples/tc-maven-plugin-sample

Actual: Failed to start DSO server with message “Invalid initial heap size”

  1. run mvn tc:bootjar from tc-maven-plugin-1.4.1/examples/tc-maven-plugin-sample

Actual: dso-boot.jar is created successfully (ignoring the jvmargs