Closed abudavis closed 2 years ago
Firstly, this is a cph issue and should have been raised against the cph repo (https://github.com/ot4i/perf-harness/issues).
For TLS/SSL cph requires a CCDT. This is indicated in your /var/mqm/errors/AMQERR01.LOG: 02/22/22 15:12:58 - Process(27737.1) User(mqm) Program(cph) Host(ip-172-31-42-9) Installation(Installation1) VRMF(9.2.0.4) Time(2022-02-22T15:12:58.864Z) ArithInsert1(1013) CommentInsert1(/var/mqm/AMQCLCHL.TAB)
AMQ9518E: File '/var/mqm/AMQCLCHL.TAB' not found.
EXPLANATION: The program requires that the file '/var/mqm/AMQCLCHL.TAB' is present and available. ACTION: This error may be caused by the program specifying an incorrect file location programmatically via MQCNO value through CCDTUrlPtr or CCDTUrlOffset. If the program has not specified the file location, the environment variables MQCHLLIB, MQCHLTAB or MQCCDTURL may have been specified. If none of these environment variables are set, the location of the file may have been specified in the mqclient.ini through ChannelDefinitionDirectory and ChannelDefinitionFile attributes under the Channels stanza. If the location was not configured programmatically, by environment variable or by mqclient.ini values then '/var/mqm/AMQCLCHL.TAB' represents a default location and filename for this installation. Ensure that file location is correctly configured and that the file is available to the program.
This either needs to be copied from the QMGR to the client, or recreated on the client using runmqsc. If you were using this repo (cphtestp) - this would have been created for you.
We are doing a test to check the MQ performance of a QMGR (MQ1) (the MQ Server) on version 9.2.0.2 running on a VM running Ubuntu OS using C Perfharness which is installed on a VM running CentOS with MQ Client 9.2.0.4 (the client) and we get the following error when trying to connect using SSL, the kdb is setup correctly on the client and MQ server. When the same test is done using MQ sample program "amqssslc" the connection succeeds making us think the issue is with the Perfharness we run.
Please see the MQ trace files attached taken during the test on both client and MQ server. Kindly go through them and let us know where the issue could be.
---- The below test worked ---
-- mqclient.ini config on the client side --
---- MQ channel ---
Attachments:
runmqras_MQclient.zip
runmqras_MQserver.zip