In the short term, one option would be to simply not include the Jetty JAR in the ActiveMQ classpath. I'd expect you might lose access to the web console and possibly also to the HTTP transport (I'm not sure if that relies on Jetty, but it wouldn't surprise me if it did), but if you could live without those things, it might give you an immediate path forward while JB works out exactly which Jetty JARs should replace jetty-all.
Tim On Fri, Nov 29, 2019, 12:22 AM Naveen Kumar <navee...@gmail.com> wrote: > Hi JB, > > For a test, > I just placed the jetty-all jar in tomcat 9 lib and server start up reports > the same error. > I did not keep activemq or any other jar. > > Thanks > Naveen > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
