使用java通过SSL连接MQ7.X
我们需要使用java独立程序通过SSL连接到MQ。我们已从合作伙伴处收到使用java通过SSL连接MQ7.X,java,ssl,ibm-mq,Java,Ssl,Ibm Mq,我们需要使用java独立程序通过SSL连接到MQ。我们已从合作伙伴处收到.arm文件,并使用keytool命令安装了证书,如下所示: /opt/jdk1.8.0_121/bin/keytool -import -alias my_cert -file mycert.arm -keystore /opt/jdk1.8.0_121/jre/lib/security/cacerts Enter keystore password: --- --- ---- Trust this certificat
.arm
文件,并使用keytool
命令安装了证书,如下所示:
/opt/jdk1.8.0_121/bin/keytool -import -alias my_cert -file mycert.arm -keystore /opt/jdk1.8.0_121/jre/lib/security/cacerts
Enter keystore password:
---
---
----
Trust this certificate? [no]: yes
Certificate was added to keystore
java中连接队列管理器的程序
MQEnvironment.hostname = "XX.XX.XX.XX";
MQEnvironment.channel = "Channel_Name"; // With SSL
MQEnvironment.port = XXXX;
System.setProperty("javax.net.debug", "ssl");
System.setProperty("javax.net.ssl.trustStore", "/opt/jdk1.8.0_121/jre/lib/security/cacerts");
System.setProperty("javax.net.ssl.trustStorePassword", "trustpass");
MQEnvironment.sslCipherSuite = "SSL_RSA_WITH_RC4_128_SHA";
_queueManager = new MQQueueManager("QueueManagerName");
System.out.println("\t _queueManager : " + _queueManager);
错误获取,如下所示
keyStore type is : jks
keyStore provider is :
init keystore
init keymanager of type SunX509
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE013: Error accessing socket streams
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE013: Error accessing socket streams
Exception in thread "main" com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE013: Error accessing socket streams
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:212)
密钥库类型为:jks
密钥库提供程序是:
初始化密钥库
SunX509类型的初始化密钥管理器
MQJE001:发生MQException:完成代码2,原因2059
MQJE013:访问套接字流时出错
MQJE001:发生MQException:完成代码2,原因2059
MQJE013:访问套接字流时出错
线程“main”com.ibm.mq.MQException中的异常:MQJE001:发生MQException:完成代码2,原因2059
MQJE013:访问套接字流时出错
位于com.ibm.mq.MQManagedConnectionJ11。(MQManagedConnectionJ11.java:212)
您能否帮助我们解决此问题。根据2059与未运行的侦听器服务相关的原因
解决了问题。有一个“HTTP SSL”服务,它显然需要运行。当盒子重新启动时,它没有启动。启动服务并重新启动服务器修复了问题
根据原因,2059涉及非运行侦听器服务
解决了问题。有一个“HTTP SSL”服务,它显然需要运行。当盒子重新启动时,它没有启动。启动服务并重新启动服务器修复了问题