| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SSL connection doesnt work Weblogic 6.1/JSSE MQ5.1 JDK1.3.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| grammie |
 Posted: Tue May 11, 2004 3:53 am Post subject: SSL connection doesnt work Weblogic 6.1/JSSE MQ5.1 JDK1.3.1 |
 |
|
Newbie
Joined: 11 May 2004
Posts: 2
|
When I run with weblogic.jar before the jsse jars I get the following error code when I try to open a connection to mq using SSL.
Linked Exception: com.ibm.mq.MQException: MQJE001: Beendigungscode 2, Ursache 2400 ;
If the jsse jars are moved in front of the weblogic.jar then it all works correctly unfortunately in our production environment i am not allowed to do this. I believe the issue is with teh weblogic SSLSocketFactory or SSLSocket implementation but would like to know if anyone else has come across this or has an alternative solution.
regards
Graham |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 11, 2004 4:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Reason Code 2400 is
| Quote: |
MQRC_UNSUPPORTED_CIPHER_SUITE
A connection to a queue manager was requested, specifying SSL encryption. However, JSSE reported that it does not support the CipherSuite specified by the application.
This reason code occurs only with Java applications.
Corrective action: Check the CipherSuite specified by the application. Note that the names of JSSE CipherSuites differ from their equivalent CipherSpecs used by the queue manager.
Also, check that JSSE is correctly installed. |
If we believe the first part of this, then you can try changing the names of the CipherSuites you are specifying on your channels to a name that's supported by the version of JSSE that's in WebLogic.
If we believe the second part of this, then JSSE thinks it is not correctly installed - and you may have to get your classpath switched.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| grammie |
| Posted: Wed May 12, 2004 8:47 am Post subject: |
|
|
Newbie
Joined: 11 May 2004
Posts: 2
|
Well the reason was that the cipher code used by default by weblogic isnt supported.
I created a new ssl context specifying my own keystore (type JKS) and this worked, the weblogic keystore was defaulting to PKCS12
thanks for the tip |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
