| Author |
Message
|
| mhashimkhan |
 Posted: Sat Aug 28, 2010 1:17 am Post subject: Problem in deployment of message set |
 |
|
Newbie
Joined: 28 Aug 2010
Posts: 5
|
I am using WMB Toolkit for MB 7
Version: 7.0.0
Build id: 7.0.0-20091028_2100
I am trying to deploy message in my execution group.
I have taken the following steps
1- Created a .bar file
2- Added my message sets (XML mxsd and a CWF mxsd).
3- Attempt to deploy in Broker
The deployment is failed due to internal error.
When i check, i found following FDC
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sat August 28 2010 17:15:06 Malay Peninsula Standard |
| UTC Time :- 1282986906.526000 |
| UTC Time Offset :- 480 ((UNKNWOWN) |
| Host Name :- MYDJ9SDM1S |
| Operating System :- Windows XP, Build 2600: SP3 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.2 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- HL010004 |
| Application Name :- MQM |
| Component :- hlgReserveLogSpace |
| SCCS Info :- lib/logger/amqhlge0.c, 1.29.2.1 |
| Line Number :- 246 |
| Build Date :- May 6 2010 |
| CMVC level :- p701-102-100504 |
| Build Type :- IKAP - (Production) |
| UserID :- 1249112 |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzlaa0.exe |
| Addressing mode :- 32-bit |
| Process :- 00004380 |
| Thread :- 00000029 |
| QueueManager :- BROKER |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 98 |
| ConnId(2) QM :- 74 |
| Last HQC :- 2.5.5-1690396 |
| Last HSHMEMB :- 2.10.10-3032800 |
| Major Errorcode :- hrcE_LOG_FULL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6709 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6709: The log for the Queue manager is full. |
| FDCSequenceNumber :- 1 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
zlaMainThread
zlaProcessMessage
zlaProcessMQIRequest
zlaMQPUT
zsqMQPUT
kpiMQPUT
kqiPutIt
kqiPutMsgSegments
apiPutMessage
aqmPutMessage
aqhPutMessage
aqqWriteMsg
aqqWriteMsgData
aqlReservePutSpace
almReserveSpace
hlgReserveLogSpace
xcsFFST
MQM Trace History
} zlaCheckStatus rc=OK
{ zcpCreateMessage
} zcpCreateMessage rc=OK
{ zcpSendOnPipe
-{ xcsResetEventSem
-} xcsResetEventSem rc=OK
-{ xcsPostEventSem
-} xcsPostEventSem rc=OK
} zcpSendOnPipe rc=OK
{ zcpReceiveOnPipe
-{ xcsWaitEventSem
-} xcsWaitEventSem rc=OK
} zcpReceiveOnPipe rc=OK
{ zlaCheckStatus
} zlaCheckStatus rc=OK
{ zcpCreateMessage
} zcpCreateMessage rc=OK
{ zcpSendOnPipe
-{ xcsResetEventSem
-} xcsResetEventSem rc=OK
-{ xcsPostEventSem
-} xcsPostEventSem rc=OK
} zcpSendOnPipe rc=OK
{ zcpReceiveOnPipe
-{ xcsWaitEventSem
-} xcsWaitEventSem rc=OK
} zcpReceiveOnPipe rc=OK
{ zlaCheckStatus
} zlaCheckStatus rc=OK
{ zcpCreateMessage
} zcpCreateMessage rc=OK
{ zcpSendOnPipe
-{ xcsResetEventSem
-} xcsResetEventSem rc=OK
-{ xcsPostEventSem
-} xcsPostEventSem rc=OK
} zcpSendOnPipe rc=OK
{ zcpReceiveOnPipe
-{ xcsWaitEventSem
-} xcsWaitEventSem rc=OK
} zcpReceiveOnPipe rc=OK
{ zlaCheckStatus
} zlaCheckStatus rc=OK
{ zcpCreateMessage
} zcpCreateMessage rc=OK
{ zcpSendOnPipe
-{ xcsResetEventSem
-} xcsResetEventSem rc=OK
-{ xcsPostEventSem
-} xcsPostEventSem rc=OK
} zcpSendOnPipe rc=OK
{ zcpReceiveOnPipe
-{ xcsWaitEventSem
-} xcsWaitEventSem rc=OK
} zcpReceiveOnPipe rc=OK
{ zlaCheckStatus
} zlaCheckStatus rc=OK
{ zcpDeleteMessage
-{ xcsFreeMemBlock
--{ xstRemoveBlockFromFreeTree
--} xstRemoveBlockFromFreeTree rc=OK
-} xcsFreeMemBlock rc=OK
} zcpDeleteMessage rc=OK
{ zlaMQPUT
-{ zcpCreateMessage
-} zcpCreateMessage rc=OK
-{ zsqMQPUT
--{ zsqVerifyQueueOrTopicObj
---{ zsqVerifyObj
---} zsqVerifyObj rc=OK
--} zsqVerifyQueueOrTopicObj rc=OK
--{ zsqVerMsgDescForPut
--} zsqVerMsgDescForPut rc=OK
--{ zsqVerOptForPutPut1
--} zsqVerOptForPutPut1 rc=OK
--{ zsqSetKernelPutParams
--} zsqSetKernelPutParams rc=OK
--{ kpiMQPUT
---{ kqiPutIt
----{ kqiVerOptForPut
----} kqiVerOptForPut rc=OK
----{ apiSyncPointCheck
-----{ atmSyncPointCheck
------{ xllSpinLockRequest
------} xllSpinLockRequest rc=OK
------{ xllSpinLockRelease
------} xllSpinLockRelease rc=OK
------{ attAllocateTransaction
-------{ xllSpinLockInit
-------} xllSpinLockInit rc=OK
------} attAllocateTransaction rc=OK
------{ atxAssociationAdd
-------{ kpiAssociateTxn
-------} kpiAssociateTxn rc=OK
------} atxAssociationAdd rc=OK
------{ atmLockTTMutex
-------{ xllLongLockRequest
-------} xllLongLockRequest rc=OK
------} atmLockTTMutex rc=OK
------{ attAddTransaction
-------{ aocHash
-------} aocHash rc=OK
------} attAddTransaction rc=OK
------{ xllLongLockRelease
------} xllLongLockRelease rc=OK
-----} atmSyncPointCheck rc=OK
----} apiSyncPointCheck rc=OK
----{ kqiInitForPutPutList
-----{ xcsQueryMTimeFn
-----} xcsQueryMTimeFn rc=OK
-----{ kqiSetContext
------{ xcsQueryPutDateTime
------} xcsQueryPutDateTime rc=OK
-----} kqiSetContext rc=OK
-----{ kqiResolveReplyQ
------{ apiEnquireObject
-------{ aouLockObjectCatalogue
--------{ xllLongLockRequest
--------} xllLongLockRequest rc=OK
-------} aouLockObjectCatalogue rc=OK
-------{ aocEnquireObject
--------{ aouLocateEntry
---------{ aotLocateEntryByName
----------{ aouHash
----------} aouHash rc=OK
---------} aotLocateEntryByName rc=MQRC_UNKNOWN_OBJECT_NAME
--------} aouLocateEntry rc=MQRC_UNKNOWN_OBJECT_NAME
-------} aocEnquireObject rc=MQRC_UNKNOWN_OBJECT_NAME
-------{ aouUnlockObjectCatalogue
--------{ xllLongLockRelease
--------} xllLongLockRelease rc=OK
-------} aouUnlockObjectCatalogue rc=OK
------} apiEnquireObject rc=MQRC_UNKNOWN_OBJECT_NAME
-----} kqiResolveReplyQ rc=OK
----} kqiInitForPutPutList rc=OK
----{ kqiVerMsgForPutPutList
----} kqiVerMsgForPutPutList rc=OK
----{ kqiSetMsgID
-----{ xcsGetUniqueTag
-----} xcsGetUniqueTag rc=OK
Data: 0x4c78d2e0 0x041f0020
----} kqiSetMsgID rc=OK
----{ kqiQPathCheckAndSet
----} kqiQPathCheckAndSet rc=OK
----{ kqiValidatePutGroupSegInfo
----} kqiValidatePutGroupSegInfo rc=OK
----{ kqiPutMsgSegments
-----{ atmStartOp
------{ atmLockDataMutex
-------{ xllLongLockRequest
-------} xllLongLockRequest rc=OK
------} atmLockDataMutex rc=OK
-----} atmStartOp rc=OK
-----{ apiHardenTransaction
------{ atmHardenTransaction
-------{ atxHardenStart
--------{ almReserveSpace
---------{ hlgReserveLogSpace
----------{ mqlReserveSpace
----------} mqlReserveSpace rc=OK
---------} hlgReserveLogSpace rc=OK
--------} almReserveSpace rc=OK
--------{ almQueryNextLSN
---------{ hlgQueryNamedLSN
---------} hlgQueryNamedLSN rc=OK
--------} almQueryNextLSN rc=OK
-------} atxHardenStart rc=OK
------} atmHardenTransaction rc=OK
-----} apiHardenTransaction rc=OK
-----{ apiLockExclusive
------{ xllLongLockRequest
------} xllLongLockRequest rc=OK
-----} apiLockExclusive rc=OK
-----{ apiPutMessage
------{ aqmPutMessage
-------{ aqsStartQOp
--------{ aqsAttachQueue
---------{ xcsAttachSetExtents
---------} xcsAttachSetExtents rc=OK
--------} aqsAttachQueue rc=OK
-------} aqsStartQOp rc=OK
-------{ aqhPutMessage
--------{ atmGetTranDetails
--------} atmGetTranDetails rc=OK
--------{ aqhLocateSpace
---------{ aqhIdxToPtrFn
Data: 0x00000000
---------} aqhIdxToPtrFn rc=OK
---------{ aqhAllocateSpace
----------{ aqtAllocateSpaceHandle
-----------{ aqtIdxToSpcFn
-----------} aqtIdxToSpcFn rc=OK
----------} aqtAllocateSpaceHandle rc=OK
----------{ aqhIdxToPtrFn
Data: 0x00002000
----------} aqhIdxToPtrFn rc=OK
----------{ aqhIdxToPtrFn
Data: 0x00004000
----------} aqhIdxToPtrFn rc=OK
Data: 0x00005412 0x00000001 0x00000001
---------} aqhAllocateSpace rc=OK
--------} aqhLocateSpace rc=OK
--------{ atmEnquireTranLastLSN
--------} atmEnquireTranLastLSN rc=OK
--------{ atmAllocNewSLE
--------} atmAllocNewSLE rc=OK
--------{ aqqWriteMsg
---------{ aqqWriteMsgData
----------{ aqlReservePutSpace
-----------{ almReserveSpace
------------{ hlgReserveLogSpace
-------------{ mqlReserveSpace
-------------} mqlReserveSpace rc=OK
------------} hlgReserveLogSpace rc=OK
-----------} almReserveSpace rc=OK
-----------{ almReserveSpace
------------{ hlgReserveLogSpace
-------------{ mqlReserveSpace
--------------{ xllLongLockRequest
--------------} xllLongLockRequest rc=OK
--------------{ mqlReclaimSpace
---------------{ mqlReleaseLogSpace
----------------{ mqlComputeHead
----------------} mqlComputeHead rc=OK
----------------{ mqlComputeHead
----------------} mqlComputeHead rc=OK
---------------} mqlReleaseLogSpace rc=OK
--------------} mqlReclaimSpace rc=OK
--------------{ xllLongLockRelease
--------------} xllLongLockRelease rc=OK
--------------{ xllSpinLockRelease
--------------} xllSpinLockRelease rc=OK
-------------} mqlReserveSpace rc=hrcE_MQLP_NOSPACE
-------------{ mqloGetGMTime
-------------} mqloGetGMTime rc=OK
-------------{ xcsBuildDumpPtr
--------------{ xcsGetMemFn
--------------} xcsGetMemFn rc=OK
-------------} xcsBuildDumpPtr rc=OK
-------------{ xcsBuildDumpPtr
-------------} xcsBuildDumpPtr rc=OK
-------------{ xcsFFST
I have check, hard disk has space as well as only one error log is currently in use. 2 are empty
Please help |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sat Aug 28, 2010 2:39 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Code: |
AMQ6709: The log for the Queue manager is full.
|
Pretty well says it all.
you say you have checked the QM.
Is this the first .bar file you have deployed to this Broker.
You could create a simple flow (MQINput->Passthru) and try deploying that.
What did you mean by 'only one log file is in use'? Which log file?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Aug 28, 2010 9:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
Probe Description :- AMQ6709: The log for the Queue manager is full.
I have check, hard disk has space as well as only one error log is currently in use. 2 are empty. |
I doubt very much that the error was a reference to the error log files...
Did you even read the content of the error logs?
What are the logging parms on your qmgr? (right click in MQExplorer and check the properties of the qmgr...) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mhashimkhan |
| Posted: Sat Aug 28, 2010 10:15 pm Post subject: |
|
|
Newbie
Joined: 28 Aug 2010
Posts: 5
|
by one error log file, i mean AMQERR01.LOG... 2 & 3 are empty.
error in MQErr
8/29/2010 13:00:56 - Process(1716.1) User(1249112) Program(amqmsrvn.exe)
Host(MYDJ9SDM1S)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1716.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier and to save any generated output files. Use either the WMQ Support
site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support
Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a
solution is already available. If you are unable to find a match, contact your
IBM support center. Do not discard these files until the problem has been
resolved.
> I am able to deploy flows, i am not able to deploy message sets.
>Log Type = Circular
Log Primary Files = 10
Log Secondary Files = 3
Write integrity = Triple write
not sure how to proceed  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Aug 28, 2010 10:30 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What is the size of your message set's bar file?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mhashimkhan |
| Posted: Sat Aug 28, 2010 10:56 pm Post subject: |
|
|
Newbie
Joined: 28 Aug 2010
Posts: 5
|
Just check, looks big 
3,300,380 bytes |
|
| Back to top |
|
|
| mhashimkhan |
| Posted: Sat Aug 28, 2010 11:42 pm Post subject: |
|
|
Newbie
Joined: 28 Aug 2010
Posts: 5
|
| is there a way to clear MQ log? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Aug 28, 2010 11:49 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Ok,
The default amount of LOG FILES Space is pretty small.
You can't change the size of the logfile without re-creating the QMGR. So your next step(s) should be ad follows:-
1) Increase the QMGR MAXMSGLEN via the runmqsc command or via the WMQ Explorer. The default 4Mb is not enough for brokers useage anyway.
2) Increase the Number of primary Log file via the gui from 10 to say 20.
3) Stop the broker.
4) Restart the QMGR. The new log files will get automatically created.
5) Start the broker.
Now Use the GUI and check the MAXMSGLEN of all the Queues starting with SYSTEM.BROKER. Change them to be the same size that you set for the QMGR in 1) above.
Check the MAXMSGLEN of the SVRCONN Channels (SYSTEM.DEF.*) and change them if needed.
Now start the broker toolkit and try the deploy again.
Alternatively,
Delete the Broker,
Delete the QMGR
Recreate the QMGR with a bigger LogfileSize and more Primary Logfiles
Alter the QMGR MAXMSGLEN
Alter the Queue MAXMSGLEN for SYSTEM.DEFAULT.LOCAL.QUEUE
Recreate the broker.
All the above is a very good reason why most experienced Broker Devs & Admins script everything.
All of my scripts make sure that there is plenty of WMQ Logfile space, the correct CCSID and MAXMSGLEN etc. I'm sure that most of the others who post regularly here have exactly the same sort of things in their 'toolbox'.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Aug 29, 2010 6:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mhashimkhan wrote: |
| by one error log file, i mean AMQERR01.LOG... 2 & 3 are empty. |
These are the not the logs the error message is referring to. Because these are not the logs the queue manager uses internally.
| mhashimkhan wrote: |
Log Type = Circular
Log Primary Files = 10
Log Secondary Files = 3
Write integrity = Triple write |
The clue is here. If it indicates 10 primary files, why do you think those 3 files are the ones in question? The other 7 are taking a quick vacation?
| mhashimkhan wrote: |
| not sure how to proceed |
You need to stop the log filing when you deploy this bar file. If you have (as you claim in the first post) plenty of disc space allocating more space to the log is a good first move.
Another good move is to find out why your bar file is so big with message sets. How many message sets are in this bar? Have you considered deploying them individually?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mhashimkhan |
| Posted: Tue Aug 31, 2010 9:35 pm Post subject: |
|
|
Newbie
Joined: 28 Aug 2010
Posts: 5
|
davies, I am able to resolve the problem my deleting and recreating the Broker 
Vitor, yes the message set is big as it contains around 20 mxsd files. Deploying separately is not an option.
Guys thanks for your support to help me resolve the issue.   |
|
| Back to top |
|
|
|
|
