OK @Brad Wood, Thanks for your input.

Oh, almost forgot about the java agent error. That is a totally unrelated 3rd issue. Check and see if you are testing on a recent release of java such as OpenJDK8 update 242. I've been seeing a lot of users getting that error on that version of Java and it appears to be a recent regression in Java itself. You need to roll back your Java version so that error goes away.

@Pothys - MitrahSoft Right, so I don't think you understand this ticket. The CommandBox setup for your test was fine, but the code you're testing is for the wrong ticket! Like I pointed out above in ticket LDEV-2558, extension management is broken, so trying to USE extension management or test this ticket will be the blind leading the blind. Like I said above, you must actually run CFML code that uses an extension. But even given that, this issue is intermittent (affecting a small number of users) so even if you were to construct a .cfm file that used every single extension and it succeeded, you'd not be proving the ticket valid or invalid, you'd simply be showing yourself lucky enough to be in the group of people for which the issue doesn't exist. Sadly, I don't know how to reproduce this on-demand. The only common thread I'm aware of between the users who have reported it were that they were using locked-down government servers that I wasn't allowed to access for troubleshooting purposes.

So, to review, there are two unrelated issues going on here in 2 separate tickets:

• Lucee doesn't always report extensions as being installed even though they actually are (this is ticket https://luceeserver.atlassian.net/browse/LDEV-2558#icft=LDEV-2558)

• Lucee sometimes actually doesn't load extensions (like PDF or compress), there does not appear to be any errors in the logs or indications that anything has gone wrong. Code such as CFDocument or cfzip simply fails to compile. (This ticket is for this bullet point)

Using any of the facilities reported as non-working in the first bullet point to try and test the issue in the second bullet point will render the test invalid.

@Brad Wood,
First, I'm not familiar with Command box CLI but, I tried with the following way.
I can explain how I did that. Initially, I've one test.cfm in my local and run it via Command box.
In the CLI, I've used this command to run the file

I tested with cfadmin-getRHExtensions method in the cfm.
Then, I can see the count of extensions in the first time. Seems the extensions count is low. And if I test with another method means, it throws an error. Like
Lucee was not able to load a Agent dynamically! You need to load one manually by adding the following to your JVM arguments [-javaagent:"C:\Users\SQORI-016\.CommandBox\engine\cfml\cli\lucee-server\context\lucee-external-agent.jar"]
Anything I missed with that or any other way to test this ticket, If yes, Please let me know here.

@Pothys - MitrahSoft Please note that in regard to this ticket, just because the extensions don't show as loaded, doesn't mean they aren't actually loaded. For example, I can run a cfdocument tag from the CLI and it works just fine even though I show as having zero extensions installed. Obviously the PDF extension is installed however. That is why this ticket is labeled as extension management not working, not that extensions don't install. The reason I brought this up on the other ticket is BECAUSE of the complications detailed on this ticket, it is very difficult to test wither an extension is installed unless you actually try to run code that you know uses that extension. Which goes back to me asking you how you tested whether the extensions were installed.