|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Msgs are written to a file even for non persistence msgs |
« View previous topic :: View next topic » |
Author |
Message
|
tcsoperations |
Posted: Thu Apr 10, 2008 3:37 pm Post subject: Msgs are written to a file even for non persistence msgs |
|
|
Newbie
Joined: 13 Jan 2008 Posts: 3
|
Hi, We are performing load test and observed that the messages are written to a file which is at /var/mqm/qmgrs/QM/Q. The q is non persistent q and messages are also non peristence. The file 'q' which is in the above said path grows in due course of the test and results in 100% usage of the disk. This brings down the qmgr(QM). Can you please let me know your suggestion. Also please let me know if the delivery mode have an impact on the this.
Environment info:
1. OS : Suse linux 10
2. MQ Version: IBM Websphere MQ Series 6.0.2.3 |
|
Back to top |
|
 |
kevinQ |
Posted: Thu Apr 10, 2008 4:15 pm Post subject: |
|
|
Novice
Joined: 09 Apr 2008 Posts: 21
|
If you put too much data on the queues, the data will spill to disk, even if the messages are non-persistent. There is only limited amount of memory MQ can use on any machine. But you shouldn't see log grow. |
|
Back to top |
|
 |
mvic |
Posted: Fri Apr 11, 2008 2:13 am Post subject: Re: Msgs are written to a file even for non persistence msgs |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
tcsoperations wrote: |
and results in 100% usage of the disk. This brings down the qmgr(QM). |
Some questions:
1. can you increase the disk space
2. can you increase the number of getters on that queue to keep up with the rate of throughput being expected
3. have you got SP1 installed on SUSE10 as per http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006270
Hope this helps |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Apr 11, 2008 6:06 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Messages MQPUT to a queue live for a time in buffers in virtual storage - in anticipation of the MQGETting application consuming them. When buffers fill, buffer management software moves the messages to disk. This is working as designed.
You have successfully tested either what happens when a program gets into a loop and continuously puts messages to a queue; and/or what happens when you don't have enough disk space. You need to look at MAXDEPTH and MAXMSGLENGTH attributes of your queue, and set these attributes to something that makes business sense. _________________ 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 |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|