Posted: Wed Nov 11, 2009 3:45 pm Post subject: connectivity problems: MQRC_Q_MGR_NAME_ERROR/MQRC_SSL_INITIA
Novice
Joined: 27 Aug 2009 Posts: 16
I built a simple tool to troubleshoot MQ client connectivity. It was happily connecting where it should but today (or horror!) it doesn't work any more. I rebuilt it, reinstalled client tools and reconfigured SSL but nothing seems to work.
Two questions:
1. Trying to connect to a queue manager with the following env vars:
It seems that during MQCONN the system cannot read settings from AMQCLCHL.TAB. Before this used to work fine. Is there something wrong with my env vars?
2. If I add MQSERVER valiable (by finding connection info form AMQCLCHL.TAB) my client tries to connect but exits with MQRC_SSL_INITIALIZATION_ERROR 2393
Looking at network data captured by wireshark I see there is an MQ packet with status data SSL_REMOTE_BAD_CIPHER. I double checked my personal certificate and even reinstalled it but I still get this error. The personal cert was issued by a CA and was imported as a PKCS12 file type. What could be causing this problem?
The amqscnxc sample program shipped with MQ does a fine job of testing client connectivity.
MQSERVER does not allow for SSL. Ever. At all.
If you got a 2058 on our MQCONN call when using channel tables you are specifying a QM name when your channel table entries all have blanks for the QM name parm on the CLNTCONN channels. Or you are specifying a QM name that does not match the QM to which you are getting connected to. _________________ Peter Potkay
Keep Calm and MQ On
The amqscnxc sample program shipped with MQ does a fine job of testing client connectivity.
MQSERVER does not allow for SSL. Ever. At all.
If you got a 2058 on our MQCONN call when using channel tables you are specifying a QM name when your channel table entries all have blanks for the QM name parm on the CLNTCONN channels. Or you are specifying a QM name that does not match the QM to which you are getting connected to.
Remember also the way to use a channel table is with
*dummy as qmgr in the connection parm for the channel having qmgr name dummy. If you omit the leading star the qmgr's name would have to be dummy.
There was something about MQCHLTAB and MQCHLLIB variables that MQ client didn't like. They were pointing to the default location channel definition file location:
Code:
MQCHLTAB=AMQCLCHL.TAB
MQCHLLIB=/var/mqm
When I unset them the client gets through and seems to be able to read /var/mqm/AMQCLCHL.TAB
I now get a repository key error instead but that's a different story.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum