Increasing memory for Jetty with --exec in start.ini causes shibb service to fail on start.

[Rich Thomas]

Trying to increase Jetty memory per
https://wiki.shibboleth.net/confluence/display/IDP30/Jetty93
but when "--exec" is added, the shibb service starts then fails. We are
running IDP 3.2.1 on Windows.

Only log output I get is in ProcRun shibd_idp-stderr log 

2016-02-18 15:09:41 Commons Daemon procrun stderr initialized
2016-02-18 15:09:42.485:INFO::main: Logging initialized @255ms
2016-02-18 15:09:42.548:WARN:oejx.XmlConfiguration:main: Config error at
<New id="ServerLog" class="java.io.PrintStream"><Arg>|        <New
class="org.eclipse.jetty.util.RolloverFileOutputStream"><Arg><Property
name="jetty.logs" default="./logs"/>/yyyy_mm_dd.stderrout.log</Arg><Arg
type="boolean">false</Arg><Arg type="int">90</Arg><Arg><Call
class="java.util.TimeZone"
name="getTimeZone"><Arg>GMT</Arg></Call></Arg><Get id="ServerLogName"
name="datedFilename"/></New>|      </Arg></New>
java.lang.reflect.InvocationTargetException in
file:/C:/Program%20Files%20(x86)/Shibboleth/Jetty/etc/jetty-logging.xml
Exception in thread "main" java.lang.reflect.InvocationTargetException
                at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
                at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
                at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                at java.lang.reflect.Constructor.newInstance(Unknown Source)
                at
org.eclipse.jetty.util.TypeUtil.construct(TypeUtil.java:549)
                at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.newObj(XmlConfiguration.java:806)
                at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.itemValue(XmlConfiguration.java:1125)
                at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.value(XmlConfiguration.java:1030)
                at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.newObj(XmlConfiguration.java:775)
                at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:423)
                at
org.eclipse.jetty.xml.XmlConfiguration$JettyXmlConfiguration.configure(XmlConfiguration.java:354)
                at
org.eclipse.jetty.xml.XmlConfiguration.configure(XmlConfiguration.java:262)
                at
org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1243)
                at java.security.AccessController.doPrivileged(Native
Method)
                at
org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
Caused by: java.io.IOException: Cannot write log directory C:\Program\
Files\ (x86)\Shibboleth\IdP\jetty-base\logs
                at
org.eclipse.jetty.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:219)
                at
org.eclipse.jetty.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:166)
                at
org.eclipse.jetty.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:120)
                ... 15 more




--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Increasing-memory-for-Jetty-with-exec-in-start-ini-causes-shibb-service-to-fail-on-start-tp7623163.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.