Found the fix.
Noticed that we have already opened bug tickets in ActiveMQ concerning this.
*ISSUE:*
It's not directly related to ActiveMQ, it's due to an upgrade of Jetty
which has some fixes that restrict the symbolic reference usage. (
/opt/app-1 -> /opt/app)
*FIX:*
Referring to actual refe
Hi Team,
I have noticed an issue in the recent upgrade of ActiveMQ from 5.16.1 to
5.16.7 where the ActiveMQ web console fails to start with the below
exception. Other functionality is working fine but can't launch the web
console. No configuration changes were made in this upgrade from my end.
HT
