Skip to main content
Question

Apps10 MWS timing out during start

  • November 19, 2025
  • 2 replies
  • 18 views

NickPorter
Superhero (Customer)
Forum|alt.badge.img+18

Recently we have found that when starting the Apps10 MWS using the mws-svr command we get timeouts at 10 minutes. 

There doesn’t appear to be a RAM or CPU usage issue at the time of the failure and monitoring the system closely shows no sign of that even coming close to much load on either or large java process RAM usage, but I suppose we cannot rule it out. 

If we keep restarting the Windows services and restarting using mws-svr it typically comes up OK after several attempts.

Questions:

  1. Assuming that the CPU and RAM is fine, is there a way to increase the 10 minute timeout threshold?
  1. Any other ideas?

Here’s what we typically see, sometimes with MAIN not starting, other times it is INT that doesn’t come up, and sometimes both:

---

Starting Domain - IFSTEST...
11/19/25 4:51:33 PM <WARNING> Thread[Thread-15,5,main] did not responded - TIMEOUT
11/19/25 5:01:33 PM <WARNING> Thread[Thread-16,5,main] did not responded - TIMEOUT

 

Domain - IFSTEST - STATUS

 

  AdminServer : RUNNING

 

  Node - FBD-IFSAPP-TEST
    Node Manager (FBD-IFSAPP-TEST) : RUNNING
      main cluster
        MainServer1 : EXCEPTION (Timed out 10min 0sec 0ms)
      integration cluster
        IntServer1 : EXCEPTION (Timed out 10min 0sec 0ms)

 

    System Components
      HttpServer1 : RUNNING

2 replies

dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)
  • November 20, 2025

Hi ​@NickPorter 

 

I’m not sure if the timeout can be increased, or could it be any help since 10 minutes is typically enough to start the servers.

Below are some things you can do to troubleshoot at least where the problem is:

  • Check if there’s enough disk space in the server
  • Open Task Manager and sort the processes by memory. Then run the start command. Check if a java process with rapidly increasing memory appears.
  • Check the admin server logs for any errors
  • Check if there were any network changes happened recently or restore of VMs. Sometimes the admin server could not start the main/int servers if there are network changes even though the host name is unchanged.

Hope it helps!

Damith


NickPorter
Superhero (Customer)
Forum|alt.badge.img+18
  • Author
  • Superhero (Customer)
  • November 20, 2025

@dsj  Thanks for the ideas. I’m pretty sure that the 10 mins timeout has to be defined in one or more of the config files and/or java parameters, but I’m still looking for it.

We’ll double check these items you suggested but I’m pretty sure that the first two are good.  The processes start and we get 2 or 3 java processes start and max out about 1.5G or so, then just sit there while mws-svr doesn’t respond and eventually errors as shown previously.  

We did just migrate these VMs from on-prem to Azure but the error was happening internally before we moved them anyway.

I’ll update here after checking.

 

In the meantime any other ideas are welcome!