| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| TLSv1.2 protocol in message broker 7.0.0.8 |
« View previous topic :: View next topic » |
| Author |
Message
|
| fjb_saper |
 Posted: Mon Nov 13, 2017 5:51 am Post subject: |
 |
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Have you looked at restricted vs unrestricted JCE SSL JVM capabilities? 
_________________
MQ & Broker admin |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Nov 13, 2017 7:52 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
If you ever get around to finding the SSL trace file, it will provide more information on the available ciphers being negotiated.
Hint: The error message you are quoting is NOT the SSL trace.
/var/mqsi/components/<broker_name>/<execution_group_long-hex-uuid>
The easiest way to get the hex UUID is to look for the process for this execution group.
_________________
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 |
|
|
| prabhuoist |
| Posted: Tue Nov 14, 2017 4:16 am Post subject: |
|
|
Apprentice
Joined: 10 Oct 2017
Posts: 39
|
Hi There,
Thanks a lot for your suggestions.
We have found out the cause. We were using certificate which was having RC4 cypher and In java.security we are blocking this cypher.
jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768
hence it was not working. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
