Hi,
If you try to launch a JRun server and initialization takes more than 30 secs, the launch fails. Is there any way to increase this 30 second limit?
Thanks, Tony
Hi,
If you try to launch a JRun server and initialization takes more than 30 secs, the launch fails. Is there any way to increase this 30 second limit?
Thanks, Tony
Assuming you are running JRun under Windows, you can tune how long the Windows Service manager will wait. See How to debug Windows services and search that page for "30 seconds". Immediately below that you'll see a registry key you can edit.
Basically, you'll be adding creating a new DWORD key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout
the value of this key will be the number of milliseconds in which services should start. This is a global setting, not just for the JRun service.
Hello,
I'm having the same problem and I think this change will solve it. However, I'm on Windows Server 2008 in a 64bit environment and the two options I have in the registry settings ar:
DWORD (32-bit) Value QWORD (64-bit) Value
Is DWORD the correct one to use in this instance?
Thanks!