JVM startup parameters in start.ini for Program Files (x86)

[Steven Teixeira]

Thanks all.

I had been following instructions at https://wiki.shibboleth.net/confluence/display/IDP30/Jetty93 which pointed me to the start.ini file.  It seemed like it did work when I was able to use the symlink(status page reported the new maximum memory value).  If start.ini isn't appropriate, I'll abandon that.  The documentation at https://wiki.shibboleth.net/confluence/display/IDP30/Jetty93 may need to be changed.

Since shibd_idpw is more appropriate and I know the registry settings, I'll just change those and update my "between versions" testing checklist to make sure it doesn't change between versions.  For anyone who might be interested, here's the current v3.2.1 path in the registry in a PowerShell command to change the value:

PS C:\Windows\system32> Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\shibd_idp\Parameters\Java' -Name JvmMx -Value 2048

Installing the IdP package itself is the only manual step in our deployment.  I'll definitely be testing headless installs once v3.3 is released.

Thanks again for the replies.

Steven Teixeira

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Rod Widdowson
Sent: Monday, October 31, 2016 1:10 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: JVM startup parameters in start.ini for Program Files (x86)

> 
> . Or wait until Rod's online and can answer. Or it's documented in the wiki already. But I'm fairly sure it isn't done with a file.

Which I'm not right now.  More tomorrow, but briefly.

- start.ini is not appropriate for configuring jetty (a.k.a doesn't work) when it's started by procrun (which is what the shibboleth idp package does).  

- Shibd_idpw is the way to go.

- until 3.3, headless installs do not work, I believe there is a note in the wiki about that, but basically in 3.3 the way to make them work is to not poke the hole in the firewall (because of a bug deep down in MISEXEC.EXE).

- you can probably poke the registry (it's somewhere under a wow64 key below HKLM, possible SOFTWARE\WOW64\Apache2.0\procrun2.0\java).  I'll check tomorrow when I'm back at my desk. However that location isn't one we control and so it may vary between releases.   I've not seen it change in 10 years, but it's important to understand that things may suddenly.

- there may be a way of providing a command line option to the idp installer to provide the max memory when doing a headless install, but again until such time as we document it, it will be non trustworthy 

More tomorrow..

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net