You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2018/03/19 08:05:00 UTC

[jira] [Resolved] (DAEMON-382) High memory consumption

     [ https://issues.apache.org/jira/browse/DAEMON-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Thomas resolved DAEMON-382.
--------------------------------
    Resolution: Invalid

Java heap allocation != maximum process memory usage.

There are lots of factors that can account for the additional memory usage and the situation you describe is not abnormal. The users list is the place to get help if you need further advice.

> High memory consumption
> -----------------------
>
>                 Key: DAEMON-382
>                 URL: https://issues.apache.org/jira/browse/DAEMON-382
>             Project: Commons Daemon
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>         Environment: C:\ReportLoq\ReportLoqService.exe //IS/ReportLoq --DisplayName="ReportLoq Server" --Startup=auto --StartPath=C:\ReportLoq --StartMode=jvm --StopMode=jvm --Jvm="C:\Program Files\Java\jdk1.8.0_151\jre\bin\server\jvm.dll" --StartClass=dk.flsmidth.sitecalculator.Launcher --StartMethod=start --StopClass=dk.flsmidth.sitecalculator.Launcher --StopMethod=stop --Classpath c:\ReportLoq\site-calc.jar --JvmOptions=-Duser.timezone=UTC ++JvmOptions=-Dcom.sun.management.jmxremote.port=8686 ++JvmOptions=-Dcom.sun.management.jmxremote.authenticate=false ++JvmOptions=-Dcom.sun.management.jmxremote.ssl=false --JvmMx=4096 --JvmMs=2048 --StartParams=-headless --Description="FLSmidth" --StdOutput=C:\ReportLoq\logs\service-out.txt --StdError=C:\ReportLoq\logs\service-err.txt --LogPath="c:\ReportLoq\logs"
>            Reporter: Kenneth Vindum
>            Priority: Major
>         Attachments: Capture.PNG
>
>
> Memory consumption of procsrv.exe is much higher than requested by JvmMx.
> I've set the --JvmMX=4096 but the .exe process is consuming nearly 7GB of memory dispite the fact that the JVM only consumed the requested 4GM. The remaining 3GB seems to be consumed by procsrv.exe
> Please see the attached screenshot



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)