Author |
Message
|
rajesekhar.potteti |
Posted: Thu Aug 06, 2009 7:10 am Post subject: MQ Channels not runninng |
|
|
Newbie
Joined: 09 Apr 2008 Posts: 7
|
Hi my MQ channels are not running. Both the queue managers are in cluster, listeners are active. While I start the channels they are in inactive state only. Sender and receiver channels were configured properly.
Please suggest.
Raj. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Aug 06, 2009 7:23 am Post subject: Re: MQ Channels not runninng |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rajesekhar.potteti wrote: |
Please suggest. |
I suggest you read the manuals.
Channels that are in an inactive state are only a problem if they don't change to running when there's message traffic. In that instance check the channel initiator.
I'd be more concerned if they went to retrying when you started them. And question why you're manually starting cluster channels.
Bottom line - is there a problem with your cluster? Or a problem with messages not flowing? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
rajesekhar.potteti |
Posted: Thu Aug 06, 2009 7:36 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2008 Posts: 7
|
Yes you are right, my sender channels are in retrying status and receiver channels are in inactive status.
I tried starting using command prompt but its the same.
I have seen in Error log AMQERR01.LOG the following error was given @ the end.
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. |
|
Back to top |
|
 |
JosephGramig |
Posted: Thu Aug 06, 2009 7:42 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
CHANNELS:
MaxChannels=<some large number>
MaxActiveChannels=<some large number>
AdoptNewMCACheck=ALL
AdoptNewMCA=ALL
AdoptNewMCATimeout=60
TCP:
KeepAlive=Yes
ListenerBacklog=256
QMErrorLog:
ErrorLogSize=1048576
Make sure your stanzas are set to something meaningful.
What version of MQ? Better be V6 or better... |
|
Back to top |
|
 |
Vitor |
Posted: Thu Aug 06, 2009 7:44 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rajesekhar.potteti wrote: |
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. |
What did the systems administrator say?
Check also for network connectivity with telnet and do the other checks suggested on the many posts you'll find in here on retrying channels. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
exerk |
Posted: Thu Aug 06, 2009 7:44 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Windoze?
Code: |
10038: WSAENOTSOCK -- Socket operation on non-socket. |
Check the CONNAME's are correct... _________________ 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 |
|
 |
Vitor |
Posted: Thu Aug 06, 2009 7:46 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
exerk wrote: |
Check the CONNAME's are correct... |
rajesekhar.potteti wrote: |
Sender and receiver channels were configured properly. |
We must assume this has already been done. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
exerk |
Posted: Thu Aug 06, 2009 7:49 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Vitor wrote: |
exerk wrote: |
Check the CONNAME's are correct... |
rajesekhar.potteti wrote: |
Sender and receiver channels were configured properly. |
We must assume this has already been done. |
I never assume...too many times I've seen what I want, not what was actually there  _________________ 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 |
|
 |
rajesekhar.potteti |
Posted: Thu Aug 06, 2009 7:52 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2008 Posts: 7
|
Conn Names are properly configured.
Its on the local machine Iam trying, why there is a network problem is the question Iam thinking of... |
|
Back to top |
|
 |
exerk |
Posted: Thu Aug 06, 2009 8:00 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
OK, so in each queue manager:
1. CLUSRCVR is defined, which contains the correct cluster name and CONNAME details, not forgetting that it's the CONNAME of that queue manager?
2.CLUSSDR is defined, and to a Full Repository queue manager?
And there is good network connectivity to/from the server to other servers in the network? _________________ 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 |
|
 |
Vitor |
Posted: Thu Aug 06, 2009 8:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rajesekhar.potteti wrote: |
Its on the local machine Iam trying, why there is a network problem is the question Iam thinking of... |
Your local machine has no network software? Like a firewall? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|