| Author |
Message
|
| veturi |
 Posted: Mon Jan 03, 2005 2:53 pm Post subject: WEBSPHERE MQ communication problem |
 |
|
Newbie
Joined: 03 Jan 2005
Posts: 3
|
I am trying to build a small desktop application that talks to mainframe at the backend using MQSERIES 5.3 as middle ware.
During this process, I am able to talk to the mainframe from my desktop using MQ series, but viceversa is not happenning. All the responses are getting queued up on the mainframe and are not coming back to my desktop.
when I pinged my IP address on mainframe, the ping is succesful. however the MQ ping is failing.
The sender channel on mainframe is always in 'RETRY' state.
Can some one please help me out?
_________________
Krishna K Veturi
Software Analyst. |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Jan 03, 2005 3:08 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| The sender channel on mainframe is always in 'RETRY' state. |
Is the listener on the windows running
Is the receiver channel defined on windows? Correct name? Correct case?
Is the conname right? Right port number? |
|
| Back to top |
|
|
| JT |
| Posted: Mon Jan 03, 2005 4:11 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
In the mainframe environment, are there any messages in the channel initiator address space (CHIN)?
On your desktop, are there any messages in the Windows Eventlog or AMQERR01.log file? |
|
| Back to top |
|
|
| veturi |
| Posted: Tue Jan 04, 2005 11:44 am Post subject: |
|
|
Newbie
Joined: 03 Jan 2005
Posts: 3
|
Is the listener on the windows running
A: THE LISTENER ON WINDOWS IS RUNNING
Is the receiver channel defined on windows? Correct name? Correct case?
A: THE RECIEVER CHANNEL NAME DEFINED ON DESKTOP IS A PERFECT MATCH OF THE SENDER CHANNEL ON MAINFRAME.
Is the conname right? Right port number?
CONNNAME ON MAINFRAME IS MY IPADDRESS(PORTNUMBER)
I HAVE SPECIFIED 1414 PORT#.
There are no messages on AMQERR01 file, since the communication is failing from MAINFRAME side while trying to connect to my desktop.
_________________
Krishna K Veturi
Software Analyst. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Jan 04, 2005 11:47 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| JT wrote: |
| In the mainframe environment, are there any messages in the channel initiator address space (CHIN)? |
What about this |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Jan 04, 2005 11:48 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Can you access the error log on the mainframe side? That may give a clue as to the problem.
Shirley |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Jan 04, 2005 1:01 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Given that communication to the mainframe is good.
Is the windows listener running on the same port as the Sender channel is trying to talk to?
Also...make sure that the Windoze listener is on a unique port...no other qmgr should be listening on that port on that box. |
|
| Back to top |
|
|
| veturi |
| Posted: Tue Jan 04, 2005 2:57 pm Post subject: |
|
|
Newbie
Joined: 03 Jan 2005
Posts: 3
|
| JT wrote: |
| In the mainframe environment, are there any messages in the channel initiator address space (CHIN)? |
What about this[/quote]
I couldnt find any messages in the channel initiator other than the MQ PING getting failed because of error 419 (connection reset by peers). Can someone throw some light on this error ?
| kevinf2349 wrote: |
Is the windows listener running on the same port as the Sender channel is trying to talk to? |
Yes, the listerner is on the same port as that of sender channel.
| kevinf2349 wrote: |
Also...make sure that the Windoze listener is on a unique port...no other qmgr should be listening on that port on that box.
|
Currently I have only one QMGR on my desktop.
I have a small doubt though.
My desktop OS is WINNT 4.0 with service pack 6.0. does this have any thing to do with this problem?
MQ PING on the sender channel is failing and the Sender channel is always in "RETRY' mode.
_________________
Krishna K Veturi
Software Analyst. |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Jan 04, 2005 3:35 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| the Sender channel is always in "RETRY' mode |
In which case there should be some indication in one of the CHIN SYSOUT listings as to what the problem is.
Depending on the problem, there may also be some entries in the Windows AMQERR log.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
