- Newest
- Most votes
- Most comments
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.
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
Relevant content
- asked 3 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 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.