Author |
Message
|
Gaya3 |
Posted: Fri Dec 01, 2006 4:07 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
So here the Scenario is
I believe There are couple of senders sending messages to a recvr.
Couple of steps to check.
1. Are you using the same transmission queue for sending the messages through the channels.
2. If not, check the depth of that Transmission queue and clear if messages are there
3. Then Reset and restart the channel.
4. Ensure Listeners are running on Recvr side, as you said it is using the same port, so listeners will be running.
One more check you can do
telnet <port>
Please let us know about this
Thanks and Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Last edited by Gaya3 on Fri Dec 01, 2006 4:22 am; edited 1 time in total |
|
Back to top |
|
 |
jpeela |
Posted: Fri Dec 01, 2006 4:22 am Post subject: |
|
|
 Centurion
Joined: 23 Jan 2006 Posts: 139
|
hi gayatri ,
actually we are having only one sender channel from the machine which iam discussing , but there are channels from other quemanagers sending mesages to mb machine.
but we are not even able to ping the channel.The listener on mb machine is running.while pinging we get command server not responding AMQ 4032.this was the issue previously with firewall.so should this be the problem.ofcourse we even tried stopping few channels and tried again, which still did not work. _________________ Jogi |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Dec 01, 2006 4:25 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
Start the Command server on in your current system and
check
telnet <port> or ping (both)
Please let us know about this
Thanks and Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Dec 01, 2006 4:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If you can't use telnet to connect to the listener port, then anything you try at the MQ level is a complete waste of time.
If you previously had firewall problems, it is worth your time to go back and verify that you haven't reacquired the same problems, or other firewall problems. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
jpeela |
Posted: Fri Dec 01, 2006 4:47 am Post subject: |
|
|
 Centurion
Joined: 23 Jan 2006 Posts: 139
|
hi jeff,gaytri,
the trace out from the macjine is giving the following.
Tracing route to 156.5.30.49 over a maximum of 30 hops
1 3 ms <1 ms <1 ms 192.168.x.yyy
2 7 ms 11 ms 7 ms 192.168.y.xxx
3 4 ms 7 ms 7 ms 156.5.X.JWE
4 17 ms 15 ms 15 ms 156.5.abc.asd
5 12 ms 15 ms 11 ms 156.5.as.asd
6 12 ms 15 ms 11 ms 156.5.121.241
7 11 ms 15 ms 15 ms 156.5.81.4
8 31 ms 19 ms 18 ms 62.6.6.38
9 62 ms 55 ms 64 ms 156.5.185.193
10 51 ms 47 ms 50 ms 156.5.as.af
11 89 ms 174 ms 73 ms 156.5.as.ahd
trace complete.
it shows sussful completion.
Checked out with the network guys who say that there is no fire wall enabled presently.the cammand server is running on the local machine fine.we are able to ping the destination machine as well.
but still dont understand what could be the problem.
any help.
Thanx in advance. _________________ Jogi |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Dec 01, 2006 5:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Neither traceroute nor ping are the same thing as telnet.
Make sure you can telnet to the listener port. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
jpeela |
Posted: Fri Dec 01, 2006 5:22 am Post subject: |
|
|
 Centurion
Joined: 23 Jan 2006 Posts: 139
|
hi jeff,
yes i run the command telnet IP(port)
it gave me
Connecting To 156.5.rr.oo(1423)...Could not open connection to the host, on port
23: Connect failed
yes so should this be a problem with network connection.
any suggesions.
Thanks in advance _________________ Jogi |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Dec 01, 2006 5:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
It's a problem with the way you wrote the telnet command.
On Windows, the telnet command syntax is "telnet hostname portnumber".
On unix, the telnet command syntax is "telnet hostname:portnumber". _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Dec 01, 2006 5:36 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
Ensure that your command server is running
So this problem is related to network connection.
Thanks and Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
jpeela |
Posted: Sun Dec 03, 2006 8:35 pm Post subject: |
|
|
 Centurion
Joined: 23 Jan 2006 Posts: 139
|
Hi jeff ,gayatri,
Sorry for my late response, but still I have the same problem,
telnet 156.5.xx.yy 1423 gave the following response
Connecting To 156.5.30.49...Could not open connection to the host, on port 1423:
Connect failed
and even telnet 156.5.xx.yy also gave same problem.
So cheked for the services ,started telnet service and again gave the command, but still the problem persist the same.
any solution _________________ Jogi |
|
Back to top |
|
 |
jpeela |
Posted: Sun Dec 03, 2006 8:52 pm Post subject: |
|
|
 Centurion
Joined: 23 Jan 2006 Posts: 139
|
hi all,
I have seen that telnet services are not started on other systems, and still that works fine.
And on saturday the channel kept running and today again we have the same problem can some body probe the problem,please.
awaiting your reply.
Thanks in advance. _________________ Jogi |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Dec 04, 2006 2:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You don't need telnet services.
The telnet client command just establishes a basic network connection, and lets you send raw text data.
It's a reasonable way to see that you can establish a basic network connection to some port and some address.
If it doesn't work (tells you it's connected, and then waits for you to type stuff), then nothing else will.
If it *does* work, then the network is not your problem. So go back to the rest of the suggestions, and try those and post the results. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
jpeela |
Posted: Tue Dec 05, 2006 2:44 am Post subject: |
|
|
 Centurion
Joined: 23 Jan 2006 Posts: 139
|
Hi Jeff and all,
I tried all those,presently the channel is running but at times this is happening.dont know the corredct reason .
Should this not be a problem with network,if so y other qmgrs are working fine. _________________ Jogi |
|
Back to top |
|
 |
mvic |
Posted: Tue Dec 05, 2006 3:50 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
jpeela wrote: |
Connecting To 156.5.30.49...Could not open connection to the host, on port 1423:
Connect failed |
Possibly:
The listener is not running
The listener is listening on a different port, not 1423
You have a firewall somewhere between client and server, preventing the connection. |
|
Back to top |
|
 |
bbburson |
Posted: Tue Dec 05, 2006 8:11 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004 Posts: 378 Location: Nowhere near a queue manager
|
jefflowrey wrote: |
It's a problem with the way you wrote the telnet command.
On Windows, the telnet command syntax is "telnet hostname portnumber".
On unix, the telnet command syntax is "telnet hostname:portnumber". |
No it's not. That returns Unknown host. The UNIX syntax is the same as Windows (at least the UNIXes I know about, Sun/HP/AIX). |
|
Back to top |
|
 |
|