| Author |
Message
|
| Pats21 |
 Posted: Wed Oct 03, 2007 7:05 am Post subject: MQ Tasks |
 |
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi All,
I have the following messages in my QM err logs.
************************************
10/03/07 16:28:18 - Process(553416.4) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.
10/03/07 16:28:18 - Process(553416.5) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'CHECKPOINT' has started.
10/03/07 16:28:21 - Process(569696.4) User(mqm) Program(amqzmur0)
AMQ5037: The Queue Manager task 'ERROR-LOG' has started.
10/03/07 16:28:21 - Process(569696.5) User(mqm) Program(amqzmur0)
AMQ5037: The Queue Manager task 'STATISTICS' has started.
10/03/07 16:28:21 - Process(553416.6) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'ASYNCQ' has started.
10/03/07 16:28:21 - Process(553416.7) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'EXPIRER' has started.
************************************
Can anyone let me know what are these task's ?
I searched for this tasks in the info center but dint find much info.
also the message AMQ5037 states the following:
The Queue Manager task <insert_3> has started.
Severity:
0 : Information
Explanation:
The Utility Task Manager, processId(<insert_1>) type(<insert_2>), has started the <insert_3> task.
Response:
None.
Dont know exactly what this means.
Thanks & Regards,
Pats ... |
|
| Back to top |
|
 |
| bbburson |
| Posted: Wed Oct 03, 2007 8:02 am Post subject: Re: MQ Tasks |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| Pats21 wrote: |
Severity:
0 : Information
Response:
None.
|
|
|
| Back to top |
|
|
| Pats21 |
| Posted: Wed Oct 03, 2007 10:47 pm Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Dear Bruce,
Thanks for your response !!!
I understood that these messages are just for information and that no actioin needs to be taken.
However, would like to know what these task's basically do.
Also we are facing a problem in MQ.
Following is the QM specific log files
Dir:- /var/mqm/qmgrs/BRKRDEV_QM/errors
10/03/07 18:23:12 - Process(1163708.4) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(1163708), has started the LOGGER-IO
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:12 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ7229: 10 log records accessed on queue manager 'BRKRDEV_QM' during the log
replay phase.
EXPLANATION:
10 log records have been accessed so far on queue manager BRKRDEV_QM during the
log replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:12 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ7230: Log replay for queue manager 'BRKRDEV_QM' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager BRKRDEV_QM.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:12 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ7231: 0 log records accessed on queue manager 'BRKRDEV_QM' during the
recovery phase.
EXPLANATION:
0 log records have been accessed so far on queue manager BRKRDEV_QM during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:12 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ7232: Transaction manager state recovered for queue manager 'BRKRDEV_QM'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager BRKRDEV_QM.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:12 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager
'BRKRDEV_QM'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager BRKRDEV_QM ended
have been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1163708.5) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'CHECKPOINT' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(1163708), has started the
CHECKPOINT task.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1159628.4) User(mqm) Program(amqzmur0)
AMQ5037: The Queue Manager task 'ERROR-LOG' has started.
EXPLANATION:
The Utility Task Manager, processId(1) type(1159628), has started the ERROR-LOG
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ8003: WebSphere MQ queue manager 'BRKRDEV_QM' started.
EXPLANATION:
WebSphere MQ queue manager 'BRKRDEV_QM' started.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1417508.1) User(mqm) Program(amqrrmfa)
AMQ9410: Repository manager started
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1163708.6) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'ASYNCQ' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(1163708), has started the ASYNCQ
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1159628.5) User(mqm) Program(amqzmur0)
AMQ5037: The Queue Manager task 'STATISTICS' has started.
EXPLANATION:
The Utility Task Manager, processId(1) type(1159628), has started the
STATISTICS task.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1163708.7) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'EXPIRER' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(1163708), has started the EXPIRER
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ5525: The WebSphere MQ Object Authority Manager has failed.
EXPLANATION:
The Object Authority Manager has failed to complete an MQ request.
ACTION:
Check the queue manager error logs for messages explaining the failure and try
to correct the problem accordingly.
----- amqzxma0.c : 1234 -------------------------------------------------------
10/03/07 18:23:13 - Process(1253550.1) User(mqm) Program(amqzmgr0)
AMQ5022: The Channel Initiator has started. ProcessId(917908).
EXPLANATION:
The Channel Initiator process has started.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1253550.1) User(mqm) Program(amqzmgr0)
AMQ5024: The Command Server has started. ProcessId(893316).
EXPLANATION:
The Command Server process has started.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1417508.1) User(mqm) Program(amqrrmfa)
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'BRKRDEV_QM' failed with
reason code 2195.
ACTION:
Ensure that the queue is available and retry the operation.
----- amqrrmfa.c : 3482 -------------------------------------------------------
10/03/07 18:23:13 - Process(1417508.1) User(mqm) Program(amqrrmfa)
AMQ9409: Repository manager ended abnormally.
EXPLANATION:
The repository manager ended abnormally.
ACTION:
Look at previous error messages for the repository manager in the error files
to determine the cause of the failure.
----- amqrrmfa.c : 4090 -------------------------------------------------------
10/03/07 18:23:13 - Process(917908.1) User(mqm) Program(runmqchi)
AMQ8024: WebSphere MQ channel initiator started.
EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1155536.1) User(mqm) Program(runmqchl_nd)
AMQ9002: Channel 'BRKRDEV_TO_CONFIG' is starting.
EXPLANATION:
Channel 'BRKRDEV_TO_CONFIG' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1155536.1) User(mqm) Program(runmqchl_nd)
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'BRKRDEV.CONFIGDEV.AIX.WIN.TMS.Q' on queue manager 'BRKRDEV_QM' failed with
reason code 2195.
ACTION:
Ensure that the queue is available and retry the operation.
----- amqrmssa.c : 674 --------------------------------------------------------
10/03/07 18:23:13 - Process(1155536.1) User(mqm) Program(runmqchl_nd)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'BRKRDEV_TO_CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'BRKRDEV_TO_CONFIG' in the
error files to determine the cause of the failure.
----- amqrccca.c : 777 --------------------------------------------------------
10/03/07 18:23:25 - Process(917908.1) User(mqm) Program(runmqchi)
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 941 --------------------------------------------------------
10/03/07 18:23:25 - Process(1253550.1) User(mqm) Program(amqzmgr0)
AMQ5023: The Channel Initiator has ended. ProcessId(917908).
EXPLANATION:
The Channel Initiator process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/03/07 18:23:25 - Process(1253550.1) User(mqm) Program(amqzmgr0)
AMQ5025: The Command Server has ended. ProcessId(893316).
EXPLANATION:
The Command Server process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
The Problem is that after starting the QM, it ends abnormally after few minutes.
Below is the message that we receive.
*******************************
$ strmqm BRKRDEV_QM
WebSphere MQ queue manager 'BRKRDEV_QM' starting.
10 log records accessed on queue manager 'BRKRDEV_QM' during the log replay phase.
Log replay for queue manager 'BRKRDEV_QM' complete.
Transaction manager state recovered for queue manager 'BRKRDEV_QM'.
AMQ5615: Default objects cannot be created: CompCode = 2 Reason = 2059.
$ $ $ $
$
*******************************
Any help appreciated ...
Thanks
Pats ... |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 03, 2007 11:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Try strmqm -c to rebuild the missing or invalid system object. The rest of that log is a perfectly happy v6 queue manager starting up, even the bit about logs replaying.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Thu Oct 04, 2007 3:53 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
| Most of the messages appear to be normal. The clustering messages.....not really. Have you recently migrated to V6 and possibly did not take proper steps for suspending removing, etc from the cluster? |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Oct 05, 2007 12:53 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi,
I have tried the strmqm -c option but it did not work 
yup the log looks fine ...
however, an idea on what the foll would be ...
-------------------------------------------------------------------------------
10/03/07 18:23:13 - Process(1404946.1) User(mqm) Program(amqzxma0_nd)
AMQ5525: The WebSphere MQ Object Authority Manager has failed.
EXPLANATION:
The Object Authority Manager has failed to complete an MQ request.
ACTION:
Check the queue manager error logs for messages explaining the failure and try
to correct the problem accordingly.
----- amqzxma0.c : 1234 -------------------------------------------------------
..........
10/03/07 18:23:13 - Process(1417508.1) User(mqm) Program(amqrrmfa)
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'BRKRDEV_QM' failed with
reason code 2195.
ACTION:
Ensure that the queue is available and retry the operation.
----- amqrrmfa.c : 3482 -------------------------------------------------------
..................
10/03/07 18:23:13 - Process(1155536.1) User(mqm) Program(runmqchl_nd)
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'BRKRDEV.CONFIGDEV.AIX.WIN.TMS.Q' on queue manager 'BRKRDEV_QM' failed with
reason code 2195.
ACTION:
Ensure that the queue is available and retry the operation.
----- amqrmssa.c : 674 --------------------------------------------------------
.........................
10/03/07 18:23:13 - Process(1155536.1) User(mqm) Program(runmqchl_nd)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'BRKRDEV_TO_CONFIG' ended abnormally.
ACTION:
Look at previous error messages for channel program 'BRKRDEV_TO_CONFIG' in the
error files to determine the cause of the failure.
----- amqrccca.c : 777 --------------------------------------------------------
.........................
10/03/07 18:23:25 - Process(917908.1) User(mqm) Program(runmqchi)
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 941 --------------------------------------------------------
These are the logs which might need some attention.
Pats ... |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Oct 05, 2007 2:28 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
| Also as you asked ... we have not migrated ... |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Oct 05, 2007 3:41 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Evnironment details:
OS: AIX
$ dspmqver
Name: WebSphere MQ
Version: 6.0.2.1
CMVC level: p600-201-070307
BuildType: IKAP - (Production) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Oct 05, 2007 3:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does there exist a SYSTEM.CLUSTER.TRANSMIT.QUEUE on the queue manager?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Mon Oct 08, 2007 4:20 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
We are unable to know this as the QM is not coming up.
Is there any other way to know this ?
We have checked for the folder “SYSTEM.CLUSTER.TRANSMIT.QUEUE” in the location “/var/mqm/qmgrs/BRKRDEV_QM/queues” and it is available .. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Oct 12, 2007 3:14 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
We are also looking at the option of server memory ... as the vmstat cmd output shows low free memory ...
2 0 4163098 10298 0 58 0 0 0 0 212 11513 2624 35 2 59 4
0 0 4163544 9286 0 144 0 0 0 0 221 6012 1820 17 1 73 8
1 0 4164088 8345 0 75 0 0 0 0 146 12616 2202 17 2 76 4
1 1 4164259 8055 0 92 0 0 0 0 161 6862 1908 20 2 73 6
kthr memory page faults cpu
----- ----------- ------------------------ ------------ -----------
r b avm fre re pi po fr sr cy in sy cs us sy id wa
2 0 4164978 7334 0 0 0 0 0 0 39 14242 1065 8 4 88 0
0 0 4164337 7974 0 1 0 0 0 0 17 1846 647 0 1 99 0
2 0 4164289 8022 0 0 0 0 0 0 23 7053 974 6 1 92 0
1 1 4164452 7770 0 87 0 0 0 0 141 4250 1306 19 1 75 5
0 0 4164451 7771 0 0 0 0 0 0 19 1666 547 0 1 99 0
0 0 4164449 7767 0 0 0 0 0 0 53 7593 1836 2 1 97 0
0 0 4164448 7768 0 0 0 0 0 0 11 1639 568 0 0 99 0
0 1 4164449 7681 0 83 0 0 0 0 99 3876 1283 5 1 89 5
1 1 4164449 7502 0 179 0 0 0 0 198 2544 933 2 1 85 13
0 1 4170372 3090 0 168 780 4204 7170 0 327 4360 1882 4 4 79 13
0 1 4164667 11577 0 0 2456 895 1543 0 659 5774 987 4 4 78 14
0 1 4164734 11636 0 34 317 0 0 0 582 6066 626 7 2 78 13
1 0 4164881 11234 0 148 0 0 0 0 187 6601 988 23 1 68 8
Any ideas on how much is the memory required to run a QM? |
|
| Back to top |
|
|
| ashu |
| Posted: Fri Oct 12, 2007 10:52 pm Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
| Code: |
10/03/07 18:23:13 - Process(1417508.1) User(mqm) Program(amqrrmfa)
AMQ9509: Program cannot open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object
'SYSTEM.CLUSTER.TRANSMIT.QUEUE' on queue manager 'BRKRDEV_QM' failed with
reason code 2195.
ACTION:
Ensure that the queue is available and retry the operation |
.
does the client have appropriate rights on the QMGR objects?
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| Pats21 |
| Posted: Mon Oct 15, 2007 12:52 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi,
We dont have any clients accessing this QM.
When we give the command "strmqm BRKRDEV_QM" the QM starts and within few seconds it ends with status "Ended immediately". |
|
| Back to top |
|
|
| ashu |
| Posted: Tue Oct 16, 2007 4:06 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
Why don't you define your own XMITQ? why rely on system default objects... 
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Oct 16, 2007 4:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ashu wrote: |
| Why don't you define your own XMITQ? |
Can you define your own cluster xmitq? Will the software use another queue?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
