I'm preparing to upgrade my WildFly domain cluster from 10 to 17. I've downloaded and installed WildFly 17.0.1 and just started it in domain mode, but when opening the web management console I'm getting a lot of "500 Server Error" responses for requests to /management (see attachment).
I cannot find any related log on the server. How can I further debug this?
Does this installation have any changes in the configuration files? Does it work if you start it in standalone mode and access the admin console?
Thank you Jaikiran. In fact, the only configuration is management authentication with Elytron backed by an LDAP server. Restoring file-based authentication there are no errors, so it must be something related to this. I guess querying LDAP is too slow and it happens for every query with BASIC authentication. Unfortunately I didn't find another way to configure this!
For something like a 5xx errror, I would have expected some exception/error logs in the server log files. There's nothing related to this in the logs?
Turns out *every* HTTP request on the management console triggers an LDAP request to be authenticated on the server, even images, so there is intense traffic to LDAP. I suspect this is due to BASIC authentication, so question is: can I enable a cookie-based or session-based authentication, backed by LDAP on user login but not on every request?
jaikiran No, there is nothing on the logs. I'm looking at "domain/log/host-controller.log", but other files there as well have nothing.
The elytron subsystem allows caching. My quick googling hasn't found a lot of docs coverage, but this touches on it:
That's in the context of how to migrate a legacy security config to elytron, but hopefully the key bits can be worked out from that.
The WildFly Model Reference shows the configurable attributes for a caching-realm:
Thank you Brian, configuring a caching-realm solved the issue!
Still, anonymous 500 errors should generate clear log messages about what's going on.
The absence of logs is odd. Are you fronting the server with any kind of load balancer and maybe the 5xx status messages are being returned by that load balancer and not WildFly?