| Author |
Message
|
| Peter329 |
 Posted: Fri Sep 27, 2013 4:18 am Post subject: Remote Queuing - First time try! |
 |
|
Newbie
Joined: 27 Sep 2013
Posts: 9
|
Hi,
I try to setup remote queuing for the first time. So, please be patient with me!
I have defined two Queue Managers: QM1 and QM2
in QM1 I have defined
- a local Queue QM1.TO.QM2.XMITQ (qtype XMIT)
- a remote Queue RMTQ2 which points to Q2 via QM1.TO.QM2.XMITQ
- a SDR channel name: SDR.QM1 (protocol TCP, connection name host(1422), Xmitq (QM1.TO.QM2.XMITQ) )
in QM2 I have defined
- a local Queue Q2 (qtype NORMAL)
- a receiver channel name: SDR.QM1, protocol TCP
I have sent two messages to QM1.RMTQ2 ... and they have arrived at QM1.TO.QM2.XMITQ as expected.
Now I have started channel SDR.QM1 on QM1 ... (I am on a german system)
- it says: "wird gebunden" (is being bound?)
- then : "wird wiederholt" (is being restarted?)
And the messages are not transferred!
What's wrong????? Can anybody give me some help?
Regards
Peter |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Sep 27, 2013 4:28 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Welcome to MQ
Is the MQ Listener on QM2 started on port 1422?
Is there network connectivity between QM1 and port 1422 on the server hosting QM2 (as in there is no firewall blocking it?)
Do the queue manager error logs on QM2 show anything?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Peter329 |
| Posted: Fri Sep 27, 2013 6:01 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2013
Posts: 9
|
Thanks for the friendly welcome! 
Yes, there is a listener on QM2. It is named LISTENER.TCP and it is listening on port 1422. MQ Explorer shows it as "active TCP"
The two Queue managers are running on my PC ... so they are running under the same Windows 7.
How can I view the error logs on QM2? |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Fri Sep 27, 2013 6:14 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
A Queue Managers error logs are in <MQ Data Path>\Qmgrs\<QM name>\errors\AMQERR01.LOG
Command dspmqver will show what the MQ Data Path is.
Look at the bottom of the AMQERR01.LOG file and see whether there are message saying that your channel has failed to connect and why.
Cheers,
P.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Sep 27, 2013 6:44 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Because you are on Windows, you can look at Event Viewer tool because on this platform MQ writes everything that goes to the MQ error logs into the Event Viewer as well.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 27, 2013 6:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can try, on the machine that hosts QM1, a simple telnet to the listener port on QM2.
This will verify that the network itself isn't blocking you.
You say these are the same machine - is the host you are using 'localhost', or is it a fully qualified dns name?
You could also use the amqcnxc utility to verify the network connectivity. |
|
| Back to top |
|
|
| Peter329 |
| Posted: Fri Sep 27, 2013 8:59 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2013
Posts: 9
|
Thank you so much for your advices. Looking at the log I found the error: I had misspelled one of the connection names.
Now the channels start. But the messages go to the DEAD.LETTER Queue at the target Queuemanager QM2 ...
The log just says, that there was an error and that I should inspect the message, to find the reason code, why the message was not delivered.
I can display the messages in the DEAD.LETTER.QUEUE at the target QM2. But looking at the properties of the DLH of these messages, I cant find the REASON CODE, why the message could not be delivered! |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Fri Sep 27, 2013 9:11 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
The most likely reason is probably security. ie. you are not authorised to put a message to this queue. However, you are certainly best to look at the message to be certain.
There are a number of tools you can use to browse a queue and have it format out the message for you. I am biased, of course, but I would use MO71 to do this.
Cheers,
P.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| Peter329 |
| Posted: Fri Sep 27, 2013 9:55 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2013
Posts: 9
|
thx a lot for your help, Paul!
It may well be, that this is a security problem. I run under USER1 ... which is a normal user. So I have to start MQ-Explorer and the CMD command prompt window with the option "Run as Administrator".
So how could I solve this security problem? I dont want to run under an administrator ID.
Sorry, but I have never heard of MO71 ...
Shouldnt there be an easy way to find out the reason code within the DLH with MQ Explorer?
Kind regards
Peter |
|
| Back to top |
|
|
|
|
