Return-Path: <issues-return-57670-archive-asf-public=cust-asf.ponee.io@commons.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 5951A200BD8
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue,  1 Nov 2016 19:53:01 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 57B0A160AF7; Tue,  1 Nov 2016 18:53:01 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 8D249160ADA
	for <archive-asf-public@cust-asf.ponee.io>; Tue,  1 Nov 2016 19:53:00 +0100 (CET)
Received: (qmail 15670 invoked by uid 500); 1 Nov 2016 18:52:59 -0000
Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@commons.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@commons.apache.org>
List-Post: <mailto:issues@commons.apache.org>
List-Id: <issues.commons.apache.org>
Reply-To: issues@commons.apache.org
Delivered-To: mailing list issues@commons.apache.org
Received: (qmail 15380 invoked by uid 99); 1 Nov 2016 18:52:59 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2016 18:52:59 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id D94222C2AB9
	for <issues@commons.apache.org>; Tue,  1 Nov 2016 18:52:58 +0000 (UTC)
Date: Tue, 1 Nov 2016 18:52:58 +0000 (UTC)
From: "Guillaume Chauvet (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12702129.1395145478000.147190.1478026378886@Atlassian.JIRA>
In-Reply-To: <JIRA.12702129.1395145478000@Atlassian.JIRA>
References: <JIRA.12702129.1395145478000@Atlassian.JIRA> <JIRA.12702129.1395145478068@arcas>
Subject: [jira] [Commented] (DAEMON-316) High JvmMx values result in the
 service being un-startable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 01 Nov 2016 18:53:01 -0000


    [ https://issues.apache.org/jira/browse/DAEMON-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626321#comment-15626321 ] 

Guillaume Chauvet commented on DAEMON-316:
------------------------------------------

Silly question : is it a 32 bit JVM ?

> High JvmMx values result in the service being un-startable
> ----------------------------------------------------------
>
>                 Key: DAEMON-316
>                 URL: https://issues.apache.org/jira/browse/DAEMON-316
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.15
>         Environment: Windows 7 64bit
>            Reporter: Joachim Steffenhagen
>            Priority: Critical
>
> When I specify the JvmMx and use a large value, it will result in an error during service start. A value of 1240 will still work, however when changing it to 2240, the service installation is running ok, but when I start the service in windows, it just shuts down immediately with an error message referring to service specifiec error code 4. looking into the windows event log, it displays this info:
> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
> - <System>
>   <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> 
>   <EventID Qualifiers="49152">7024</EventID> 
>   <Version>0</Version> 
>   <Level>2</Level> 
>   <Task>0</Task> 
>   <Opcode>0</Opcode> 
>   <Keywords>0x8080000000000000</Keywords> 
>   <TimeCreated SystemTime="2014-03-18T12:17:02.546588300Z" /> 
>   <EventRecordID>153783</EventRecordID> 
>   <Correlation /> 
>   <Execution ProcessID="864" ThreadID="3736" /> 
>   <Channel>System</Channel> 
>   <Computer>mycomputer</Computer> 
>   <Security /> 
>   </System>
> - <EventData>
>   <Data Name="param1">MyService</Data> 
>   <Data Name="param2">%%4</Data> 
>   </EventData>
>   </Event>
> I am installing it using 
> "$INSTDIR\prunsrv.exe" //IS//MyService --Install="$INSTDIR\prunsrv.exe" --Startup=auto \
>         --Description="VTS" --Jvm=auto \
>         ++JvmOptions="-Djavax.net.ssl.trustStore=$INSTDIR\resources\cacerts.jks";"-Djavax.net.ssl.trustStorePassword=changeit" \
>         --Classpath="$INSTDIR\MyService.jar";"$INSTDIR\log4j-1.2.15.jar";"$INSTDIR\jcifs-1.3.17.jar";"$INSTDIR\jasypt-1.9.0.jar" \
>         --StartImage=MyService.jar \
>         --JvmMs=1024 --JvmMx=2240 \
>         --StartPath="$INSTDIR" --StartMode=jvm \
>         --StartClass=de.volke.terminal.service.TerminalService --StartMethod=main --StartParams=start --StopMode=exe \
>         --StopClass=de.volke.terminal.service.TerminalService --StopMethod=main --StopImage=MyService.jar \
>         --StopPath="$INSTDIR" --StopParams=stop --LogPath="$INSTDIR\logs"
> from an NSIS script.
> To me this seems like a bug as apparenlty the error should be constant in case my whole cmd line is wrong. Else it should also accept the higher JvmMx value as this is the maximum, no matter if this much memory is really available. The behaviour was also seen on machines having 16GB RAM with >10GB free. So it appears not be related to the real memory consumption on the machine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)