Troubleshooting
Problem
One or more AMQ9620E errors are seen in the IBM MQ queue manager error log under load when TLS connections are in use. The first error mentions error code '12', and subsequent occurrences mention error code '9'. Connections to the queue manager fail as a result of this error, although the queue manager might intermittently be able to accept connections, in cases where multiple amqrmppa processes are already running.
Symptom
An error similar to the following is seen in the IBM MQ queue manager error log under load:
26/09/2023 16:30:06 - Process(123.456) User(mqm) Program(amqrmppa)
Host(mqhost) Installation(Installation1)
VRMF(9.2.0.15) QMgr(TEST_QM1)
Time(2023-09-26T15:30:06.456Z)
RemoteHost(10.0.0.22)
ArithInsert1(12)
CommentInsert1(????)
CommentInsert2(gsk_secure_soc_init)
CommentInsert3(hostname(10.0.0.22))
AMQ9620E: Internal error on call to SSL function on channel '????' to host
'hostname (10.0.0.22)'.
EXPLANATION:
An error indicating a software problem was returned from a function which is
used to provide SSL or TLS support. The error code returned was '12'. The
function call was 'gsk_secure_soc_init'.
The channel is '????'; in some cases its name cannot be determined and so is
shown as '????'. The channel did not start.
The remote host name is 'hostname(10.0.0.22)'.
Host(mqhost) Installation(Installation1)
VRMF(9.2.0.15) QMgr(TEST_QM1)
Time(2023-09-26T15:30:06.456Z)
RemoteHost(10.0.0.22)
ArithInsert1(12)
CommentInsert1(????)
CommentInsert2(gsk_secure_soc_init)
CommentInsert3(hostname(10.0.0.22))
AMQ9620E: Internal error on call to SSL function on channel '????' to host
'hostname (10.0.0.22)'.
EXPLANATION:
An error indicating a software problem was returned from a function which is
used to provide SSL or TLS support. The error code returned was '12'. The
function call was 'gsk_secure_soc_init'.
The channel is '????'; in some cases its name cannot be determined and so is
shown as '????'. The channel did not start.
The remote host name is 'hostname(10.0.0.22)'.
This message is followed by multiple recurrences of the same AMQ9620E error message, reporting error code '9' instead of '12'. The subsequent messages identify the same process ID, although the thread ID may be different. The process is 123 in this example message, followed by the thread ID 456: Process(123.456).
An additional error message AMQ9661E reporting error code '411' from 'gsk_secure_soc_read' might also be written to the error log for the same process ID after the initial AMQ9620E message is written to the error log.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"ARM Category":[{"code":"a8m0z00000008OYAAY","label":"Connectivity-\u003EChannels"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"},{"Product":{"code":"SSKM59","label":"IBM MQ for HPE NonStop"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}},{"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
28 April 2025
UID
ibm17039406