Description
Code to reproduce onebeyond/rascal#156
Steps:
- update
adhoc/rmq-publisher.js
to provide password of RMQ user - run
npm install
- run
DEBUG=rascal:* node adhoc/rmq-publisher.js
- restart AMQ cluster (see howto section below)
- wait for the cluster to get restarted indicated by
Handling connection error: Connection closed: 320 (CONNECTION-FORCED) with message "CONNECTION_FORCED - broker forced connection closure with reason 'shutdown'" initially from connection: 2e494af6-b83c-4253-8f2c-3ba62aab109d, amqps://rascal:***@b-f6fe758b-07f7-4afa-b0ae-302212d604c3.mq.us-west-2.amazonaws.com:5671?heartbeat=10&connection_timeout=10000&channelMax=100 +7s
RabbitBroker (rascal) - error Error: Connection closed: 320 (CONNECTION-FORCED) with message "CONNECTION_FORCED - broker forced connection closure with reason 'shutdown'
(tested with Node.js v14.16.0)
HOWTO restart Amazon MQ cluster
You need to have AWS CLI v2: https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html
-
configure new AWS profile by executing
aws configure --profile rascal-test
-
enter
AKIARBZZQR2HDJWZZZIB
as access key -
enter access secret (for AWS CLI)
-
enter
us-west-2
as region -
leave
Default output format
empty -
use new AWS profile to restart AMQ cluster:
aws --profile rascal-test mq reboot-broker --broker-id b-f6fe758b-07f7-4afa-b0ae-302212d604c3
-
it takes a few minutes (~5mins) for cluster to fully restart