| Author |
Message
|
| zpat |
 Posted: Thu May 27, 2021 4:13 am Post subject: MQ Explorer v9 - how to stop it using CRL servers? |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Windows 10, MQ Explorer 9.2.0.1 connecting to QM v9.0 on z/OS
For some reason this fails using a TLS 1.2 channel to one particular QM and the only error I can find suggested our firewalls may be blocking access to a CRL host.
With the normal MQ client, I have disabled OCSP to avoid this issue by editing MQclient.ini
How can I do the same with MQ explorer (which uses the dreaded JRE java environment)?
I want to stop MQE trying to connect to any CRL/OCSP servers as the failure to do so is preventing me connecting to the QM over TLS 1.2
Is there an option for MQexplorer.ini to achieve this?
How does one stop a JVM based MQ application from using CRL lookup?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu May 27, 2021 11:44 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Not sure if THIS is any help to you?
Or:
| Code: |
| -Dcom.sun.net.ssl.checkRevocation=false |
Added to the start command?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu May 27, 2021 1:10 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I will try that - thanks. Does that also apply to the IBM JRE?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu May 27, 2021 1:19 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
No idea to be honest. Only other thing I can suggest is to open a PMR.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu May 27, 2021 9:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Find the MQExplorer.ini and edit the vmargs section
add -Dcom.sun.net.ssl.checkRevocation=false
Restart MQExplorer and let us know how that worked... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Thu May 27, 2021 11:40 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Tried that and also
-Dcom.ibm.jsse2.checkRevocation=false
Didn't seem to work or maybe this is not the problrm.
Tracing is next - but when I enable trace MQE simply hangs as I have hundreds of QMs defined.
How can I get a new workspace without losing my old settings?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 28, 2021 4:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Export your old settings to an xml file. You can reimport them later.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Fri May 28, 2021 8:33 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Export and then remove all my MQE config which has been carefully nutured over many years!
It's a leap of faith for sure.
Maybe I am thinking of message broker toolkit - but I thought there was a way to switch workspaces?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| markt |
| Posted: Fri May 28, 2021 8:54 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| Under Program Files/IBM/MQExplorer/eclipse/configuration there's config.ini. Edit the osgi.instance.area to point at a different directory and that's where the new workspace will go. You'll then have the opportunity to start clean in there or copy from another existing workspace. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri May 28, 2021 10:39 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Thanks
That worked and it should really be in the product to allow selection of workspace.
Finally managed to capture a trace and so we will see what the support centre make of it.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
