| Author |
Message
|
| shinabro |
 Posted: Fri Jan 21, 2005 7:36 am Post subject: WSAD setup with remote QM |
 |
|
Newbie
Joined: 21 Jan 2005
Posts: 5
|
I am trying to connect to a QM which is running on 390 and having problems with QCF.createQueueConnection()
InitialContext ic = new InitialContext();
QueueConnectionFactory qcf = (QueueConnectionFactory) (ic.lookup("java:comp/env/jms/QCF"));
qConnection = qcf.createQueueConnection();
The error I get from WebSphere is as follows:
MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect Closure reason = 2009
The error I get when I put the strmqtrc is as follows:
3112.2 !! - __________
3112.2 !! - MQCONN <<
3112.2 !! - Name : Input Parm
3112.2 !! - Hconn: NULL
3112.2 !! - ConnectOpts:
3112.2 Data:-
3112.2 !! - Reason:
3112.2 Data:-
3112.2 0x09F0FA70 0A 08 00 00 : ....
3112.2 --}! zstMQConnect (rc=MQRC_Q_MGR_NAME_ERROR)
3112.2 --}! lpiSPIMQConnect (rc=MQRC_Q_MGR_NAME_ERROR)
Which looks like MQ Q MGR is not set, but when I turn on JMS tracing from WebSphere, I get the following so it looks like it is passing QM.
c51415f JMSManagedCon > createConnectionFactory
[ConnectionManager]@205a0140
JNDI Name <jms/QCF>
shareable <false>
c51415f WSJMSManagedQ > createConnectionFactoryHandle
[ConnectionManager]@205a0140
JNDI Name <jms/QCF>
shareable <false>
c51415f JMSConnection > JMSConnectionFactoryHandle
com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory@540a0140
physical connection factory = null
default user name = null
object type = 4
properties = {TRAN=0, MRET=1, TM=SYSTEM.DEFAULT.MODEL.QUEUE, QMGR=MQS4}
[ConnectionManager]@205a0140
JNDI Name <jms/QCF>
shareable <false>
c51415f JMSConnection < JMSConnectionFactoryHandle
c51415f JMSQueueConne > JMSQueueConnectionFactoryHandle
com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory@540a0140
physical connection factory = null
default user name = null
object type = 4
properties = {TRAN=0, MRET=1, TM=SYSTEM.DEFAULT.MODEL.QUEUE, QMGR=MQS4}
[ConnectionManager]@205a0140
JNDI Name <jms/QCF>
shareable <false>
c51415f JMSQueueConne < JMSQueueConnectionFactoryHandle
c51415f WSJMSManagedQ < createConnectionFactoryHandle
com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle@110a8143
managed connection factory = com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory@540a0140
connection manager = com.ibm.ejs.j2c.ConnectionManager@205a0140
restricted methods enabled = false
c51415f JMSManagedCon < createConnectionFactory
com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle@110a8143
managed connection factory = com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory@540a0140
connection manager = com.ibm.ejs.j2c.ConnectionManager@205a0140
restricted methods enabled = false
c51415f JMSQueueConne > createQueueConnection
c51415f JMSConnection > JMSConnectionRequestInfo
true
c51415f JMSConnection < JMSConnectionRequestInfo
c51415f PrivExAction W J2CA0114W: No container-managed authentication alias found for connection factory or datasource JMS$QCF.
c51415f JMSManagedCon > createManagedConnection
Subject:
Principal: null
com.ibm.ejs.jms.JMSConnectionRequestInfo@4db18143
credential = null
session sharing = true
c51415f JMSManagedCon > getPasswordCredential
Subject:
Principal: null
com.ibm.ejs.jms.JMSConnectionRequestInfo@4db18143
credential = null
session sharing = true
c51415f JMSManagedCon d Using credentials from Subject
c51415f JMSManagedCon d No PasswordCredential in Subject
c51415f JMSManagedCon < getPasswordCredential
<null>
c51415f WSJMSManagedQ > createManagedConnection
<null>
c51415f JMSManagedCon > JMSManagedConnection
com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory@540a0140
physical connection factory = null
default user name = null
object type = 4
properties = {TRAN=0, MRET=1, TM=SYSTEM.DEFAULT.MODEL.QUEUE, QMGR=MQS4}
<null>
c51415f WSJMSManagedC > getConnectionFactory
c51415f WSJMSManagedC < getConnectionFactory
com.ibm.mq.jms.MQXAQueueConnectionFactory@538c3b87
c51415f JMSManagedQue > createConnection
com.ibm.mq.jms.MQXAQueueConnectionFactory@538c3b87
c51415f JMSManagedQue e Caught exception:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'MQS4'
Any ideas on what I might be doing wrong would greatly be appreciated.  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jan 21, 2005 7:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does your z/OS have the Client Connection Facility enabled?
Do you have z/OS security set up to authenticate this connection?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| shinabro |
| Posted: Fri Jan 21, 2005 8:06 am Post subject: |
|
|
Newbie
Joined: 21 Jan 2005
Posts: 5
|
Oop forgot to mention that I tried the following tools to make sure I have connectivity and/or permission. I think the tool is from IBM (but not sure)
1) rfhutil (some MQ Series client tool)
2) amqztrcn.exe |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 21, 2005 8:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
rfhutilC is the client version.
You say you tried them, did it succeed?
Are you sure you are passing the correct credentials to the mainframe?
Have your mainframe security administrator pull a violation report and see.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| shinabro |
| Posted: Fri Jan 21, 2005 8:17 am Post subject: |
|
|
Newbie
Joined: 21 Jan 2005
Posts: 5
|
Yes. I did run the utils without any problems.
That is an interesting point about the security. Would you happen to know how I can check what userid and password I am using from rfhutil.
Thanks VERY much for your quick responses. |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jan 21, 2005 8:17 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| What are your JNDI setting for QCF? |
|
| Back to top |
|
|
| shinabro |
| Posted: Fri Jan 21, 2005 8:34 am Post subject: |
|
|
Newbie
Joined: 21 Jan 2005
Posts: 5
|
For QCF on the WebSphere (with WebSphere MQ JMS Provider).
I have the following entries (others I took default)
Name: QCF
JNDI Name: jms/QCF
Queue Manager: MQS4
Host: <mainframe host name>
Port: 1435
Channel: MQS4.CLNT
Should I have any other entries |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jan 21, 2005 8:36 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
What about TRANSPORT
Is it setting to CLIENT?
If not, you should |
|
| Back to top |
|
|
| shinabro |
| Posted: Fri Jan 21, 2005 8:50 am Post subject: |
|
|
Newbie
Joined: 21 Jan 2005
Posts: 5
|
That was it. Thank you VERY much.
I have been pinning with WebSphere/MQ for a week on this. |
|
| Back to top |
|
|
|
|
