| Author |
Message
|
| preich |
 Posted: Wed Oct 12, 2005 4:57 am Post subject: MQSeries 2009 problem: how to resolve |
 |
|
Novice
Joined: 12 Oct 2005
Posts: 15
|
(original url: http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=280&thread=97191&cat=9)
How i can resolve that connection/communication problem?
Thanks.
I have tried to setup and start mqseries server on linux, but fail with connection to queue manager
[reichp@test02 samp]$ uname -a
Linux test02.testdomain 2.4.21-20.EL #1 Wed Aug 18 20:58:25 EDT 2004 i686 i686 i386 GNU/Linux
[reichp@test02 samp]$ cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 3)
[reichp@test02 samp]$ ps -auxw | grep mqm
502 31067 0.0 0.0 3860 584 pts/3 S 18:12 0:00 grep mqm
[reichp@test02 samp]$ crtmqm -q earth.queue.manager
There are 90 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager created.
Creating or replacing default objects for earth.queue.manager.
Default objects statistics : 40 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
[reichp@test02 samp]$
[reichp@test02 samp]$ runmqsc
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
AMQ8146: WebSphere MQ queue manager not available.
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
[reichp@test02 samp]$ strmqm
There are 90 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager 'earth.queue.manager' starting.
5 log records accessed on queue manager 'earth.queue.manager' during the log replay phase.
Log replay for queue manager 'earth.queue.manager' complete.
Transaction manager state recovered for queue manager 'earth.queue.manager'.
WebSphere MQ queue manager 'earth.queue.manager' started.
[reichp@test02 samp]$
[reichp@test02 samp]$
[reichp@test02 samp]$ runmqsc
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager earth.queue.manager.
define qlocal(queue11);
1 : define qlocal(queue11);
AMQ8006: WebSphere MQ queue created.
define channel(channel11) chltype(svrconn) trptype(tcp) mcauser('mqm');
2 : define channel(channel11) chltype(svrconn) trptype(tcp) mcauser('mqm');
AMQ8014: WebSphere MQ channel created.
define listener(listener11) trptype(tcp) control(qmgr) port(5414);
3 : define listener(listener11) trptype(tcp) control(qmgr) port(5414);
AMQ8626: WebSphere MQ listener created.
start listener(listener11);
4 : start listener(listener11);
AMQ8021: Request to start WebSphere MQ Listener accepted.
start channel(channel11);
5 : start channel(channel11);
AMQ8018: Start WebSphere MQ channel accepted.
end
6 : end
5 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
[reichp@test02 samp]$ runmqlsr -t TCP -m earth.queue.manager &
[1] 31172
[reichp@test02 samp]$ 5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
[reichp@test02 samp]$ ps -auxw | grep mqm
mqm 31107 0.0 0.7 65776 7556 ? S 18:12 0:00 amqzxma0 -m earth.queue.manager
mqm 31112 0.0 0.3 39836 4064 ? S 18:12 0:00 /opt/mqm/bin/amqzfuma -m earth.queue.manager
mqm 31114 0.0 0.3 28604 3556 ? S 18:12 0:00 amqzmuc0 -m earth.queue.manager
mqm 31119 0.0 0.3 32056 3624 ? S 18:12 0:00 amqzmur0 -m earth.queue.manager
mqm 31122 0.0 0.2 30448 2480 ? S 18:12 0:00 /opt/mqm/bin/amqrrmfa -t2332800 -s2592000 -p2592000 -g5184000 -c3600 -m earth.queue.manager
mqm 31125 0.0 0.2 34780 2320 ? S 18:12 0:00 /opt/mqm/bin/amqzdmaa -m earth.queue.manager
mqm 31128 0.0 0.2 20572 2332 ? S 18:12 0:00 /opt/mqm/bin/amqzmgr0 -m earth.queue.manager
mqm 31139 0.0 0.5 41680 5272 ? S 18:12 0:00 amqzlaa0 -mearth.queue.manager -fip0
mqm 31142 0.0 0.2 28984 2296 ? S 18:12 0:00 /opt/mqm/bin/runmqchi -m earth.queue.manager -r
mqm 31143 0.0 0.2 22764 2300 ? S 18:12 0:00 /opt/mqm/bin/amqpcsea earth.queue.manager
mqm 31158 0.0 0.2 17088 2200 ? S 18:12 0:00 /opt/mqm/bin/runmqlsr -r -m earth.queue.manager -t TCP -p 5414
mqm 31172 0.0 0.2 17088 2076 pts/3 S 18:12 0:00 runmqlsr -t TCP -m earth.queue.manager
mqm 31188 0.0 0.2 17372 2692 ? S 18:13 0:00 /opt/mqm/bin/amqrmppa -m earth.queue.manager
502 31202 0.0 0.0 3864 584 pts/3 S 18:17 0:00 grep mqm
[reichp@test02 samp]$
[reichp@test02 samp]$ telnet test02 5414
Trying 192.168.161.12...
Connected to test02.bsteam.ru (192.168.161.12).
Escape character is '^]'.
Connection closed by foreign host.
IBM Websphere MQ -> add queue manager (test02, 5414, channel11) show me an error:
"Could not estabilish a connection to the queue manager (AMQ4059)".
From pavelr machine i can connect to test02:5414 as well. Change port to 1414 (standard for mqseries) not resolve the problem.
I have also tried with simple java client:
import com.ibm.mq.*;
public class MQSeriesTest {
public String queueManagerName;
public String queueName;
public MQSeriesTest(String server, int port, String queueManager, String channel, String queue)
{
MQEnvironment.hostname = server;
MQEnvironment.port = port;
MQEnvironment.channel = channel;
MQEnvironment.properties.put(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES_CLIENT);
this.queueManagerName = queueManager;
this.queueName = queue;
}
public void sendTestMessage() throws Exception
{
MQQueueManager queueManager = new MQQueueManager(queueManagerName);
System.out.println("DONE1");
MQQueue queue = queueManager.accessQueue(queueName, MQC.MQOO_OUTPUT);
MQMessage message = new MQMessage();
message.writeUTF("This is a test message from Java");
queue.put(message);
queueManager.disconnect();
}
public static void main(String args[]) {
try {
new MQSeriesTest("test02", 1414, "earth.queue.manager", "channel11", "queue11").sendTestMessage();
} catch (Exception e) {
e.printStackTrace();
}
}
}
and have
MQJE001: ?л???м?л ??м??????? MQException: ?л? ?????????? 2, ╗?????? 2009
MQJE016: ???????????л? л??????о MQ ?????????л ??м??? м???? ? ╗?л╡???? ╗л?м???????
??????? ??м????? = 2009
MQJE001: ?л???м?л ??м??????? MQException: ?л? ?????????? 2, ╗?????? 2009
MQJE016: ???????????л? л??????о MQ ?????????л ??м??? м???? ? ╗?л╡???? ╗л?м???????
??????? ??м????? = 2009
com.ibm.mq.MQException: MQJE001: ?л???м?л ??м??????? MQException: ?л? ?????????? 2, ╗?????? 2009
MQJE016: ???????????л? л??????о MQ ?????????л ??м??? м???? ? ╗?л╡???? ╗л?м???????
??????? ??м????? = 2009
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:338)
at com.ibm.mq.StoredManagedConnection.(StoredManagedConnection.java:84)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:168)
at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:772)
at com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:697)
at com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:657)
at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:153)
at com.ibm.mq.MQQueueManager.(MQQueueManager.java:451)
at MQSeriesTest.sendTestMessage(MQSeriesTest.java:1
at MQSeriesTest.main(MQSeriesTest.java:29)
Caused by: com.ibm.mqservices.MQInternalException: MQJE001: ?л???м?л ??м??????? MQException: ?л? ?????????? 2, ╗?????? 2009
MQJE016: ???????????л? л??????о MQ ?????????л ??м??? м???? ? ╗?л╡???? ╗л?м???????
??????? ??м????? = 2009
at com.ibm.mq.MQv6InternalCommunications.checkControlFlags(MQv6InternalCommunications.java:740)
at com.ibm.mq.MQv6InternalCommunications.establishChannel(MQv6InternalCommunications.java:656)
at com.ibm.mq.MQv6InternalCommunications.initialize(MQv6InternalCommunications.java:206)
at com.ibm.mq.MQv6InternalCommunications.(MQv6InternalCommunications.java:102)
at com.ibm.mq.MQSESSIONClient.MQCONNX(MQSESSIONClient.java:1337)
at com.ibm.mq.MQSESSIONClient.MQCONN(MQSESSIONClient.java:1246)
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:184)
... 11 more
So, 2009 code is a
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
MQJE001: Completion Code 2, Reason 2009
How i can resolve that problem, with connection/communication problems with mqseries on linux and mqseries client on windows?
TCP connection with telnet to test02:1414 is okay. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Oct 12, 2005 5:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why did you put in 1414, when you know that your listener is running on 5414?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| preich |
| Posted: Wed Oct 12, 2005 5:03 am Post subject: |
|
|
Novice
Joined: 12 Oct 2005
Posts: 15
|
| It is not general problem, i have tried 1414/5414 - in both cases it have equals result. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 5:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It will abosolutely *never* work with 1414.
So don't even bother trying it.
Look for errors in the Windows event log on the client.
Look for errors in the qmgr error logs on the server machine.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| xxx |
| Posted: Wed Oct 12, 2005 5:16 am Post subject: |
|
|
Centurion
Joined: 13 Oct 2003
Posts: 137
|
I would create a remote queue and local queue on the remote box,
then use amqsput on QR and check if the channels start and the message reaches local queue on the remote box,
If that is fine I would check the id with which java program is run , |
|
| Back to top |
|
|
| preich |
| Posted: Wed Oct 12, 2005 5:18 am Post subject: |
|
|
Novice
Joined: 12 Oct 2005
Posts: 15
|
Thanks for reply, but can you explain:
1.Why i can't use 1414 port, as i know it is standard port for mqseries server?
I have seen /var/mqm/qmgrs/errors and found next lines (when i have connected with my java mqseries client)
10/12/2005 05:11:23 PM - Process(32029.195) User(dsukhoroslov) Program(amqrmppa)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'channel11' ended abnormally.
ACTION:
Look at previous error messages for channel program 'channel11' in the error
files to determine the cause of the failure.
What's problem with channel11 in my configuration?
Thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 5:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can't use a qremote to talk to the same qmgr. And being able to put messages to a local queue using bindings will do nothing to help you solve your client connection issue.
You can use amqsputC to try to establish a client connection from the client windows machine.
You can use amqscnxc to try and establish a client connection from the client windows machine.
| preich wrote: |
| 1.Why i can't use 1414 port, as i know it is standard port for mqseries server? |
It's not the *standard* port, it's the *default* port.
You can't use it because you aren't running your listener against that port.
| preich wrote: |
| What's problem with channel11 in my configuration? |
I don't know.
You'll have to
| Quote: |
ACTION:
Look at previous error messages for channel program 'channel11' in the error
files to determine the cause of the failure. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Oct 12, 2005 5:25 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| Quote: |
Look at previous error messages for channel program 'channel11' in the error
files to determine the cause of the failure.
|
What was the previous error message? Did you even read the AMQ9999?
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Oct 12, 2005 5:28 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Looks like you have defined a channel called CHANNEL11 and are trying to access it as channel11.
Check the channel definitions.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 5:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| preich |
| Posted: Wed Oct 12, 2005 5:39 am Post subject: |
|
|
Novice
Joined: 12 Oct 2005
Posts: 15
|
Ok, thanks - with uppercase CHANNEl11 it works on 5414 port.
Thanks! |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Oct 12, 2005 7:05 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
if i get all the time - that was wasted because of upper-lowercase sensitivity - added to my lifetime, then i would live forever 
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
