By using AWS re:Post, you agree to the Terms of Use
/Amazon MQ/

Questions tagged with Amazon MQ

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Error when viewing queues in AWS MQ (activemq) console

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](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/troubleshooting-activemq.html#issues-jsp-exception). 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]
2
answers
0
votes
42
views
asked 4 months ago

SAM deployment of lambda (EventSource MQTT) fails with invalid parameter VIRTUAL_HOST

I am struggeling with an issue which appeared out of a sudden between two deployments of our application. What we are doing is. There is a lambda function which has an EventSource configured. In this case it is a MessageQueue (MQ) Event, listening to a AmazonMQ RabbitMQ Broker. It worked fine for many months but with todays deployment it failed. Last working deployment: 2022-02-02 11:06:16 UTC+0100 Error: ``` Resource handler returned message: "Invalid request provided: Invalid parameters: VIRTUAL_HOST (Service: Lambda, Status Code: 400, Request ID:, Extended Request ID: null)" (RequestToken: , HandlerErrorCode: InvalidRequest) ``` Template excerpt: ``` ConsumerFunction: Type: 'AWS::Serverless::Function' Properties: CodeUri: . Events: MQEvent: Type: MQ Properties: BatchSize: 120 Enabled: true Broker: 'arn:aws:mq:us-east-1:11111:broker:cwv-broker:11111' Queues: - 'consumer-queue-name' SourceAccessConfigurations: - Type: BASIC_AUTH URI: 'arn:aws:secretsmanager:us-east-1:1111:secret:global-secrets/rabbitmq-broker-credentials' - Type: VIRTUAL_HOST URI: '/consumervhost' FunctionName: 'consumer-v1-prod' Handler: handler/consumer.php Layers: - !Sub 'arn:aws:lambda:${AWS::Region}:209497400698:layer:php-80:16' - !Sub 'arn:aws:lambda:${AWS::Region}:403367587399:layer:redis-php-80:11' MemorySize: 250 Policies: - AWSSecretsManagerGetSecretValuePolicy: SecretArn: 'arn:aws:secretsmanager:us-east-1:11111:secret:global-secrets/rabbitmq-broker-credentials' - VPCAccessPolicy: {} - !Ref CwvMqAccessPolicy ReservedConcurrentExecutions: 5 Runtime: provided.al2 Timeout: 900 VpcConfig: SecurityGroupIds: - !ImportValue MainVPC-DefaultSecurityGroup SubnetIds: - !ImportValue MainVPC-SubnetPrivateA - !ImportValue MainVPC-SubnetPrivateB Parameters: RetentionDays: 1 ``` Sam version: SAM CLI, version 1.37.0 Deployment script: ``` sam package \ --output-template-file /tmp/deploy-stack.yaml \ --s3-bucket "deployment-resources" \ --profile "$AWS_PROFILE" sam deploy \ --template-file /tmp/deploy-stack.yaml \ --s3-bucket "deployment-resources" \ --capabilities CAPABILITY_IAM \ --stack-name "consumer-prod-v1" \ --profile "$AWS_PROFILE" ``` Help is much appreciated.
0
answers
0
votes
3
views
asked 5 months ago
  • 1
  • 90 / page