--- Begin Message ---Hi All, I am trying to do SSL communication with Java client & MQServer on Windows NT and AIX. I have done this succesfuly with JKS format of keystore. But I am struggling with keystore of PKCS12 format. I created keystore of PKCS12 format using IBM's Ikeyman tool & imported keys from certficates( demo certificates installed in IE from GlobalSIgn). Also I used following JVM that I got from Webshphere installation. *********************************************************** java version "1.3.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32 build cn131-20021107 (JIT enabled: jitc)) ******************************************************** After that I was able to read PKCS12 keystore with your programs (SSOKeyStore.java) With this JVM when I executed program then I got runtime error message ******************************************************** Setting up MQ environment Connecting Queue Manager java.lang.RuntimeException: Invalid keystore format at com.ibm.jsse.bb.engineInit(Unknown Source) at javax.net.ssl.TrustManagerFactory.init(Unknown Source) at javax.net.ssl.SSLSocketFactory.getDefault(Unknown Source) at com.ibm.mq.SSLHelper.createSSLSocket(SSLHelper.java:112) at com.ibm.mq.MQInternalCommunications.createSocketConnection(MQInternal Communications.java:1128) at com.ibm.mq.MQInternalCommunications.access$000(MQInternalCommunications.java:110) at com.ibm.mq.MQInternalCommunications$1.run(MQInternalCommunications.ja va:444) at java.security.AccessController.doPrivileged(Native Method) at com.ibm.mq.MQInternalCommunications.<init>(MQInternalCommunications.java:441) at com.ibm.mq.MQSESSIONClient.MQCONN(MQSESSIONClient.java:1310) at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:161) at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:270) at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:290) at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80) at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:150) at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:682) at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:620) at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:393) at MQPutGet.sendReceive(MQPutGet.java:75) at MQPutGet.main(MQPutGet.java:188) MQJE001: An MQException occurred: Completion Code 2, Reason 2059 MQJE013: Error accessing socket streams MQJE001: Completion Code 2, Reason 2059 An MQSeries error occurred : Completion code 2 Reason code 2059 error reason: null finished ****************************************************** Today again then I ran my program with following Jbuilder JDK ******************************** java version "1.4.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21) Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode) ************************ & I got usual error message on console *********************************************** Setting up MQ environment Connecting Queue Manager MQJE001: An MQException occurred: Completion Code 2, Reason 2059 MQJE013: Error accessing socket streams MQJE001: Completion Code 2, Reason 2059 An MQSeries error occurred : Completion code 2 Reason code 2059 error reason:null finished ********************************************* I want to kow why the "Invalid keystore format" problem is coming with PKCS12 format while is having no trouble with JKS format.I am attaching trace of programs for both JVMs(IBM & SUN). many thanks & regards Rakesh<<winmail.dat>>
--- End Message ---
Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.