Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Nov 18, 2019

Control the timeout for connection from MQ to OCSP server

When operating IBM MQ 9 with enabled Online Certificate Status Protocol (OCSP) we encounter situations where MQ is logging errors in case OCSP servers are not reachable e.g. due to network issue.

We want to simulate, understand and be able to control the possible cases regarding OCSP checks in MQ.

Therefore we want to have a feature to control the TCP connection timeout in MQ when it connects to OCSP servers.

Until now in our TCP connection failure simulations we always observe errors in the MQ log after around 4 minutes 20 seconds counting from MQ channel start. We consider it too long. Refer to Support Case TS002969214.

Through the above support case we already received an answer from the IBM Lab that this feature could be possbible. Response from the IBM MQ Lab:

"GSKit does provide interfaces to alter the default behaviour of its OCSP checks for TLS connections,
The default behaviour is not to timeout the HTTP connection request, once connected the default OCSP
request timeout is set to 30 seconds.
IBM MQ does not currently use these interfaces (so defaults apply), adding MQ ini file controls to allow
alteration of these timeouts to a custom value would be a reasonable request for inclusion in a future
MQ version via the RFE process.
The current 4 min 20 second timeout is likely to be due to some lower level TCP/IP mechanism closing
the socket because of the dropped packets."

Thank you.

Idea priority High
RFE ID 138263
RFE Product IBM MQ
  • Guest
    Jan 14, 2020

    We hope to deliver this enhancement in a future MQ update

  • Guest
    Nov 19, 2019

    Addition from customer: the timeout should apply for at least two cases:
    - Connect to OCSP provider
    - OCSP provider not responding in time
    to guarantee a startup time of the channel below 5 seconds including SSL/TLS Handshake in case there is an issue with the OCSP provider or network.