| Author |
Message
|
| Pats21 |
 Posted: Wed Aug 19, 2009 2:09 pm Post subject: WMQ on WIN XP standalone machine |
 |
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi All,
I guess this is a very simple issue which I am not aware off.
I have installed WMQv6 on a standalone WIN XP machine which is not connected to any network.
The installation was finewithout any errors. I was also able to create QM's on the system.
However, once I start created a sender and receiver channel pair between the two QM's the sender channel is not starting and giving the following error.
2009/08/20 00:01:12 - Process(5576.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
AMQ9208: Error on receive from host localhost (127.0.0.1).
EXPLANATION:
An error occurred receiving data from localhost (127.0.0.1) over TCP/IP. This
may be due to a communications failure.
ACTION:
The return code from the TCP/IP (recv) call was 10054 (X'2746'). Record these
values and tell the systems administrator.
I guess this has something to do with some network setting.
Please let me know whether there is anything you know off.
Thanks.
Pats ... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Aug 19, 2009 2:19 pm Post subject: Re: WMQ on WIN XP standalone machine |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Pats21 wrote: |
I guess this has something to do with some network setting.
Please let me know whether there is anything you know off.
|
Ensure all the queue managers are listening on different ports.
Ensure any firewall installed on the machine is configured to allow the WMQ traffic.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Tue Aug 25, 2009 1:08 pm Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
| well I have checked that the QM's are running on different port and my firewall is not blocking any traffic on these ports. |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Aug 25, 2009 1:28 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Pats21 wrote: |
| well I have checked that the QM's are running on different port and my firewall is not blocking any traffic on these ports. |
You could try putting mesage locally using amqsputc.
Also, you can test telnet localhost port and see how it prompts?
Both of these steps confirm that the listener is running/working. |
|
| Back to top |
|
|
| sumit |
| Posted: Wed Aug 26, 2009 7:32 am Post subject: Re: WMQ on WIN XP standalone machine |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Pats21 wrote: |
| I have installed WMQv6 on a standalone WIN XP machine which is not connected to any network. |
It means that both the queue manager are on same machine.
Do a ping on local host and see you are getting response. Else, replace 'localhost' by either your system name or ip address and try again.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 26, 2009 7:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Take a close look at your sender channel definitions. What ipaddress did you use? Do an ipconfig. What port?
Your sender channel definitions should have CONNAME(hostipaddress(port)).
Since both qmgrs are on the same host, the port numbers must be different. Each qmgr must have a listener (object) listening on the port named in the partners sender channel def.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Wed Aug 26, 2009 1:15 pm Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi Jeevan ... as per your suggestion i tried all the three... and here is what happened ...
when i tried using amsputc program and it gave me below error:
MQCONN ended with reason code 2059
However, if i am using amqsput program then it works fine.
I also tried to telnet to the port using the following command
telnet localhost 1414
but it dint work and the following error was logged in the MQ log files
----- amqccita.c : 1727 -------------------------------------------------------
2009/08/26 23:04:13 - Process(3412.6) User(MUSR_MQADMIN) Program(amqrmppa.exe)
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record
these values and tell the systems administrator.
----- amqccita.c : 1727 -------------------------------------------------------
And YES i stopped and started the listener on the QM before doing the above and it stopped and started without any errors.
Hi Sumit ... i tried to ping on 'localhost' and my machine name and there was no problem.
Now remember this is a standalone WIN XP laptop i m using which is not connected to any network ...
Hi Bruce ... every thing looks fine .. and the port are different as well ...
What I am thinking is that as it is a standalone machine ... the traffic is not able to be routed from one port to the other .... but now i do not know what needs to be done to resolve this ....
Also below is the output of the 'ipconfig -all' command
C:\Documents and Settings\User>ipconfig -all
Windows IP Configuration
Host Name . . . . . . . . . . . . : machinename
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethern
et
Physical Address. . . . . . . . . : 00-1A-6B-D4-5D-5B
So am not sure whether this is causing a problem ... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 26, 2009 1:24 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Now remember this is a standalone WIN XP laptop i m using which is not connected to any network ... |
Yes, but: I'm guessing that you have never connected this to a network. It doesn't need to be connected to an physical network to get qmgrs to communicate in the same o/s; but you need to have configured TCP.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Wed Aug 26, 2009 1:32 pm Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
yes this machine had never been connected to a network.
Sorry but i did not get exactly what do you mean by configured for TCP??? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Aug 26, 2009 11:07 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Configured for TCP means
Configuring the network interface on the machine. This will make sure that the IP stack gets loaded.
Then 127.0.0.1 becomes a valid IP address.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Aug 26, 2009 11:54 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
THIS may be of some help to you. As your machine is completely stand-alone, and not connected to a network, completely disable any firewall to remove that as a possibility of cause.
You can find more information on Windows TCP/IP error codes HERE although the link on that page to the Microsoft site is broken.
I know it has been said earlier in the post, but ensure the listeners are running on different ports, so get it working in one direction only first by:
1. Stopping and deleting the listener in the SENDING queue manager.
2. Stop the listener in the RECEIVING queue manager, set its port to 14141*, restart the listener and check it is running.
3. Ensure the CONNAME in the SENDING queue manager channel definition is set to CONNAME('localhost(14141)') note the quotes.
4. Start the channel, and if successful, repeat in the opposite direction. If you use MQExplorer to define the listener, and try to use the same port, you will see a warning that it already in use.
* unlikely to be in use by anything.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Aug 28, 2009 2:07 pm Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi exerk ... tried all your suggestions but no luck ... 
Hi smdavies99 ... i am not sure how do this ...
also when i do a ping on localhost it gives me a reply ... also when i see the host file in 'C:\WINDOWS\system32\drivers\etc' location i see that localhost is having the ip address as 127.0.0.1.
Guys please help ... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Aug 28, 2009 2:18 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Host Name . . . . . . . . . . . . : machinename |
is this the exact output from the ipconfig command? Your hostname is 'machinename'?
So, you did a ping like this: ping machinename
| Quote: |
| also when i do a ping on localhost it gives me a reply |
What was the exact ping command you used. What is the exact reply from the ping? Paste it here.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Fri Aug 28, 2009 2:24 pm; edited 1 time in total |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Aug 28, 2009 2:22 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
The only suggestion I have left is that you hit support.microsoft.com and find out how to reinstall TCP/IP, sorry.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Aug 28, 2009 2:52 pm Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi Bruce2359,
Here is the output of the ping command
C:\Documents and Settings\User>ping localhost
Pinging user-a5f2 [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms |
|
| Back to top |
|
|
|
|
