| Author |
Message
|
| solomon_13000 |
 Posted: Tue Aug 19, 2008 1:57 am Post subject: channel retrying |
 |
|
Master
Joined: 13 Jun 2008
Posts: 284
|
Possible reasons why a channel is retrying:
1. Firewall issue
2. SSL is not up
what are the other possibilities that can cause a channel to retry?
Regards. |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Tue Aug 19, 2008 2:42 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
network down...
listener went down...
etc..
_________________
Cheers |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Tue Aug 19, 2008 3:08 am Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| Can port being used cause a channel to be retrying?. By issuing the command netstat -na it shows which port is being used. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 19, 2008 3:55 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| solomon_13000 wrote: |
| Can port being used cause a channel to be retrying?. By issuing the command netstat -na it shows which port is being used. |
This has no meaning because the command doesn't tell you who uses the port. You need to check the listnener status to verify that a listener is running on that port. To verify that you can access it from outside we suggest trying telnet host port, where host is your target MQServer and port is the port the qmgr listnener is listening on. (exit with ctrl+] +enter and type quit at the prompt.)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| belchman |
| Posted: Tue Aug 19, 2008 5:15 am Post subject: |
|
|
Partisan
Joined: 31 Mar 2006
Posts: 386
Location: Ohio, USA
|
Sender/Receiver out of sequence
Receiver stopped
XMIT queue inhibited
Angelina Jolie walking by  (would cause me to retry)
Sender/Receiver not same trptype
...
_________________
Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Aug 19, 2008 12:55 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Destination queue on the receiving end is full and no dead letter queue defined.
Destination queue on the receiving end is full and receiver channel intermittently goes to "paused" state as receiving queue manager is processing messages to dead letter queue.
Conname in sender is incorrect (either destination host is incorrect or destination listener port is incorrect).
Conname is a DNS name and DNS name cannot be resolved (due to network issue or DNS server being unavailable).
Generally, the sender channel's queue manager log will give a good clue as to the reason for the retrying status. |
|
| Back to top |
|
|
|
|
