| Author |
Message
|
| pratik_oze |
 Posted: Fri Mar 20, 2009 2:47 am Post subject: error connecting to a mainframes QM from unix using JMS & |
 |
|
Apprentice
Joined: 22 Jun 2004
Posts: 34
|
I am trying to connect to an mainframes queue manager from java code running on unix box. the ssl properties have been set correctly as its been used by other codes as well.
following is the error seen on console
The hastable is: {SleepTime=10000, WaitIntervalWhileGet=100, MsgHeaderDestinationName=DEST, MsgType=FILE, SrcDirPath=/apps/test, StopFileName=/apps/test/stopfiles/receipteng.stopfile, QueueManagerName=QM, QueueName=CC.TEST.IN, SSLFile=SSL.properties, PortNumber=20032, HostName=200.1.19.1, ChannelName=CC.TEST.SVRCONN}
MQJMSHandler - ServCon Channel Details Found...
MQJMSHandler - SSL File Name: SSL.properties
MQJMSHandler - SSL File Name:SSL
Congifuring SSL from input file: SSL
MQJMSHandler - SSL Details found for the above channel...
MQJMSHandler - SSL PeerName: CN=ibmWebSphereMQQM
MQJMSHandler - SSL Chip: SSL_RSA_WITH_3DES_EDE_CBC_SHA
ssl.keyStore: /var/wmq_security/ismqsi_d/ismqsi_d.jks
ssl.keyStorePassword: tgbredsx
ssl.trustStore: /var/wmq_security/ismqsi_d/ismqsi_d.jks
ssl.trustStorePasswordtgbredsx
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
============================================
following is the error in java logger
ERROR:::MQJMS2005: failed to create MQQueueManager for 'QM'Cause- null
MQJMS2005: failed to create MQQueueManager for 'QM'
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'QM' |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Mar 20, 2009 2:54 am Post subject: Re: error connecting to a mainframes QM from unix using JMS |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pratik_oze wrote: |
I am trying to connect to an mainframes queue manager from java code running on unix box. the ssl properties have been set correctly as its been used by other codes as well.
|
By which you mean other Java apps have successfully connected to the mainframe using non-SSL channels, or that those SSL properties have been used in unix-unix comms?
If this is the first time you've tried to connect to the mainframe (SSL or non-SSL) ask the sys progs if they've got CAF running.
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Fri Mar 20, 2009 2:55 am; edited 1 time in total |
|
| Back to top |
|
|
| pratik_oze |
| Posted: Fri Mar 20, 2009 2:55 am Post subject: |
|
|
Apprentice
Joined: 22 Jun 2004
Posts: 34
|
| Same as I am trying for this one. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 20, 2009 2:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pratik_oze wrote: |
| Same as I am trying for this one. |
So which is the "same"? Java apps connecting or the SSL question?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 20, 2009 2:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If other Java is already connected to the mainframe successfully proceed as you would normally for a 2059. Especially if you're confident of the SSL.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Mar 21, 2009 9:00 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| ssl.trustStorePasswordtgbredsx |
Missing a colon somewhere there? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pratik_oze |
| Posted: Tue Mar 24, 2009 1:13 am Post subject: |
|
|
Apprentice
Joined: 22 Jun 2004
Posts: 34
|
Where do you mean?
we have the following lines included
===============================
sslKeyStorePassword = tgbredsx
sslTrustStorePassword = tgbredsx
sslCiph = TRIPLE_DES_SHA_US
sslPeerName=CN=ibmwebspheremqismqsi_d |
|
| Back to top |
|
|
|
|
