Launching groovy app in Maven

We've developed a Groovy app. During development we use the following command line to run it

 C:\myapp>mvn grails:run-app

      

Without sending any request to the server, you can see the memory used by the java process grow and grow. When it starts at a speed of about 100 M, memory is allocated and after a couple of hours - without taking into account anything - the memory reaches 300 M.

When I run the application directly

C:\myapp> grails run-app

      

the consumed memory is somehow different, without sending any request, it somehow stabilizes at 110M. Sometimes it rises, sometimes it falls.

Although 300M is not critical, I would like to know if it is a memory leak or not.

Does anyone have similar behaviors?

Thanks!

0


a source to share


2 answers


It might be a memory leak in Maven, but rather a leak in the grails: run-app command. I would suggest putting this on the Grails development mailing list.



Why does this bother you? You should only use these commands for development, not production as you will be deploying the war file to production. If you're just concerned, the Grails developers mailing list is definitely the place to go for something like this.

0


a source


I doubt there is a memory leak here.

It is perfectly okay for the JVM to wait for the full GC to complete until it does. This means that if you allocate more memory, your java / groovy process will happily use it.

Most likely you have different default memory settings for Maven vs Grails. I'm not sure exactly how these properties are set on windows, but they look something like this:



GRAILS_OPTS = "- Xms100m -Xmx110m"

MAVEN_OPTS = "- Xms100m -Xmx300m"

0


a source







All Articles