EAR file deployment keeps failing for staging server only.

119 views
Skip to first unread message

Wendell Hatcher

unread,
Sep 20, 2023, 11:20:02 AM9/20/23
to wil...@googlegroups.com
I have an issue where a single ear file keeps failing to deploy for a single cluster on our staging environment.   I see the following error and have updating the timeout settings to over 5 minutes is there anything else I can do?


2023-09-20 11:15:50,585 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 108) WFLYCTL0349: Timeout after [5] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'deploy' at address '[("deployment" => "System2.ear")]'



-Wendell 

Wendell Hatcher

unread,
Sep 20, 2023, 11:22:44 AM9/20/23
to wil...@googlegroups.com
Here are the deployment errors as well.

domain@jas01:9443 /] deploy --name=System2.ear --server-groups=g-cluster
{"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"g-cluster" => {"host" => {"jas01" => {"g_server01" => "WFLYCTL0409: Execution of operation 'composite' on remote process at address '[
    (\"host\" => \"jas01\"),
    (\"server\" => \"g_server01\")
]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation"},"rhgmscstagejas02" => {"g_server02" => "WFLYCTL0409: Execution of operation 'composite' on remote process at address '[
    (\"host\" => \"jas02\"),
    (\"server\" => \"g_server02\")
]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation"}}}}}}
Reply all
Reply to author
Forward
0 new messages