MID Server fails to start - WrapperManager Error: Failed to connect to the Wrapper at port 32,000Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } MID Server is not starting, and the following error can be seen in the agent\logs\wrapper.log This example is "Connection timed out: connect": 2021/12/03 07:18:02 | WrapperManager Error: Exiting JVM...2021/12/03 07:18:03 | JVM exited while loading the application.2021/12/03 07:18:09 | Launching a JVM...2021/12/03 07:18:09 | WrapperManager: Initializing...2021/12/03 07:18:10 | Logger for 'glide' has not been configured by the container, configuring now:2021/12/03 07:18:10 | Configuring log handler: java.util.logging.FileHandler2021/12/03 07:18:10 | Setting useParentHandlers=false for Logger 'glide'2021/12/03 07:18:10 | Overriding formatter to: com.glide.util.DefaultLogFormatter (for handler: java.util.logging.FileHandler)2021/12/03 07:18:31 | WrapperManager Error: Failed to connect to the Wrapper at port 32,000. Cause: java.net.ConnectException: Connection timed out: connect2021/12/03 07:18:31 | WrapperManager Error: Exiting JVM...2021/12/03 07:18:31 | JVM exited while loading the application.2021/12/03 07:18:31 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.2021/12/03 07:18:31 | There may be a configuration problem: please check the logs.2021/12/03 07:18:32 | <-- Wrapper Stopped This example is "Connection refused": 2025/09/15 11:03:24 | WrapperManager Debug: Open socket to Wrapper...Wrapper-Connection2025/09/15 11:03:26 | WrapperManager Error: Failed to connect to the Wrapper at port 32,000. Cause: java.net.ConnectException: Connection refused2025/09/15 11:03:26 | WrapperManager Error: Exiting JVM...2025/09/15 11:03:26 | WrapperManager Debug: WrapperManager.stopImmediate(1) called by thread: Wrapper-Connection Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } up to at least Yokohama Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This error tells that the JVM is not able to connect to the Java Service Wrapper. This is probably caused by port conflicts (in the above case, port 32000) if this port is used by other applications, or not open the firewall side, or is blocked by a software firewall on the server. Port in Use If port 32000 is already in use by another process, Tanuki Wrapper should just Warn and find a port that is not in use, as documented here:https://wrapper.tanukisoftware.com/doc/english/prop-port.html To check, from a Command Prompt, running as Administrator, you can work out what other process might be using the same port. e.g. netstat -ano -p tcp | find "32000" tasklist | find "6040" where 32000 is the port shown in the error, and 6040 is a process ID shown by netstat Update Dec 2025: Port in use ought not to be the cause any more. Since at least Yokohama, we see the port is in use, then increment the port number until it works. Each pair of wrapper and java processes need separate ports, but we've had customers running multiple mid servers on the same host for years without this issue. This can be confirmed in wrapper.log by adding wrapper.debug=true in wrapper-override.conf, on a host with a few other MID Servers already running. 2025/12/05 14:49:40 | WrapperManager Debug: Implementation Vendor: Tanuki Software, Ltd.2025/12/05 14:49:40 | WrapperManager Debug: Implementation Version: 3.5.572025/12/05 14:49:42 | WrapperManager Debug: Java Version : 17.0.12-sncmid1+3 OpenJDK 64-Bit Server VM...2025/12/05 14:49:43 | WrapperManager Debug: Open socket to Wrapper...Wrapper-Connection 2025/12/05 14:49:43 | WrapperManager Debug: Unable to open socket to Wrapper from port 31,000, already in use. (5) 2025/12/05 14:49:43 | WrapperManager Debug: Unable to open socket to Wrapper from port 31,001, already in use. (5) 2025/12/05 14:49:43 | WrapperManager Debug: Unable to open socket to Wrapper from port 31,002, already in use. (5) 2025/12/05 14:49:44 | WrapperManager Debug: Opened Socket from 31,003 to 32,001 2025/12/05 14:49:44 | accepted a socket on port 32001 from 127.0.0.1 at port 31003 Firewall This has been seen with Yokohama on Linux. Windows Servers are likely to be running Windows Defender Firewall, which has also been seen to block this (Tokyo release). Add a new rule for IncomingTCPport 32000