IBM MQ Docker（Windows）连接Flume（Cloudera VM）报错求助

Hey there, let's work through your JMSAdmin error step by step—since you're new to IBM MQ, let's start with fixing foundational setup issues first, then tackle common error causes.

First: Fix Your Docker Run Command #

I noticed a couple of gaps in your initial Docker setup that might be causing downstream issues:

• You created the qm1data volume but didn't mount it to the container (so your queue manager data won't persist across restarts)
• You didn't specify a container name, which makes docker exec more error-prone

Use this corrected command to launch your IBM MQ container:

docker run \
  --env LICENSE=accept \
  --env MQ_QMGR_NAME=QM1 \
  --name MyMQContainer \
  --volume qm1data:/mnt/mqm \
  --publish 1414:1414 \
  --publish 9443:9443 \
  --detach \
  ibmcom/mq

This gives your container a predictable name (MyMQContainer) and ties your volume to the container's MQ data directory for persistence.

Step 2: Properly Access JMSAdmin with Correct Permissions #

IBM MQ tools like JMSAdmin require running as the mqm user (the dedicated MQ administrator account in the container). Here's the right sequence to launch it:

1. Log into your container with the correct name:

   docker exec -it MyMQContainer /bin/bash
   

2. Switch to the mqm user (you'll need this for proper access to MQ resources):

   su - mqm
   

3. Navigate to the JMSAdmin directory and launch the tool:

   cd /opt/mqm/java/bin/
   ./JMSAdmin
   

Common JMSAdmin Error Fixes #

If you still hit errors after the above steps, here's how to troubleshoot the most frequent issues:

1. "Permission Denied" or "Command Not Found" #

• Double-check you switched to the mqm user (running as root or another user will restrict access to MQ tools)
• Verify the JMSAdmin script exists by running ls /opt/mqm/java/bin/—if it's missing, your container might have failed to initialize fully. Restart the container and check logs with docker logs MyMQContainer to debug initialization issues.

2. JMSAdmin Fails to Connect to QM1 #

If the tool launches but can't reach your queue manager:

• First confirm QM1 is running: run dspmq as the mqm user. It should show QMNAME(QM1) STATUS(Running).
• If it's not running, start it with strmqm QM1.

3. Prepping for Flume Integration (Critical for Remote Connection) #

Since you need to connect from your Cloudera VM (10.0.2.15) to the Windows-hosted MQ container, you'll need to configure QM1 to accept remote connections:

1. As the mqm user, launch the MQ command shell:

   runmqsc QM1
   

2. Run these commands to create a channel and allow access from your Cloudera VM:

   # Define a server connection channel for Flume
   DEFINE CHANNEL(FLUME.CHL) CHLTYPE(SVRCONN) TRPTYPE(TCP)
   # Allow connections from your Cloudera VM's IP
   SET CHLAUTH(*) TYPE(ADDRESSMAP) ADDRESS('10.0.2.15') USERSRC(CHANNEL) CHCKCLNT(ASQMGR)
   # Refresh security settings to apply changes
   REFRESH SECURITY TYPE(CONNAUTH)
   

3. Exit the shell with END.

Also, note: Your Cloudera VM will need to connect to your Windows host's IP (not the container's internal IP). For VirtualBox NAT mode, this is usually 10.0.2.2—so Flume should target 10.0.2.2:1414 with channel FLUME.CHL.

内容的提问来源于stack exchange，提问作者SirGustave