Trying to connect to onprem MQ using IBM MQ Connector.

[adithyaseelam24]

Trying to connect to onprem MQ using IBM MQ Connector.
Using destination type as Host address and updated it with the MQ hostname.

Getting below error.
JMSWMQ0018: Failed to connect to queue manager 'Hostname' with connection mode 'Client' and host name 'Client'. 

[robertcarlos]

Hi @adithyaseelam24,

Welcome to Google Cloud Community!

You may check the following setup first before configuring the connector:

• In your Google Cloud project:
  • Grant the roles/connectors.admin IAM role to the user configuring the connector.
  • Grant the following IAM roles to the service account that you want to use for the connector:
    • roles/secretmanager.viewer
    • roles/secretmanager.secretAccessor

    A service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. For more information, see Creating a service account.

  • Enable the following services:
    • secretmanager.googleapis.com (Secret Manager API)
    • connectors.googleapis.com (Connectors API)

    To understand how to enable services, see Enabling services.

  If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.

You may also check the following documentations for your reference:

• Configure IBM MQ 
• Get an IBM MQ queue for development running on Google Cloud 
• JMSWMQ0018 due to RC=2397 AMQ9771 SSL handshake failed for channel connecting from WebSphere Applica... 

If the aforementioned steps didn't work, you may file a bug so that our engineers could take a look at this. We don't have a specific ETA on this one but you can keep track of its progress once the ticket has been created.

Hope this helps.

[arunraj250020]

Hi,

Has this issue been resolved ? I am still facing it  . Your help is much appreciated

Thanks

[AlexET]

Hi @arunraj250020, welcome to the community! Thanks for your question.

To get the most focused help, could you please open a new thread with the details of your specific situation? Feel free to reference this thread if it's helpful. This will allow the community to give you more tailored attention.

You might also find this guide useful: Tips to Ask Questions in the Integration Services Forum

We look forward to seeing your question in a new thread!

[ananymisra]

Hi @arunraj250020 , if you are getting the same error, you can try these troubleshooting steps and share your observations with us: 

The error message JMSWMQ0018: Failed to connect to queue manager 'Hostname' with connection mode 'Client' and host name 'Client' indicates that your application is experiencing trouble connecting to your IBM MQ queue manager. The 'Hostname' placeholder in the message should represent the actual name or IP address of your MQ server. Seeing 'Client' repeated there often suggests a problem resolving the server's address.

Detailed Error Log: Please examine your application's logs for any detailed error messages or stack traces. These can provide valuable context regarding the connection failure.

IBM MQ Server Error Logs: If you have access to the IBM MQ server, please check the queue manager error logs (typically AMQERR01.LOG, AMQERR02.LOG, etc.). These logs often contain information about connection attempts and any errors encountered by the MQ server.

Use MQ Explorer (if available): If you have access to MQ Explorer, please attempt to establish a client connection to the queue manager using the same connection parameters as your application. This can help determine if the problem lies within your application's specific configuration or is a more general connectivity issue.

Simplify the Connection: If feasible, try connecting to the MQ server from a different client machine or using a simple MQ client utility (such as amqsputc and amqsgetc if the MQ client is installed). This can help rule out any application-specific problems.

Temporarily Disable Firewalls: As a temporary troubleshooting step (if possible and safe within your environment), try disabling firewalls on both the client machine and the MQ server. If this resolves the connection issue, it indicates that firewall rules need to be configured appropriately.