Error when viewing queues in AWS MQ (activemq) console

0

I'm getting an error when viewing any queue in my AWS MQ ActiveMQ broker: "Exception occurred while processing this request, check the log for more information!"

When I check the logs, I see a couple errors [1].

I then found the troubleshooting step related to this error. The recommended fix was to give the activemq-webconsole group read/write/admin rights on all topics and queues. This made no difference. I also tried making the user I was logging into the console with a member of that group, and that had no effect.

Does anyone know what is needed to be able to view queues in the console of an AWS MQ ActiveMQ broker?

[1]

WARN | Security Error occurred on connection to: vm://localhost#4, User amazonmq-system-13e98d69-51c6-4474-ae0a-54deefb2b1bc is not authorized to read from: queue://new-space | org.apache.activemq.broker.TransportConnection.Service | ActiveMQ VMTransport: vm://localhost#5-2

WARN | /admin/browse.jsp | org.eclipse.jetty.server.HttpChannel | qtp672313607-85 javax.servlet.ServletException: javax.servlet.ServletException: org.apache.jasper.JasperException: An exception occurred processing [/browse.jsp] at line [48] 45: </tr> 46: </thead> 47: <tbody> 48: <jms:forEachMessage queueBrowser="${requestContext.queueBrowser.browser}" var="row"> 49: <tr> 50: <td><a href="<c:url value="message.jsp"> 51: <c:param name="id" value="${row.JMSMessageID}" /> Stacktrace: at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.Server.handle(Server.java:500)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:543)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:398)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at java.lang.Thread.run(Thread.java:750)[:1.8.0_322] 2022-02-25 21:40:14,966 | WARN | /admin/browse.jsp | org.eclipse.jetty.server.HttpChannel | qtp672313607-85 javax.servlet.ServletException: javax.servlet.ServletException: org.apache.jasper.JasperException: An exception occurred processing [/browse.jsp] at line [48] 45: </tr> 46: </thead> 47: <tbody> 48: <jms:forEachMessage queueBrowser="${requestContext.queueBrowser.browser}" var="row"> 49: <tr> 50: <td><a href="<c:url value="message.jsp"> 51: <c:param name="id" value="${row.JMSMessageID}" /> Stacktrace: at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.Server.handle(Server.java:500)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:543)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:398)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)[jetty-all-9.4.28.v20200408-uber.jar:9.4.28.v20200408] at java.lang.Thread.run(Thread.java:750)[:1.8.0_322]

jared
asked 2 years ago941 views
2 Answers
1

Hello,

Tim here on the Support Team.

I was looking at your notes and you did the right thing finding our documentation and giving that a try.

I came across the official Apache bug reporting channel: https://issues.apache.org/jira/browse/AMQ-6224

It looks like others have ran into this before. I think there is a bit of variability as to the exact cause, so I’m not confident your issue aligns exactly with what is occurring on that link.

Could you make a technical support case with us at AWS? You can follow this link and submit a technical support case: https://aws.amazon.com/contact-us/

It may take a bit of gathering of logs on the broker and a few additional items that are easier to work through on a support case. When you open the support case be sure to include the:

  • Account
  • Broker ARN
  • The logs you shared here
  • You can share a link to this forum post on the case submission as well
  • The VPC the broker is in
  • If this worked before or is the first time you’re encountering it

Thanks and do let me know if you have questions in the meantime.

AWS
SUPPORT ENGINEER
Tim_P
answered 2 years ago
  • Thanks, Tim. I created a support case and will follow up if we're able to resolve the issues. Hopefully others will be able to benefit from the potential solution.

0
Accepted Answer

I found the issue. I had misspelled the web console group in the activemq configuration file. I was using activmemq.webconsole but the correct spelling is activemq-webconsole. It looks like the incorrect spelling came from the documentation I shared in my original post, so I submitted a pull request to fix it: https://github.com/awsdocs/amazon-mq-developer-guide/pull/20

jared
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions