| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ-JMS using SSL |
« View previous topic :: View next topic » |
| Author |
Message
|
| legux |
 Posted: Mon Nov 14, 2005 7:46 am Post subject: MQ-JMS using SSL |
 |
|
Novice
Joined: 14 Nov 2005
Posts: 18
|
Hi,
I am trying to connect to a queue manager using ssl.
The queue manager has a self-signed-certificate which was produced by ikeyman.
for jms i imported the certificate to a truststore.
The channel is a "server connection" channel which uses RC4_MD5_US as the ssl specification sslcauth is set to optional.
No I'm trying to get the connection.
The parameters for MQConnectionFactory are:
connectionFactory.setHostName(hostName);
connectionFactory.setPort(port);
connectionFactory.setChannel(channel);
connectionFactory.setQueueManager(queueManagerName);
connectionFactory.setTransportType(transportType);
connectionFactory.setFailIfQuiesce(failIfQuiesce);
connectionFactory.setUseConnectionPooling(true);
connectionFactory.setSSLCipherSuite("SSL_RSA_WITH_RC4_128_MD5");
When starting initializing the MQConnectionFactory i am setting the following properties:
System.setProperty("javax.net.ssl.trustStore","c:/temp/trustStore.jks");
System.setProperty("javax.net.ssl.keyStore","c:/temp/trustStore.jks");
System.setProperty("javax.net.ssl.keyStorePassword","xxx");
when starting the jboss the connection doesn't establish. (without using ssl there are no problems).
In JBOss-Logs i get a JMSException MQJMS2005.
In my log-files i get two error codes:
AMQ9208 with return code: 10054
and
AMQ9492.
Hope you can help me correcting my mistakes.
Thanks,
Steffen
Systems:
Windows xp,
JBoss 4.0
Websphere MQ V6.0 |
|
| Back to top |
|
 |
| Tibor |
| Posted: Mon Nov 14, 2005 2:33 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Switch on the SSL trace (-Djavax.net.debug=ssl) and send the output to the topic.
HTH,
Tibor |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 14, 2005 2:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Try
| Code: |
System.setProperty("javax.net.ssl.trustStore","/c:/temp/trustStore.jks");
System.setProperty("javax.net.ssl.keyStore","/c:/temp/trustStore.jks");
|
 |
|
| Back to top |
|
|
| legux |
| Posted: Mon Nov 14, 2005 11:41 pm Post subject: |
|
|
Novice
Joined: 14 Nov 2005
Posts: 18
|
Thank sfor your answers:
at first i tried to change the path to this:
System.setProperty("javax.net.ssl.trustStore","/c:/temp/trustStore.jks");
System.setProperty("javax.net.ssl.keyStore","/c:/temp/keyStore.jks");
but this had no effect.
Now it follows the debug trace:
08:39:05,724 INFO [STDOUT] setting up default SSLSocketFactory
08:39:05,724 INFO [STDOUT] use default SunJSSE impl class: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
08:39:05,724 INFO [STDOUT] class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl is loaded
08:39:05,740 INFO [STDOUT] keyStore is : c:/temp/keyStore.jks
08:39:05,740 INFO [STDOUT] keyStore type is : jks
08:39:05,740 INFO [STDOUT] keyStore provider is :
08:39:05,740 INFO [STDOUT] init keystore
08:39:05,787 INFO [STDOUT] init keymanager of type SunX509
08:39:05,959 INFO [STDOUT] ***
08:39:05,959 INFO [STDOUT] found key for : ibmwebspheremqclient
08:39:06,006 INFO [STDOUT] chain [0] = [
[
Version: V3
Subject: CN=ibmwebspheremqclient, OU=IT-Services, O=DirkRossmann GmbH, L=Burgwedel, ST=Niedersachsen, OID.2.5.4.17=30938, C=DE
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 1023 bits
modulus: 60478851073696398792754575775570250913738992900585436166851952706388563254378035582029116246258140967544345121964835459810524648735648945468210536609408407090049146417513318091492073780132202701987235828449166977762956962493007173365599371193990871427293110958724452583990774636218371653584933185296268594711
public exponent: 65537
Validity: [From: Mon Nov 14 10:38:28 CET 2005,
To: Tue Nov 14 10:38:28 CET 2006]
Issuer: CN=ibmwebspheremqclient, OU=IT-Services, O=DirkRossmann GmbH, L=Burgwedel, ST=Niedersachsen, OID.2.5.4.17=30938, C=DE
SerialNumber: [ 43785b14]
]
Algorithm: [MD5withRSA]
Signature:
0000: 0D B1 E6 B8 99 99 62 EE 55 4D 51 C7 51 70 55 AD ......b.UMQ.QpU.
0010: 45 AC 4B 76 5F D1 E1 10 F3 77 33 68 80 40 56 29 E.Kv_....w3h.@V)
0020: 1E 92 C6 98 28 1E FC A6 A9 78 25 27 12 45 F6 14 ....(....x%'.E..
0030: DC 5F 62 BC AB 92 2A 00 0F E1 45 55 1A 68 2F 18 ._b...*...EU.h/.
0040: 80 2C A2 0F AA 68 69 B7 D3 90 7B A2 15 B1 87 5C .,...hi........\
0050: 2E E2 2C 03 B8 7B 8D B3 A4 EF 2A 75 D3 11 01 97 ..,.......*u....
0060: AC 0F D7 CF 26 89 EE 69 1F 6F 3E A7 B1 AB 2D 39 ....&..i.o>...-9
0070: D3 A8 89 75 12 8C 4B 30 FC C8 D9 EE 02 95 66 EF ...u..K0......f.
]
08:39:06,006 INFO [STDOUT] ***
08:39:06,068 INFO [STDOUT] trustStore is: c:\temp\trustStore.jks
08:39:06,068 INFO [STDOUT] trustStore type is : jks
08:39:06,068 INFO [STDOUT] trustStore provider is :
08:39:06,068 INFO [STDOUT] init truststore
08:39:06,256 INFO [STDOUT] adding as trusted cert:
08:39:06,256 INFO [STDOUT] Subject: CN=Entrust.net Secure Server Certification Authority, OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS incorp. by ref. (limits liab.), O=Entrust.net, C=US
08:39:06,256 INFO [STDOUT] Issuer: CN=Entrust.net Secure Server Certification Authority, OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS incorp. by ref. (limits liab.), O=Entrust.net, C=US
08:39:06,256 INFO [STDOUT] Algorithm: RSA; Serial number: 0x374ad243
08:39:06,256 INFO [STDOUT] Valid from Tue May 25 18:09:40 CEST 1999 until Sat May 25 18:39:40 CEST 2019
08:39:06,256 INFO [STDOUT] adding as trusted cert:
08:39:06,256 INFO [STDOUT] Subject: CN=VeriSign Class 1 CA Individual Subscriber-Persona Not Validated, OU="www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)98", OU=VeriSign Trust Network, O="VeriSign, Inc."
08:39:06,256 INFO [STDOUT] Issuer: OU=Class 1 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,256 INFO [STDOUT] Algorithm: RSA; Serial number: 0xd8b4feeaad2185bf4756a9d29e17ffb
08:39:06,256 INFO [STDOUT] Valid from Tue May 12 02:00:00 CEST 1998 until Tue May 13 01:59:59 CEST 2008
08:39:06,256 INFO [STDOUT] adding as trusted cert:
08:39:06,256 INFO [STDOUT] Subject: CN=ibmwebspheremqrsm.queue.manager, OU=IT-Service, O=Dirk Rossmann GmbH, L=Burgwedel, ST=Niedersachsen, OID.2.5.4.17=30938, C=DE
08:39:06,256 INFO [STDOUT] Issuer: CN=ibmwebspheremqrsm.queue.manager, OU=IT-Service, O=Dirk Rossmann GmbH, L=Burgwedel, ST=Niedersachsen, OID.2.5.4.17=30938, C=DE
08:39:06,256 INFO [STDOUT] Algorithm: RSA; Serial number: 0x43785a57
08:39:06,256 INFO [STDOUT] Valid from Sun Nov 13 10:35:19 CET 2005 until Tue Nov 14 10:35:19 CET 2006
08:39:06,271 INFO [STDOUT] adding as trusted cert:
08:39:06,271 INFO [STDOUT] Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,271 INFO [STDOUT] Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,271 INFO [STDOUT] Algorithm: RSA; Serial number: 0x9b7e0649a33e62b9d5ee90487129ef57
08:39:06,271 INFO [STDOUT] Valid from Fri Oct 01 02:00:00 CEST 1999 until Thu Jul 17 01:59:59 CEST 2036
08:39:06,271 INFO [STDOUT] adding as trusted cert:
08:39:06,271 INFO [STDOUT] Subject: EMAILADDRESS=personal-basic@thawte.com, CN=Thawte Personal Basic CA, OU=Certification Services Division, O=Thawte Consulting, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,271 INFO [STDOUT] Issuer: EMAILADDRESS=personal-basic@thawte.com, CN=Thawte Personal Basic CA, OU=Certification Services Division, O=Thawte Consulting, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,271 INFO [STDOUT] Algorithm: RSA; Serial number: 0x0
08:39:06,271 INFO [STDOUT] Valid from Mon Jan 01 01:00:00 CET 1996 until Fri Jan 01 00:59:59 CET 2021
08:39:06,271 INFO [STDOUT] adding as trusted cert:
08:39:06,271 INFO [STDOUT] Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,287 INFO [STDOUT] Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,287 INFO [STDOUT] Algorithm: RSA; Serial number: 0x70bae41d10d92934b638ca7b03ccbabf
08:39:06,287 INFO [STDOUT] Valid from Mon Jan 29 01:00:00 CET 1996 until Wed Aug 02 01:59:59 CEST 2028
08:39:06,287 INFO [STDOUT] adding as trusted cert:
08:39:06,287 INFO [STDOUT] Subject: OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign, OU=VeriSign International Server CA - Class 3, OU="VeriSign, Inc.", O=VeriSign Trust Network
08:39:06,287 INFO [STDOUT] Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,287 INFO [STDOUT] Algorithm: RSA; Serial number: 0x254b8a853842cce358f8c5ddae226ea4
08:39:06,287 INFO [STDOUT] Valid from Thu Apr 17 02:00:00 CEST 1997 until Tue Oct 25 01:59:59 CEST 2011
08:39:06,287 INFO [STDOUT] adding as trusted cert:
08:39:06,287 INFO [STDOUT] Subject: EMAILADDRESS=personal-premium@thawte.com, CN=Thawte Personal Premium CA, OU=Certification Services Division, O=Thawte Consulting, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,287 INFO [STDOUT] Issuer: EMAILADDRESS=personal-premium@thawte.com, CN=Thawte Personal Premium CA, OU=Certification Services Division, O=Thawte Consulting, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,287 INFO [STDOUT] Algorithm: RSA; Serial number: 0x0
08:39:06,287 INFO [STDOUT] Valid from Mon Jan 01 01:00:00 CET 1996 until Fri Jan 01 00:59:59 CET 2021
08:39:06,287 INFO [STDOUT] adding as trusted cert:
08:39:06,287 INFO [STDOUT] Subject: EMAILADDRESS=personal-freemail@thawte.com, CN=Thawte Personal Freemail CA, OU=Certification Services Division, O=Thawte Consulting, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,287 INFO [STDOUT] Issuer: EMAILADDRESS=personal-freemail@thawte.com, CN=Thawte Personal Freemail CA, OU=Certification Services Division, O=Thawte Consulting, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,287 INFO [STDOUT] Algorithm: RSA; Serial number: 0x0
08:39:06,287 INFO [STDOUT] Valid from Mon Jan 01 01:00:00 CET 1996 until Fri Jan 01 00:59:59 CET 2021
08:39:06,287 INFO [STDOUT] adding as trusted cert:
08:39:06,287 INFO [STDOUT] Subject: OU=Class 1 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,287 INFO [STDOUT] Issuer: OU=Class 1 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,302 INFO [STDOUT] Algorithm: RSA; Serial number: 0xcdba7f56f0dfe4bc54fe22acb372aa55
08:39:06,302 INFO [STDOUT] Valid from Mon Jan 29 01:00:00 CET 1996 until Wed Aug 02 01:59:59 CEST 2028
08:39:06,302 INFO [STDOUT] adding as trusted cert:
08:39:06,302 INFO [STDOUT] Subject: CN=Entrust.net Secure Server Certification Authority, OU=(c) 2000 Entrust.net Limited, OU=www.entrust.net/SSL_CPS incorp. by ref. (limits liab.), O=Entrust.net
08:39:06,302 INFO [STDOUT] Issuer: CN=Entrust.net Secure Server Certification Authority, OU=(c) 2000 Entrust.net Limited, OU=www.entrust.net/SSL_CPS incorp. by ref. (limits liab.), O=Entrust.net
08:39:06,302 INFO [STDOUT] Algorithm: RSA; Serial number: 0x389b113c
08:39:06,302 INFO [STDOUT] Valid from Fri Feb 04 18:20:00 CET 2000 until Tue Feb 04 18:50:00 CET 2020
08:39:06,302 INFO [STDOUT] adding as trusted cert:
08:39:06,302 INFO [STDOUT] Subject: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 3 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,302 INFO [STDOUT] Issuer: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 3 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,302 INFO [STDOUT] Algorithm: RSA; Serial number: 0x7dd9fe07cfa81eb7107967fba78934c6
08:39:06,302 INFO [STDOUT] Valid from Mon May 18 02:00:00 CEST 1998 until Wed Aug 02 01:59:59 CEST 2028
08:39:06,302 INFO [STDOUT] adding as trusted cert:
08:39:06,302 INFO [STDOUT] Subject: EMAILADDRESS=premium-server@thawte.com, CN=Thawte Premium Server CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,302 INFO [STDOUT] Issuer: EMAILADDRESS=premium-server@thawte.com, CN=Thawte Premium Server CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,302 INFO [STDOUT] Algorithm: RSA; Serial number: 0x1
08:39:06,302 INFO [STDOUT] Valid from Thu Aug 01 02:00:00 CEST 1996 until Fri Jan 01 00:59:59 CET 2021
08:39:06,302 INFO [STDOUT] adding as trusted cert:
08:39:06,302 INFO [STDOUT] Subject: OU=Secure Server Certification Authority, O="RSA Data Security, Inc.", C=US
08:39:06,302 INFO [STDOUT] Issuer: OU=Secure Server Certification Authority, O="RSA Data Security, Inc.", C=US
08:39:06,302 INFO [STDOUT] Algorithm: RSA; Serial number: 0x2ad667e4e45fe5e576f3c98195eddc0
08:39:06,302 INFO [STDOUT] Valid from Wed Nov 09 01:00:00 CET 1994 until Fri Jan 08 00:59:59 CET 2010
08:39:06,302 INFO [STDOUT] adding as trusted cert:
08:39:06,318 INFO [STDOUT] Subject: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 4 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,318 INFO [STDOUT] Issuer: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 4 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,318 INFO [STDOUT] Algorithm: RSA; Serial number: 0x32888e9ad2f5eb1347f87fc4203725f8
08:39:06,318 INFO [STDOUT] Valid from Mon May 18 02:00:00 CEST 1998 until Wed Aug 02 01:59:59 CEST 2028
08:39:06,318 INFO [STDOUT] adding as trusted cert:
08:39:06,318 INFO [STDOUT] Subject: CN=Entrust.net Client Certification Authority, OU=(c) 2000 Entrust.net Limited, OU=www.entrust.net/GCCA_CPS incorp. by ref. (limits liab.), O=Entrust.net
08:39:06,318 INFO [STDOUT] Issuer: CN=Entrust.net Client Certification Authority, OU=(c) 2000 Entrust.net Limited, OU=www.entrust.net/GCCA_CPS incorp. by ref. (limits liab.), O=Entrust.net
08:39:06,318 INFO [STDOUT] Algorithm: RSA; Serial number: 0x389ef6e4
08:39:06,318 INFO [STDOUT] Valid from Mon Feb 07 17:16:40 CET 2000 until Fri Feb 07 17:46:40 CET 2020
08:39:06,318 INFO [STDOUT] adding as trusted cert:
08:39:06,318 INFO [STDOUT] Subject: CN=Entrust.net Client Certification Authority, OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/Client_CA_Info/CPS incorp. by ref. limits liab., O=Entrust.net, C=US
08:39:06,318 INFO [STDOUT] Issuer: CN=Entrust.net Client Certification Authority, OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/Client_CA_Info/CPS incorp. by ref. limits liab., O=Entrust.net, C=US
08:39:06,318 INFO [STDOUT] Algorithm: RSA; Serial number: 0x380391ee
08:39:06,318 INFO [STDOUT] Valid from Tue Oct 12 21:24:30 CEST 1999 until Sat Oct 12 21:54:30 CEST 2019
08:39:06,318 INFO [STDOUT] adding as trusted cert:
08:39:06,318 INFO [STDOUT] Subject: CN=VeriSign Class 2 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,318 INFO [STDOUT] Issuer: CN=VeriSign Class 2 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,318 INFO [STDOUT] Algorithm: RSA; Serial number: 0x6170cb498c5f984529e7b0a6d9505b7a
08:39:06,318 INFO [STDOUT] Valid from Fri Oct 01 02:00:00 CEST 1999 until Thu Jul 17 01:59:59 CEST 2036
08:39:06,318 INFO [STDOUT] adding as trusted cert:
08:39:06,318 INFO [STDOUT] Subject: OU=Class 2 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Issuer: OU=Class 2 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0x2d1bfc4a178da391ebe7fff58b45be0b
08:39:06,334 INFO [STDOUT] Valid from Mon Jan 29 01:00:00 CET 1996 until Wed Aug 02 01:59:59 CEST 2028
08:39:06,334 INFO [STDOUT] adding as trusted cert:
08:39:06,334 INFO [STDOUT] Subject: OU=VeriSign Class 2 OnSite Individual CA, O=VeriSign
08:39:06,334 INFO [STDOUT] Issuer: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 2 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0x43de45067e91ed3bb670e417526649b5
08:39:06,334 INFO [STDOUT] Valid from Tue May 19 02:00:00 CEST 1998 until Tue Oct 13 01:59:59 CEST 2009
08:39:06,334 INFO [STDOUT] adding as trusted cert:
08:39:06,334 INFO [STDOUT] Subject: EMAILADDRESS=server-certs@thawte.com, CN=Thawte Server CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,334 INFO [STDOUT] Issuer: EMAILADDRESS=server-certs@thawte.com, CN=Thawte Server CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, ST=Western Cape, C=ZA
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0x1
08:39:06,334 INFO [STDOUT] Valid from Thu Aug 01 02:00:00 CEST 1996 until Fri Jan 01 00:59:59 CET 2021
08:39:06,334 INFO [STDOUT] adding as trusted cert:
08:39:06,334 INFO [STDOUT] Subject: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
08:39:06,334 INFO [STDOUT] Issuer: CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0x3863b966
08:39:06,334 INFO [STDOUT] Valid from Fri Dec 24 18:50:51 CET 1999 until Tue Dec 24 19:20:51 CET 2019
08:39:06,334 INFO [STDOUT] adding as trusted cert:
08:39:06,334 INFO [STDOUT] Subject: CN=VeriSign Class 4 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Issuer: CN=VeriSign Class 4 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0xeca0a78b6e756a01cfc47ccc2f945ed7
08:39:06,334 INFO [STDOUT] Valid from Fri Oct 01 02:00:00 CEST 1999 until Thu Jul 17 01:59:59 CEST 2036
08:39:06,334 INFO [STDOUT] adding as trusted cert:
08:39:06,334 INFO [STDOUT] Subject: CN=VeriSign Class 1 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Issuer: CN=VeriSign Class 1 Public Primary Certification Authority - G3, OU="(c) 1999 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0x8b5b75568454850b00cfaf3848ceb1a4
08:39:06,334 INFO [STDOUT] Valid from Fri Oct 01 02:00:00 CEST 1999 until Thu Jul 17 01:59:59 CEST 2036
08:39:06,334 INFO [STDOUT] adding as trusted cert:
08:39:06,334 INFO [STDOUT] Subject: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 2 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Issuer: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 2 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0xb92f60cc889fa17a4609b85b706c8aaf
08:39:06,334 INFO [STDOUT] Valid from Mon May 18 02:00:00 CEST 1998 until Wed Aug 02 01:59:59 CEST 2028
08:39:06,334 INFO [STDOUT] adding as trusted cert:
08:39:06,334 INFO [STDOUT] Subject: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 1 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Issuer: OU=VeriSign Trust Network, OU="(c) 1998 VeriSign, Inc. - For authorized use only", OU=Class 1 Public Primary Certification Authority - G2, O="VeriSign, Inc.", C=US
08:39:06,334 INFO [STDOUT] Algorithm: RSA; Serial number: 0x4cc7eaaa983e71d39310f83d3a899192
08:39:06,334 INFO [STDOUT] Valid from Mon May 18 02:00:00 CEST 1998 until Wed Aug 02 01:59:59 CEST 2028
08:39:06,334 INFO [STDOUT] init context
08:39:06,365 INFO [STDOUT] trigger seeding of SecureRandom
08:39:06,365 INFO [STDOUT] done seeding SecureRandom
08:39:06,365 INFO [STDOUT] instantiated an instance of class com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
08:39:07,318 INFO [STDOUT] export control - checking the cipher suites
08:39:07,318 INFO [STDOUT] export control - no cached value available...
08:39:07,318 INFO [STDOUT] export control - storing legal entry into cache...
08:39:07,381 INFO [STDOUT] %% No cached client session
08:39:07,381 INFO [STDOUT] *** ClientHello, SSLv3
08:39:07,381 INFO [STDOUT] RandomCookie:
08:39:07,381 INFO [STDOUT] GMT: 1131974555
08:39:07,381 INFO [STDOUT] bytes = {
08:39:07,381 INFO [STDOUT] 57
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 119
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 233
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 237
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 153
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 123
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 227
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 132
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 183
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 30
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 43
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 18
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 107
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 79
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 218
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 118
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 231
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 61
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 204
08:39:07,381 INFO [STDOUT] ,
08:39:07,381 INFO [STDOUT] 253
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 183
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 71
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 95
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 175
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 40
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 26
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 19
08:39:07,396 INFO [STDOUT] ,
08:39:07,396 INFO [STDOUT] 145
08:39:07,396 INFO [STDOUT] }
08:39:07,396 INFO [STDOUT] Session ID:
08:39:07,396 INFO [STDOUT] {}
08:39:07,396 INFO [STDOUT] Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5]
08:39:07,396 INFO [STDOUT] Compression Methods: {
08:39:07,396 INFO [STDOUT] 0
08:39:07,396 INFO [STDOUT] }
08:39:07,396 INFO [STDOUT] ***
08:39:07,396 INFO [STDOUT] main, WRITE: SSLv3 Handshake, length = 45
08:39:07,897 INFO [STDOUT] main, received EOFException: error
08:39:07,897 INFO [STDOUT] main, handling exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
08:39:07,897 INFO [STDOUT] main
08:39:07,897 INFO [STDOUT] , SEND TLSv1 ALERT:
08:39:07,897 INFO [STDOUT] fatal,
08:39:07,990 INFO [STDOUT] description = handshake_failure
08:39:07,990 INFO [STDOUT] main, WRITE: TLSv1 Alert, length = 2
08:39:07,990 INFO [STDOUT] main, called closeSocket()
08:39:07,990 INFO [STDOUT] 08:39:07 [1132040347990] [main] com.ibm.mq.jms.services.psk.MessageCatalogue@4a2ec6 ==> getMessage(1)() entry
08:39:07,990 INFO [STDOUT] 08:39:07 [1132040347990] [main] com.ibm.mq.jms.services.psk.MessageCatalogue@4a2ec6 ==> getMessage(0)() entry
08:39:07,990 INFO [STDOUT] 08:39:07 [1132040347990] [main] com.ibm.mq.jms.services.psk.MessageCatalogue@4a2ec6 <== getMessage(0)() exit
08:39:07,990 INFO [STDOUT] 08:39:07 [1132040347990] [main] com.ibm.mq.jms.services.psk.MessageCatalogue@4a2ec6 <== getMessage(1)() exit
08:39:08,006 WARN [JMSContainerInvoker] JMS provider failure detected:
javax.jms.JMSException: MQJMS2005: Fehler beim Erstellen von MQQueueManager für 'localhost:RSM.QUEUE.MANAGER'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586) |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Nov 15, 2005 2:43 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Have you look at the error log on the mq server end of the channel? (AMQERR01.LOG).
Also, you could try setting up a normal SSL client channel via a channel table and trinyg to use amqsputc. If that works, that would eliminate the server end from the problem.
_________________
-wayne |
|
| Back to top |
|
|
| Tibor |
| Posted: Tue Nov 15, 2005 3:07 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| wschutz wrote: |
| Have you look at the error log on the mq server end of the channel? (AMQERR01.LOG). |
It would be very important because this:
| Code: |
| 08:39:07,897 INFO [STDOUT] main, handling exception: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake |
| wschutz wrote: |
| Also, you could try setting up a normal SSL client channel via a channel table and trinyg to use amqsputc. If that works, that would eliminate the server end from the problem. |
I'm not sure about this way because keystores are in different format (cms vs. jks).
HTH,
Tibor |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Nov 15, 2005 3:20 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| I'm not sure about this way because keystores are in different format (cms vs. jks). |
I guess the implication was that he'd also have to setup a CMS keystore on the client end. 
_________________
-wayne |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 15, 2005 3:40 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Different keystore type on the client side should not matter.
The trace shows that the certificate is being found and provided.
What I suspect is that the encryption protocol supported by the cert might not match the channel setup?
Anyway the server side trace, assuming that this was indeed the client side trace should tell us more.
Thanks
F.J. |
|
| Back to top |
|
|
| legux |
| Posted: Tue Nov 15, 2005 5:55 am Post subject: |
|
|
Novice
Joined: 14 Nov 2005
Posts: 18
|
Thanks for all your help,
in the amqerr01.log are no errors logged. Only there are only actions of starting mq-series.
| Quote: |
Also, you could try setting up a normal SSL client channel via a channel table and trinyg to use amqsputc. If that works, that would eliminate the server end from the problem. |
I have no idea how to set up a normal ssl client channel via a channel table. Can you give me a hint?
Hope you can understand it, because they are german.
15.11.2005 13:42:32 - Process(252.2) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: Die WS-Manager-Task 'LOGGER-IO' wurde gestartet.
ERKLÄRUNG:
Der Task-Manager für Dienstprogramme, Prozess-ID(0) Typ(252), hat die Task
LOGGER-IO gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(4084.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7229: 9 Protokollsätze wurden auf WS-Manager 'RSM.QUEUE.MANAGER' während der
Protokollwiederholungsphase aufgerufen.
ERKLÄRUNG:
9 Protokollsätze wurden bisher auf WS-Manager RSM.QUEUE.MANAGER während der
Protokollwiederholungsphase aufgerufen, um den WS-Manager in einen zuvor
bekannten Status zurückzuversetzen.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(4084.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7230: Die Protokollwiederholung für WS-Manager 'RSM.QUEUE.MANAGER' ist
beendet.
ERKLÄRUNG:
Die Protokollwiederholungsphase des Neustartprozesses wurde für WS-Manager
RSM.QUEUE.MANAGER beendet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(4084.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7231: 0 Protokollsätze wurden auf WS-Manager 'RSM.QUEUE.MANAGER' während der
Wiederherstellungsphase aufgerufen.
ERKLÄRUNG:
Während der Wiederherstellungsphase des Transaktionsmanagerstatus wurden bisher
0 Protokollsätze auf WS-Manager RSM.QUEUE.MANAGER aufgerufen.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(4084.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7232: Der Transaktionsmanagerstatus wurde für WS-Manager 'RSM.QUEUE.MANAGER'
wiederhergestellt.
ERKLÄRUNG:
Der Status der Transaktionen zu dem Zeitpunkt, als der WS-Manager beendet
wurde, wurde für WS-Manager RSM.QUEUE.MANAGER wiederhergestellt.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(4084.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ7233: 0 von 0 unvollständigen Transaktionen wurden für WS-Manager
'RSM.QUEUE.MANAGER' aufgelöst.
ERKLÄRUNG:
0 von 0 Transaktionen, die zum Zeitpunkt der Beendigung des WS-Managers
RSM.QUEUE.MANAGER unvollständig waren, wurden aufgelöst.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(252.3) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: Die WS-Manager-Task 'CHECKPOINT' wurde gestartet.
ERKLÄRUNG:
Der Task-Manager für Dienstprogramme, Prozess-ID(0) Typ(252), hat die Task
CHECKPOINT gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(4084.1) User(MUSR_MQADMIN) Program(amqzxma0.exe)
AMQ8003: Der WebSphere MQ-Warteschlangenmanager 'RSM.QUEUE.MANAGER' wurde
gestartet.
ERKLÄRUNG:
Der WebSphere MQ-Warteschlangenmanager 'RSM.QUEUE.MANAGER' wurde gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:32 - Process(1592.2) User(MUSR_MQADMIN) Program(amqzmur0.exe)
AMQ5037: Die WS-Manager-Task 'ERROR-LOG' wurde gestartet.
ERKLÄRUNG:
Der Task-Manager für Dienstprogramme, Prozess-ID(1) Typ(1592), hat die Task
ERROR-LOG gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:33 - Process(1592.3) User(MUSR_MQADMIN) Program(amqzmur0.exe)
AMQ5037: Die WS-Manager-Task 'STATISTICS' wurde gestartet.
ERKLÄRUNG:
Der Task-Manager für Dienstprogramme, Prozess-ID(1) Typ(1592), hat die Task
STATISTICS gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:33 - Process(1932.1) User(MUSR_MQADMIN) Program(amqrrmfa.exe)
AMQ9410: Repository-Manager gestartet.
ERKLÄRUNG:
Der Repository-Manager wurde erfolgreich gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:33 - Process(252.5) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: Die WS-Manager-Task 'EXPIRER' wurde gestartet.
ERKLÄRUNG:
Der Task-Manager für Dienstprogramme, Prozess-ID(0) Typ(252), hat die Task
EXPIRER gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:33 - Process(252.4) User(MUSR_MQADMIN) Program(amqzmuc0.exe)
AMQ5037: Die WS-Manager-Task 'ASYNCQ' wurde gestartet.
ERKLÄRUNG:
Der Task-Manager für Dienstprogramme, Prozess-ID(0) Typ(252), hat die Task
ASYNCQ gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:34 - Process(2076.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
AMQ5022: Der Kanalinitiator wurde gestartet. Prozess-ID(2172).
ERKLÄRUNG:
Der Kanalinitiatorprozess wurde gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:34 - Process(2076.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
AMQ5024: Der Befehlsserver wurde gestartet. Prozess-ID(2208).
ERKLÄRUNG:
Der Befehlsserverprozess wurde gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:34 - Process(2076.1) User(MUSR_MQADMIN) Program(amqzmgr0.exe)
AMQ5026: Das Empfangsprogramm 'LISTENER.1' wurde gestartet. Prozess-ID(2224).
ERKLÄRUNG:
Der Empfangsprogrammprozess wurde gestartet.
AKTION:
Keine.
-------------------------------------------------------------------------------
15.11.2005 13:42:35 - Process(2172.1) User(MUSR_MQADMIN) Program(runmqchi.exe)
AMQ8024: WebSphere MQ-Kanalinitiator gestartet.
ERKLÄRUNG:
Der Kanalinitiator für die Warteschlange 'SYSTEM.CHANNEL.INITQ' wurde
gestartet.
AKTION:
Keine.
------------------------------------------------------------------------------- |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 15, 2005 4:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This is just a log of the qmgr starting...
What you need to do is turn on debugging at the SSL level on the qmgr
Then we can have a look at the qmgr SSL debug log.
That would help. |
|
| Back to top |
|
|
| legux |
| Posted: Tue Nov 15, 2005 11:34 pm Post subject: |
|
|
Novice
Joined: 14 Nov 2005
Posts: 18
|
Here is the error log:
It logs, that the Password-Stash-File was not found.
In My ssl-directory .../qmgrs/rsm!queue!manager/ssl there are the following files:
key.crl
key.kdb
key.rdb
key.sth
The Password was exported, when creating the certificate.
Hope you can help me.
Thanks,
steffen
----- amqrmrsa.c : 459 --------------------------------------------------------
16.11.2005 08:29:31 - Process(6568.84) User(MUSR_MQADMIN) Program(amqrmppa.exe)
AMQ9660: SSL-Schlüssel-Repository: Die Kennwort-Stash-Datei ist nicht vorhanden
oder kann nicht verwendet werden.
ERKLÄRUNG:
Das SSL-Schlüssel-Repository kann nicht verwendet werden, da MQ kein Kennwort
für den Zugriff darauf erhalten kann. Folgende Fehlerursachen sind möglich:
(a) Die Schlüsseldatenbankdatei und die Kennwort-Stash-Datei befinden sich
nicht in dem Pfad, der für das Schlüssel-Repository konfiguriert wurde
(b) Die Schlüsseldatenbankdatei befindet sich zwar im richtigen Pfad, es wurde
jedoch keine Kennwort-Stash-Datei für sie erstellt
(c) Die Dateien befinden sich zwar im richtigen Pfad, aber die Benutzer-ID,
unter derMQ ausgeführt wird, verfügt über keinen entsprechenden Lesezugriff
(d) Mindestens eine der beiden Dateien ist beschädigt
Der Kanal ist '????'; in einigen Fällen kann der Name nicht ermittelt werden
und wird als '????' angezeigt. Der Kanal wurde nicht gestartet.
AKTION:
Vergewissern Sie sich, dass in der Variablen des Schlüssel-Repositorys der Pfad
der Schlüsseldatenbankdatei angegeben ist. Überprüfen Sie darüber hinaus, ob
der Schlüsseldatenbankdatei in demselben Verzeichnis eine Kennwort-Stash-Datei
zugeordnet wurde und ob die Benutzer-ID, unter der MQ ausgeführt wird, über
Lesezugriff auf beide Dateien verfügt. Falls sich beide Dateien bereits im
richtigen Pfad befinden und Lesezugriff auf sie besteht, löschen Sie diese und
erstellen Sie sie erneut. Starten Sie den Kanal erneut.
----- amqrssqa.c : 1044 -------------------------------------------------------
16.11.2005 08:29:31 - Process(6568.84) User(MUSR_MQADMIN) Program(amqrmppa.exe)
AMQ9660: SSL-Schlüssel-Repository: Die Kennwort-Stash-Datei ist nicht vorhanden
oder kann nicht verwendet werden.
ERKLÄRUNG:
Das SSL-Schlüssel-Repository kann nicht verwendet werden, da MQ kein Kennwort
für den Zugriff darauf erhalten kann. Folgende Fehlerursachen sind möglich:
(a) Die Schlüsseldatenbankdatei und die Kennwort-Stash-Datei befinden sich
nicht in dem Pfad, der für das Schlüssel-Repository konfiguriert wurde
(b) Die Schlüsseldatenbankdatei befindet sich zwar im richtigen Pfad, es wurde
jedoch keine Kennwort-Stash-Datei für sie erstellt
(c) Die Dateien befinden sich zwar im richtigen Pfad, aber die Benutzer-ID,
unter derMQ ausgeführt wird, verfügt über keinen entsprechenden Lesezugriff
(d) Mindestens eine der beiden Dateien ist beschädigt
Der Kanal ist '????'; in einigen Fällen kann der Name nicht ermittelt werden
und wird als '????' angezeigt. Der Kanal wurde nicht gestartet.
AKTION:
Vergewissern Sie sich, dass in der Variablen des Schlüssel-Repositorys der Pfad
der Schlüsseldatenbankdatei angegeben ist. Überprüfen Sie darüber hinaus, ob
der Schlüsseldatenbankdatei in demselben Verzeichnis eine Kennwort-Stash-Datei
zugeordnet wurde und ob die Benutzer-ID, unter der MQ ausgeführt wird, über
Lesezugriff auf beide Dateien verfügt. Falls sich beide Dateien bereits im
richtigen Pfad befinden und Lesezugriff auf sie besteht, löschen Sie diese und
erstellen Sie sie erneut. Starten Sie den Kanal erneut.
----- amqccisa.c : 1213 -------------------------------------------------------
16.11.2005 08:29:31 - Process(6568.84) User(MUSR_MQADMIN) Program(amqrmppa.exe)
AMQ9492: Das TCP/IP-Responder-Programm hat einen Fehler gefunden.
ERKLÄRUNG:
Das Responder-Programm wurde gestartet, hat jedoch einen Fehler gefunden.
AKTION:
Prüfen Sie vorhergehende Fehlernachrichten in den Fehlerdateien, um den Fehler
zu bestimmen, der vom Responder-Programm gefunden wurde.
----- amqrmrsa.c : 459 -------------------------------------------------------- |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Nov 16, 2005 2:39 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
|
| Back to top |
|
|
| legux |
| Posted: Wed Nov 16, 2005 7:07 am Post subject: |
|
|
Novice
Joined: 14 Nov 2005
Posts: 18
|
Thanks for all your help.
I have found the mistake.
in my ssl-settings at the queue manager i had the wrong link to my key.kdb...
i had assigned it to: qmgrs/rsm!queue!manager/ssl and not to:
qmgrs/rsm!queue!manager/ssl/key
i should not change the values two many times a day, while testing.
steffen |
|
| 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
|
|
|
|
