Some lucee admin JS URLs failing

I have a new install of CommandBox on Ubuntu using AJP to serve files through Apache. When I load up the Lucee admin in the web browser, 4 of the scripts and one image served by .cfm extensions fail to load with an HTTP Status Code of 503. This causes that overview page to not load the metrics at all. I can browse around the admin, but some functions will also return similar errors (e.g. trying to add a datasource). If I use a text-based browser on the server to get to the lucee admin directly on 127.0.0.1:8080, I can browse and successfully add datasources, etc. This also affects other cfm scripts in similar ways.

Can someone help point me in the right direction for a resolution?

Snippet from the CommandBox log (with DEBUG and TRACE enabled):

[TRACE] io.undertow.request: Created GZIP response conduit for HttpServerExchange{ GET /lucee/res/js/base.min.js.cfm}
[TRACE] io.undertow.server.HttpServerExchange: Starting to write response for HttpServerExchange{ GET /lucee/res/js/base.min.js.cfm}
[DEBUG] runwar.context: The response channel was closed prematurely.  Request path: /lucee/res/js/base.min.js.cfm status-code: 200
[DEBUG] io.undertow.request.io: UT005013: An IOException occurred
java.nio.channels.ClosedChannelException: null
        at io.undertow.conduits.DeflatingStreamSinkConduit.write(DeflatingStreamSinkConduit.java:116) ~[runwar-4.7.16.jar:4.7.16]
        at org.xnio.conduits.Conduits.writeFinalBasic(Conduits.java:132) ~[runwar-4.7.16.jar:4.7.16]
        at io.undertow.conduits.DeflatingStreamSinkConduit.writeFinal(DeflatingStreamSinkConduit.java:174) ~[runwar-4.7.16.jar:4.7.16]
        at org.xnio.conduits.ConduitStreamSinkChannel.writeFinal(ConduitStreamSinkChannel.java:104) ~[runwar-4.7.16.jar:4.7.16]
        at io.undertow.channels.DetachableStreamSinkChannel.writeFinal(DetachableStreamSinkChannel.java:195) ~[runwar-4.7.16.jar:4.7.16]

Apache error log:

[Mon Jan 23 08:32:54.401881 2023] [proxy_ajp:error] [pid 1440666:tid 139845754992384] [client X.X.X.X:58246] AH00992: ajp_read_header: ajp_ilink_receive failed, referer: https://mydomain.com/lucee/admin/server.cfm?action=overview
[Mon Jan 23 08:32:54.401890 2023] [proxy_ajp:error] [pid 1440666:tid 139845754992384] (120007)APR does not understand this error code: [client X.X.X.X:58246] AH00893: dialog to (null) (*) failed, referer: https://mydomain.com/lucee/admin/server.cfm?action=overview

Not sure. CommandBox says the client (Apache) closed the response channel (disconnected) early. But Apache says… we’ll I’m not really sure what that Apache error message even means, lol. I would do some Googling on the Apache error and see what causes it. I’ve used Apache to proxy over AJP to CommandBox and I’ve never run into this before.

Thanks @bdw429s . Any chance this could be related to undertow? Or do I need to go hunting down the Apache path? Googling hasn’t turn up much so far, and anything it does usually mentions Tomcat.

Sure, that’s possible. Apache is the one who seems to be having the issue, so I’d start seeing if you can get any more logging out of Apache to get more details on the issue.

I have exactly the same problem with Apache AJP + Commandbox with a ContentBox website and so far, I can’t solve the issue despite several days of Googling and searching.

In my case, the issue seems to only happened when contentBox serves images (which are redirected to /index.cfm/__media/path/to/image/jpg). The other files seems to work fine.

If I use the HTTP connector, then , there is no issue, so the problem seems to come from AJP, and more specifically from the connection between Apache and the backend.
Also, When I install Lucee using the lucee installer (which comes bundeled with Tomcat), then I do not see this issue, which seems to indicate that it is related to commandbox / undertow.

@technomaz Did you solve your problem? Did you find any additional clue?

Any help appreciated… Thanks…