| Author |
Message
|
| Vin |
 Posted: Tue Nov 30, 2004 10:43 am Post subject: MQJMS2005 failed to create MQQueue Manager |
 |
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
Having this problem in our test environment where in its not able to connect to the queue manager
the MQReason and completion codes it displays are 2009 and 2
Listener is running fine and there is a server connection channel that is defined too. Not sure what went wrong, any other pointers please? |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Nov 30, 2004 11:12 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Most of the 2009s that I've seen were caused by having older jar files. What kind of environment are you in - WAS, WSAD, stand-alone, etc? What version of WMQ are you using? What OS? |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Nov 30, 2004 12:39 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
On the box where the queue manager is located do the following command (UNIX):
| Code: |
| netstat -an | grep 1414 | wc -l |
or (Windows):
| Code: |
| netstat -an | grep 1414 |
By default, a queue manager can only handle 100 TOTAL channel connections. Have you exceeded it?
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| Vin |
| Posted: Tue Nov 30, 2004 1:12 pm Post subject: |
|
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
| thanks guys, I did fix this problem but not sure how? all I did was bring MQSeries down and then kill the listener manually (I think this is what made the difference, not sure how). I did check the number of server channels and its only 9, so that does not seem to have caused the problem. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Nov 30, 2004 1:20 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| I did check the number of server channels and its only 9, so that does not seem to have caused the problem. |
I think that is what has caused the problem.
If you max out on channels again, you will get the same problem.
Most likely you are not doing the MQDISC properly |
|
| Back to top |
|
|
| Vin |
| Posted: Tue Nov 30, 2004 4:10 pm Post subject: |
|
|
Master
Joined: 25 Mar 2002
Posts: 212
Location: India
|
| we have the max number of active channels set to something around 2000, so I'm not sure whether that was really the problem |
|
| Back to top |
|
|
| slaupster |
| Posted: Mon Dec 06, 2004 5:21 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2004
Posts: 41
|
If you had hit MaxChannels, then you get 2059 as the client and QMGR do in fact communicate, but the QMGR is unable to service the request due to MaxChannels being reached.
mqrc 2009 is more severe than 2059 in that the client did not even get to talk MQ protocol to the QMGR, ie the Socket connection failed completly. Usually this means that the listener is not running, connecting to the wrong port, resource problem for the OS kernel to allocate TCP connection etc.
If you are sure that the listener was running on the right port and all that, then maybe there was some anomoly going on, but in simple TCP terms, your client could not open a Socket to the host and port combo for whatever reason. |
|
| Back to top |
|
|
| knegarpetter |
| Posted: Fri Dec 10, 2004 5:04 am Post subject: |
|
|
Apprentice
Joined: 10 Dec 2004
Posts: 39
|
well, I get the same error...
when im trying to connect to "any" host... even a host i know doesnt excist... i get reason 2059.
this is driving me nuts... i have to connect to a queueManager on another server, but all i get is...
| Code: |
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'INTV1.QM'
JMSEXception Code: MQJMS2005 linked: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2058 |
crazy...
Petter[/code] |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Dec 10, 2004 6:23 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Is your MQSERVER=SVRCONN.CHL.NAME/TCP/hostname.domain.com environmental variable correctly set?
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| knegarpetter |
| Posted: Fri Dec 10, 2004 6:35 am Post subject: |
|
|
Apprentice
Joined: 10 Dec 2004
Posts: 39
|
hmmmm
To be honest, I have no idea... im new to all of this... booth to the mq and the jms issue...
"where" do i find this property?? and how do i set it.....???
Im trying to connect to a host on another server....
this is my code that i try to run, maybe im doing it all wrong...
| Code: |
factory = new MQQueueConnectionFactory();
factory.setTransportType(1);
factory.setQueueManager(QueueManager);
factory.setHostName(mqBroker);
factory.setPort(mqPort);
factory.setChannel(inChannel);
connection = factory.createQueueConnection();
|
and on the last row .. connection .. it will kick me in the nuts....
have to solve this... or else... im out on the street ....  |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Dec 10, 2004 6:41 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
The 2058 error is usually a qmgr name error. Is your qmgr name really 'INTV1.QM'? You can issue dspmq to confirm.
You can also double-check your configuration with the amqsputC program by setting the environment variable as csmith28 pointed out. |
|
| Back to top |
|
|
| knegarpetter |
| Posted: Fri Dec 10, 2004 7:06 am Post subject: |
|
|
Apprentice
Joined: 10 Dec 2004
Posts: 39
|
sorry i get 2059... with this exception :
.
| Code: |
MSEXception Code: MQJMS2005 linked: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2059
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'broker:queuemanager' |
im going nuts here....
i dont even know if it is an config in the server or if im doing something wrong in my code....
P |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Dec 10, 2004 7:33 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| knegarpetter wrote: |
| i dont even know if it is an config in the server or if im doing something wrong in my code.... |
Did you try the amqsputC with the MQSERVER? This will help you confirm that the configuration is correct or not. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Dec 10, 2004 7:41 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
| knegarpetter wrote: |
hmmmm
To be honest, I have no idea... im new to all of this... booth to the mq and the jms issue...
"where" do i find this property?? and how do i set it.....???
Im trying to connect to a host on another server....
this is my code that i try to run, maybe im doing it all wrong...
[/code]
and on the last row .. connection .. it will kick me in the nuts....
have to solve this... or else... im out on the street .... |
Log on to the Client Server and assume the identity of the USER ID that the code is running under then run the following command:
# echo $MQSERVER
If it is not set then set it using:
# export MQSERVER=
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Dec 10, 2004 7:44 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I just tried this:
| Code: |
import javax.jms.*;
import com.ibm.mq.jms.*;
public class mqtest2 {
public static void main(String[] args) throws Exception{
QueueSession session = null;
QueueConnection connection = null;
MQQueueConnectionFactory factory = null;
try {
factory = new MQQueueConnectionFactory();
factory.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP);
factory.setQueueManager("pubsub.qmgr");
factory.setHostName("bowertp");
factory.setPort(1414);
factory.setChannel("SYSTEM.DEF.SVRCONN");
connection = factory.createQueueConnection();
session = connection.createQueueSession(true, Session.AUTO_ACKNOWLEDGE);
Queue q1 = session.createQueue("SYSTEM.DEFAULT.LOCAL.QUEUE");
QueueReceiver receiver = session.createReceiver(q1, "JMSCorrelationID IS NULL");
connection.start();
System.out.println("Receive the message: " + receiver.receiveNoWait());
session.rollback();
}
finally {
session.close();
connection.close();
}}} |
and it worked for me. I'd double-check your configuration. Make sure your listener is running |
|
| Back to top |
|
|
|
|
