Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to make a client connection to queue manager with ACE12 V9 and V10. #537

Open
Arnold0210 opened this issue Oct 14, 2023 · 1 comment

Comments

@Arnold0210
Copy link

Hi!,

I'm building an environment with ACE12 and IBM MQ images on Docker, that allow me to a deploy some solutions, and do unit test.

For this purpose I wrote the following docker compose file:

version: '3.9'
services:
  aceserver: 
    image: arnold9810/ace12v9r1:V0
    container_name: serverace
    ports:
      - 7600:7600
      - 7800:7800
      - 7843:7843
    depends_on:
      - mqdev
    networks:
      - ace-mq-net
    environment:
      LICENSE: accept
      ACE_SERVER_NAME: ACESERVER
    restart: always
  mqdev:
    image: icr.io/ibm-messaging/mq:latest
    container_name: MQDEV
    environment:
      LICENSE: accept
      MQ_QMGR_NAME: MQDEV
      MQ_APP_PASSWORD: passw0rd
      MQ_ADMIN_PASSWORD: passw0rd
      MQSNOAUT: 'Yes'
    ports:
      - 1414:1414
      - 9157:9157
      - 9443:9443
    volumes:
      - mqvolume:/mnt/mqm
    networks:
      - ace-mq-net
volumes:
    mqvolume:
networks:
  ace-mq-net:
   driver: bridge

When I raise up the environment, I deploy a MQ Policy on ACE container with the follow configuration:

<policies>
  <policy policyType="MQEndpoint" policyName="MQ_DEV" policyTemplate="MQEndpoint">
    <connection>CLIENT</connection>
    <destinationQueueManagerName>MQDEV</destinationQueueManagerName>
    <queueManagerHostname>host.docker.internal</queueManagerHostname>
    <listenerPortNumber>1414</listenerPortNumber>
    <channelName>DEV.ADMIN.SVRCONN</channelName>
    <securityIdentity>DSN_MQDEV</securityIdentity>
    <useSSL>false</useSSL>
    <SSLPeerName></SSLPeerName>
    <SSLCipherSpec></SSLCipherSpec>
    <SSLCertificateLabel></SSLCertificateLabel>
    <reconnectOption>default</reconnectOption>
    <CCDTUrl></CCDTUrl>
    <MQApplName></MQApplName>
  </policy>
</policies>

After it, I set de DSN Configuration using the following command on the ace container:

. /opt/ibm/ace-12/server/bin/mqsiprofile
mqsisetdbparms -w /home/aceuser/ace-server/ -n mq::DSN_MQDEV -u admin -p passw0rd

And I modified the server.conf.yaml to update the remotequeuemanager configuration (line 25 of server.conf.yaml)

remoteDefaultQueueManager: '{MQ_POLICY}:MQ_DEV' 

and restart de container where ACE is running, but when the container restarted, the logs show the following:

Failed to make a client connection to queue manager 'MQ DEV' using hostname 'host.docker.internal' on port '1414': MQCC=2; MQRC=2012.

I've been looking in the documentation about the MQRC 2012, but is not clearly about what I will be doing wrong.

Someone did that configuration before?

@arthurbarr
Copy link
Member

Sorry, I'm not sure what to suggest. We've not done any testing with Docker Swarm. Given that MQ return code 2012 relates to an environment error in the client application, I think you might have better luck with contacting the ACE team.

JEFFLUFC added a commit that referenced this issue Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants