| Author |
Message
|
| itsme_001 |
 Posted: Wed Mar 09, 2011 12:19 am Post subject: Not able to start sdr chl |
 |
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
hi,
I'm unable to start a sdr shl. when i try to do a chl ping it says:
"Command server not responding within timeout period. Ensure command server is running and the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' is configured to anable programs to get messages off it (AMQ4032)"
when i searched for amq4032, it told me to start the MQ explorer using strmqcfg -c. but i'm using MQ 5.3 on Windows
Wht can I do??? |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Mar 09, 2011 12:39 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
And the queue manager and general WMQ error logs say what about the state of your no-longer supported version?
_________________
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 |
|
|
| itsme_001 |
| Posted: Wed Mar 09, 2011 1:38 am Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
| Date/Time :- Tuesday March 08 12:55:48 IST 2011 |
| Host Name :- mq_uat (AIX 5.3) |
| PIDS :- 5724B4101 |
| LVLS :- 530.14 CSD14 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Dec 15 2007 |
| CMVC level :- p530-14-L071214 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000207 (mqm) |
| Program Name :- runmqlsr_nd |
| Process :- 00061062 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 1 |
| Arith1 :- 15 f |
| Comment1 :- SIGTERM |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Mar 09, 2011 1:46 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
It would have been really helpful if you'd given the full story in your original post 
What happens when you log on to the server and try the command from a console session?
_________________
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 |
|
|
| itsme_001 |
| Posted: Wed Mar 09, 2011 2:41 am Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
Hi,
I tried frm the cmd prompt.
But when I try to start the sdr chl it remains in a binding state. After I stop the channel and reset and resolve it and then try to do a chl ping it does not respond back.
Have checked in the error logs too. but could not find any errors.
In the services window I see that command server, channel initiatoer and listener are running. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Mar 09, 2011 3:14 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| itsme_001 wrote: |
| ...After I stop the channel and reset and resolve it... |
Your usual drip-feed of information 
Why are you resetting the sequence number? Why are you resolving the channel? How are you resolving the channel? Have you checked whether the 'other end' is there, in isolation of a channel ping? Have you carried out any of the diagnostics as detailed in the Info Centre and other resources?
_________________
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 |
|
|
| Mr Butcher |
| Posted: Wed Mar 09, 2011 3:30 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
i know why .... because he has none or only little MQ knowledge and is fiddling around trying to get things work.
@itsme_001
stop fiddling around with mq using commands you do not know, you do not understand and you do never looked up in the manuals. you will screw up things or make the problem even worse..... 
binding looks like a networking issue....
check what is defined in conname of the channel you are trying to start
from the machine mq is installed use a telnet to exactly that ip and port
if it does not work resolve the network issue or the issue with the remote machine.
once the telnet works (and only then) return to mqseries and start the channel and then see what you have screwed up with your commands.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 09, 2011 6:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Stop the sender channel.
Do a tcpip ping. Can you successfully do a tcpip ping from the (non-started) sender channel? If no, then it's a network issue. It's my guess, too.
_________________
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 |
|
|
| Mr Butcher |
| Posted: Wed Mar 09, 2011 7:21 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
in some installations the tcp ping is blocked by filewalls, while the mq port is open.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Mar 09, 2011 7:23 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
If there is a possibility that tcpip ping is blocked at a firewall, try to telnet from a c: or $ shell to the receiver end ip address... unless the network guys have blocked telnet traffic.
One way or another, you must validate that the sender end of the channel can see the receiver end of the channel - before your mq channels will work at all.
_________________
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 |
|
|
| santnmq |
| Posted: Wed Mar 09, 2011 8:37 pm Post subject: |
|
|
Centurion
Joined: 11 Jan 2011
Posts: 125
|
Check the configuration of the sender channel, port etc. if all seems to be fine, check if the listener is running at the RCVR end on the port specified at sender channel.
Also, check if all the mq process is running, including "amqpcsea". |
|
| Back to top |
|
|
| itsme_001 |
| Posted: Wed Mar 09, 2011 11:48 pm Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
thank you for the advice Mr. Butcher, bruce2359, exerk
The problem is with the queue 'SYSTEM.ADMIN.COMMAND.QUEUE' and not with any network or tcp/ip. Well the experts missed one thing is that its a corrupt queue issue.
After stopping the queue manager I've started the qmgr using -c parameter which brought back the qmgr into normal state with the the sdr chl ping working and then the chl stating normally.
binding looks like a networking issue -> not always....
and the commands which I've tried are from the manuals only........... |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Mar 09, 2011 11:55 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| and the commands which I've tried are from the manuals only |
i recommend not to use those commands unless you know what they do and when to use them (e.g. reset and resolve on a binding channel does not help anything).
_________________
Regards, Butcher |
|
| Back to top |
|
|
| itsme_001 |
| Posted: Thu Mar 10, 2011 12:00 am Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
| I use the reset and resolve on channels only when there is no issue with the network ports and only after stopping the channels which are in binding mode. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Mar 10, 2011 12:38 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
| But when I try to start the sdr chl it remains in a binding state. After I stop the channel and reset and resolve it and then try to do a chl ping it does not respond back. |
this and your last post still tells me that you do not know what reset and resolve really does.
reset a channel only if there is a sequence number problem.
resolve a channel only if there is a indoubt UOW.
in both cases you should investigate WHY the problem occurred before you use these commands.
using these commands without investigation and out of the box may screw up things, may make problems worse, may duplicate messages, or may result im message loss.
again, when a channel is binding, you have a networking issue (most likely). this can not be resolved by reset and resolve, even if you stop the binding channel before you issue the commands.
over and out
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
