Image Support #3285

Running IBM multi-instance queue managers on Azure marketplace 7.5.0.8 websphere image

Added by Robert about 1 month ago. Updated 4 days ago.

Status:ClosedDue date:
Priority:High% Done:

0%

Assignee:Robert
Category:-
Image:WebSphere MQ 7.5 Your Marketplace Account ID:0000-0000-0000
Operating System:RHEL 7.5 Marketplace:Microsoft Azure
JRE:Not Applicable Customer State:London
Instance Type:Not Applicable Customer Country:United Kingdom

Description

Hi,

We are trying to run a simple multi-instance queue manager with the following setup:

1. Two MQ servers running the WebSphere MQ 7.5.0.8 RedHat image.
2. The MQ data and logs folders stored on an Azure File Share and mounted via CIFS on both MQ servers. The mqm user/group has full permissions and the same uid/gid on both servers.

Even though the queue setup on both nodes seems to work without error, when we try and start the standby instance using the strmqm -x command, the currently active node fails with an "Ended unexpectedly" error, and the standby node takes over as the active node. For some reason both nodes just refuse to run the queue at the same time.

I have tested the file share using amqmfsck command, which passed without errors, so I am not sure what could be the issue here. The mount point we are using is:

//mqfileshare.file.core.windows.net/mqshare /mnt/mqshare cifs vers=3.0,credentials=/etc/smbcredentials/.seasacp01tas01imq.cred,uid=mqm,gid=mqm,dir_mode=0775,file_mode=0775,nobrl

I have included some screenshots of the behaviour we are seeing. Is this a known incompatibility with Azure File Shares and IBM MQ running on RedHat, or could it be something else?

Any help you could provide would be much appreciated.

Thanks,

Robert

IBM-MQ-MultiInstance-Failure-1.png (78.6 KB) Robert, 03/20/2019 10:13 am

IBM-MQ-MultiInstance-Failure-2.png (48.2 KB) Robert, 03/20/2019 10:13 am

IBM-MQ-MultiInstance-Failure-3.png (58.8 KB) Robert, 03/20/2019 10:13 am

IBM-MQ-MultiInstance-Failure-4.png (31.7 KB) Robert, 03/20/2019 10:13 am

History

#1 Updated by Mariusz about 1 month ago

  • Assignee set to Mariano

#2 Updated by Mariusz about 1 month ago

  • Status changed from New to Feedback
  • Assignee changed from Mariano to Robert

Hi Robert,
Thank you for using our IBM MQ images on Azure.
In your case, because this is not a standard scenario (Azure File Share as shared filesystem) the best option would be to raise a PMR with IBM. Unfortunately, according to this document: https://www-01.ibm.com/support/docview.wss?uid=swg21996472#EOS1 version 7.5.0.8 is not supported by IBM any longer so it is not possible.

We still provide this version on Azure and AWS marketplace, but we will not be able to create a support request for that.
Take a look at our FAQ page: https://www.midvisioncloud.com/questions/ :
What if IBM discontinues support for a product version?

In this situation, MidVision Cloud will continue to provide level 1 and level 2 support until our discontinuation of the product or the cancellation of your subscription, whichever is later. 

However, please be aware that we may no longer be able to raise a PMR or obtain a fix from IBM for these products.

Is it possible for you to test the same scenario on one of the supported versions?
The newest version we provide is: 9.1
https://azuremarketplace.microsoft.com/en-us/marketplace/apps/midvision.websphere-mq-91?tab=Overview
But we also published versions 9.0 and 8.0

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/midvision.websphere-mq-90?tab=Overview
https://azuremarketplace.microsoft.com/en-us/marketplace/apps/midvision.websphere-mq?tab=Overview

Even if you have to use 7.5 (because of different reasons)- I think it will be very helpful if we test the same scenario on a newer version, confirm compatibility and get support from IBM and then try the same on 7.5.

Regards,
Mariusz Chwalek

#3 Updated by Rafael 10 days ago

  • Status changed from Feedback to Marked for Closure

Hi Robert,

We noticed there hasn't been an update to this ticket for some time. Can we consider this ticket closed from support point of view? Is this still an issue or is there anything further that we can do for you in this regard? If not we will be timing out this ticket and will be closed in a few days time. If you have any other queries, please do not hesitate to ask us.

Best regards,

Rafa

#4 Updated by Rafael 4 days ago

  • Status changed from Marked for Closure to Closed

Also available in: Atom PDF