Description

• It is observed that Mid Server is down. On further investigation, we observed that error "Timed out waiting for wrapperServiceMain" seen in wrapper log file.
• Mid server host machine was restarted and when the host machine was up, mid service was not started automatically.
• We manually tried starting the service, but that does not help and resulted in Microsoft error - 1053 

Release or Environment

• All Releases

Cause

• We continued to troubleshoot and below is the log snippet found in the wrapper log,

Child process: Java version: timed out
2021/02/04 18:44:18 | Failed to resolve the version of Java.
2021/02/04 18:44:18 | <-- Wrapper Stopped
2021/02/04 18:44:28 | Timed out waiting for wrapperServiceMain
2021/02/04 18:49:05 | --> Wrapper Started as Service
2021/02/04 18:49:05 | Java Service Wrapper Standard Edition 64-bit 3.5.40
2021/02/04 18:49:05 | Copyright (C) 1999-2019 Tanuki Software, Ltd. All Rights Reserved.
2021/02/04 18:49:05 | http://wrapper.tanukisoftware.com
2021/02/04 18:49:05 | Licensed to ServiceNow, Inc. for MID

• The potential root cause of this issue could be:
  
  • The WrapperManager not getting launched, because of the jvm getting timed out. 
  • Startup method taking time to complete/execute.

Resolution

• In this current use case, the below properties are added to the wrapper.conf file located at Midserver\agent folder.
  

  wrapper.startup.timeout=300
  wrapper.jvm_exit.timeout=300

• Another property "wrapper.ping.timeout=300" already exists in wrapper.conf file and the default value is 300 seconds. 
• The above property defines the number of seconds to allow between the time that the Wrapper launches the JVM process and the time that the JVM side of the Wrapper responds that the application has started. Setting this property value to "0" (zero) means never times out. 
• After following steps, Mid server was started successfully and the issue got resolved.