IBM MQ: Why is my cluster sender channel trying to connect to 1414 when I have clearly specified 1415 (or any other port)?

Posted by on October 15, 2018 Leave a comment (5) Go to comments

Cluster sender channels seems to get “stuck” sometimes and fall back to port 1414 when trying to find the cluster repository.

The solution:
Delete the channel and create it again

DEFINE CHANNEL(TO.REPO) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME('127.0.0.1(1415)') CLUSTER(EXTERNAL.CLIENTS) DESCR('Cluster-sender channel from MYQM01 to repo at MYREPO01')

Tested on MQ 9.0.5.0 and Red Hat Linux 7.5

IBM MQ
  1. Morag Hughson October 18, 2018 at 22:04

    Would altering the channel also work? Have you reported it to IBM in a PMR?

    Reply
  2. JoshMc October 27, 2018 at 10:37

    Next time check to make sure there are no space characters embedded in the conname for example: CONNAME(‘127.0.0.1(1415)’), I found that the port will be ignored in this case.

    Reply

Leave a Comment


NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre lang="" line="" escaped="" cssfile="">

This site uses Akismet to reduce spam. Learn how your comment data is processed.