How to control VM arguments for maven-jetty-plugin?

Question

How to set VM arguments for Jetty run from maven-jetty-plugin?

For example, I need to pass -Xmx arguments to Jetty run by the mvn jetty:run command.

I know that question is really old, but did you find a solution ? (I mean not add an argument for the whole JVM but only for jetty) I think Cargo would do the trick, but I don't feel like adding another thing to my project... — Depado, May 21 '12 at 10:02
-DargLine doesn't work with jetty:run, it works with jetty:run-forked — Gordon, Jan 01 '18 at 04:45

Michal Bernhard · Accepted Answer · 2017-09-12T12:17:00.273

61

The enviroment variable MAVEN_OPTS is the answer. The string content of MAVEN_OPTS is passed to JVM (java.exe).

Linux: in shell type export MAVEN_OPTS=....
Windows: in shell (cmd.exe) type set MAVEN_OPTS=...

For example: on Windows set MAVEN_OPTS="-Xmx1024m" sets the heap size of the Maven process to 1024mb.

Update (01.04.2013): Pass it directly to Jetty.

Matthew Farwell (please upvote his answer to give him credit) comes with the solution of using a forked JVM process to run Jetty which is a new feature of the Jetty plugin. This is a better solution as the former runs inside same JVM process as Maven (thus shares memory).

edited Sep 12 '17 at 12:17

answered Jan 05 '10 at 16:57

Michal Bernhard

3,755
3
25
37

1

Wouldn't that set it for the entire JVM run? Is there a way to get it to just affect the jetty that it starts? – BeepDog Sep 08 '11 at 15:28
1

yes it is - see (and vote up) the new answer from Matthew Farwell - there is new feature of jetty plugin to run jetty in separated jvm with own arguments – Michal Bernhard Apr 01 '13 at 07:03

score 46 · Answer 2 · edited Feb 07 '14 at 16:52

46

With more recent versions of the maven-jetty-plugin, you can use mvn:run-forked. The option jvmArgs will allow you to set -Xmx etc.

For more information, see: jetty:run-forked : Running an unassembled webapp in a separate jvm.

I think the original issue was Starting Jetty in separate JVM.

edited Feb 07 '14 at 16:52

condit

10,211
2
38
60

answered Nov 14 '12 at 21:57

Matthew Farwell

58,043
17
119
166

1

Solutions where Jetty assembles the WAR file prior to running it, are a problem in my case. When assembling the WAR file, the plugin appears to skip the 'filtering steps' I need when copying and packaging Web resources. The jetty:deploy-war goal simply uses a pre-built WAR file, but does not support the jvmArgs parameter. :-( Setting the MAVEN_OPTS env variable works, but I have to set it back for other apps I build. It would be nice if I could set the JVM options via the plugin config, keeping that config with the app that needs it. – Jack Straw Jan 29 '16 at 19:31

score 13 · Answer 3 · answered Jan 05 '10 at 16:01

It seems like your current approach is correct - when running jetty through maven, jetty is a thread inside the maven process. So increasing maven's heap will increase jetty's heap.

How are you setting MAVEN_OPTS?

One example I found looks like this: MAVEN_OPTS='-Xmx256m -Xms10m' mvn clean jetty:run

Note that MAVEN_OPTS is an environment variable here, and not passed to the JVM (who wouldn't know what to do with it).

Chris Ritchie · Answer 4 · 2019-09-02T19:49:35.940

9

To specify vm arguments via the command line (as originally asked) you can do the following:

mvn clean install -DargLine="-Xmx1524m"

edited Sep 02 '19 at 19:49

answered May 25 '15 at 15:04

Chris Ritchie

4,211
2
30
28

1

Under which circumstances does this work? Is it specific to jetty? For me, it didn't work, while setting MAVEN_OPT did. – glaed Jan 28 '17 at 14:55
mvn -DargLine="-Xmx1524m" clean install – cafebabe1991 Aug 24 '19 at 11:20
@cafebabe1991 Happy for you to comment on my post, and highlight errors, if there are any. Don't think it is necessary to modify my answer, since, it is my answer!! No idea why Stackoverflow would allow modification of someones answer because you don't like the order of where the -D flag goes. To my knowledge, the order is irrelevant. Reverted back to original answer. – Chris Ritchie Sep 02 '19 at 19:52
@ChrisRitchie If I remember correctly the -D was not being picked up by the maven unless it is in the order I specified. I agree that I shouldn't have edited your answer. – cafebabe1991 Sep 03 '19 at 09:07

score 4 · Answer 5 · edited Jun 05 '13 at 07:00

4

The <jvmArgs> param mentioned here : Maven jetty plugin didn't work for me .

Maven version : Apache Maven 3.0.3

Jetty Maven plugin version : jetty-maven-plugin:8.1.10.v20130312

This worked :

MAVEN_OPTS='-Xmx4096m -Xms4096m'
export MAVEN_OPTS
mvn jetty:run &

edited Jun 05 '13 at 07:00

Ankur

5,018
19
35
62

answered Jun 05 '13 at 06:42

Binita Bharati

2,998
28
20

score 2 · Answer 6 · answered Apr 23 '12 at 15:20

2

On Linux/Unix

export MAVEN_OPTS="-Xmx256m" && mvn clean install jetty:run

will do the trick

answered Apr 23 '12 at 15:20

Gonzalo Gómez García

51
3

1

This leaves the variable set for later executions, which might not be intended. – Raúl Salinas-Monteagudo May 28 '13 at 08:23

score 2 · Answer 7 · answered Dec 02 '12 at 03:15

2

The plugin allows you to specify jvmArgs like this:

<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<configuration>
    <jvmArgs>-Xmx1024</jvmArgs>
    <scanIntervalSeconds>10</scanIntervalSeconds>
    <connectors>
        <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
            <port>8080</port>
            <maxIdleTime>60000</maxIdleTime>
        </connector>
    </connectors>
    <webAppConfig>
        <jettyEnvXml>jetty-env.xml</jettyEnvXml>
    </webAppConfig>
</configuration>
<executions>
    <execution>
        <phase>test</phase>
        <goals>
            <goal>run-exploded</goal>
        </goals>
    </execution>
</executions>
</plugin>

answered Dec 02 '12 at 03:15

doredson

55
2

did not work for me, I tried: org.mortbay.jetty jetty-maven-plugin 8.1.5.v20120716 -Xmx2048M -XX:MaxPermSize=2048m ${project.basedir}/war ${project.basedir}/war/WEB-INF/web.xml – davidjnelson Jan 16 '13 at 20:17
1

@davidjnelson You need to use `jetty:run-forked` goal. See: Matthew Farwell's answer above: http://stackoverflow.com/a/13388081/19501. – amit Oct 18 '13 at 04:04
But how to have jetty run as `jetty:run-forked` when the command being typed in is `mvn clean install` ? – Stephane Dec 18 '15 at 10:33

score 0 · Answer 8 · answered Mar 14 '14 at 06:25

you can use to pass -Xmx argument like;

<plugin>
            <groupId>org.eclipse.jetty</groupId>
            <artifactId>jetty-maven-plugin</artifactId>
            <version></version>
            <configuration>
                <jvmArgs>-Xmx -Xms -XX:PermSize= -XX:MaxPermSize= -XX:+HeapDumpOnOutOfMemoryError</jvmArgs>
                <scanIntervalSeconds>1</scanIntervalSeconds>
                <stopKey>stop-jetty</stopKey>
                <stopPort>9999</stopPort>
                <systemProperties>
                    <systemProperty>
                        <name>jetty.port</name>
                        <value>9090</value>
                    </systemProperty>
                    <systemProperty>
                        <name>spring.profiles.active</name>
                        <value></value>
                    </systemProperty>
                </systemProperties>

                <webApp>
                    <contextPath>/</contextPath>
                </webApp>
            </configuration>
        </plugin>

score 0 · Answer 9 · answered Aug 21 '16 at 10:22

There is no way using the commandline. But you could copy the mvn.cmd / mvn.sh to mvnhp.cmd and change the line

%MAVEN_JAVA_EXE% %JVM_CONFIG_MAVEN_PROPS% %MAVEN_OPTS% %MAVEN_DEBUG_OPTS% -classpath %CLASSWORLDS_JAR% "-Dclassworlds.conf=%M2_HOME%\bin\m2.conf" "-Dmaven.home=%M2_HOME%" "-Dmaven.multiModuleProjectDirectory=%MAVEN_PROJECTBASEDIR%" %CLASSWORLDS_LAUNCHER% %MAVEN_CMD_LINE_ARGS%

To

%MAVEN_JAVA_EXE% -Xmx1024m %JVM_CONFIG_MAVEN_PROPS% %MAVEN_OPTS% %MAVEN_DEBUG_OPTS% -classpath %CLASSWORLDS_JAR% "-Dclassworlds.conf=%M2_HOME%\bin\m2.conf" "-Dmaven.home=%M2_HOME%" "-Dmaven.multiModuleProjectDirectory=%MAVEN_PROJECTBASEDIR%" %CLASSWORLDS_LAUNCHER% %MAVEN_CMD_LINE_ARGS%

How to control VM arguments for maven-jetty-plugin?

9 Answers9

Linked

Related