[
https://issues.jboss.org/browse/WFLY-12061?page=com.atlassian.jira.plugin...
]
Brian Stansberry resolved WFLY-12061.
-------------------------------------
Resolution: Rejected
This is expected behavior. WildFly does not accept requests until it has started.
Accepting such requests in earlier releases was a bug, as the requests would be routed to
partially deployed services and get random results.
If your application counts on making an external invocation during deployment and
won't complete deployment until it successfully does, then boot will not complete and
will eventually time out.
The solution to this is to either separate the client and the server apps, or not have the
client block completion of deployment waiting for completion of the call to the server;
e.g. make the call on first request.
A HTTP request on startup from one ear to another crashes Wildfly
after restart.
--------------------------------------------------------------------------------
Key: WFLY-12061
URL:
https://issues.jboss.org/browse/WFLY-12061
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 11.0.0.Final
Environment: Tested on Windows 10
Reporter: Mathias Veje
Assignee: Richard Opalka
Priority: Major
Attachments: SimpleRestService.zip
I have two ear files, a simple server and a simple client. The client ear depends on the
server ear. The Client ear sends a Http request to the server in its Postconstruct. If
both ear files have been deployed and you restart Wildfly it will fail with:
2019-05-01 11:18:25,168 ERROR [org.jboss.as.controller.management-operation] (Controller
Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container
stability. Operation will roll back. Step that first updated the service container was
'add' at address '[
("core-service" => "management"),
("management-interface" => "http-interface")
]'
This error does not occur on Wildfly 10 but does on 11 and 16. I have not tested the 12
through 15. I have included a Gradle project with the 2 ear files.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)