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:
- Assuming that the CPU and RAM is fine, is there a way to increase the 10 minute timeout threshold?
- 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