| Author |
Message
|
| mqonnet |
 Posted: Tue Jan 20, 2004 12:10 pm Post subject: |
 |
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
The way it works and should work is, the log(actual files on disk) are opened to write the message(persistent) to it. Once done with writing, if was within a UOW, it is committed.
So, assuming the above is how it is designed to work and that it is working right, i would expect the log files size to increase as you are doing your put/commit.
But again, the storage mechanism/rules are different depending upon the platform. And i cant really comment on the specifics. But what i mentioned above is how it should behave.
Now, you never mentioned if the messages were put to a local queue or to a remote queue. If remote queue, it makes sense that the message was sent accross to the remote end and it might have take a little extra time(of course not minutes) than put to a local queue. Also the message size counts towards the time it takes to write out to log.
Also the best way to figure out if a message actually made to the destination queue is to look at the queue or run amqsbcg against it rather than look at the physical queue files(i know your situation was different and you had to prove that it really made it to the queue).
Hope this throws some more insight.
Cheers
Kumar |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Tue Jan 20, 2004 1:48 pm Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
They will appear in the q file if the message buffer for the queue is filled.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| Carla Viragh |
| Posted: Wed Jan 21, 2004 4:38 am Post subject: |
|
|
Voyager
Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil
|
Well... I tested this delay putting a message in a local queue... But you are right when you say it´s different on each plataform.
Thanks for all ... you are great!
_________________
Carla Viragh |
|
| Back to top |
|
|
| techno |
| Posted: Wed Jan 21, 2004 8:53 am Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
When MQPUT is done and when the msg is persistent, it is written to both log and queue file. Isn't it?
Thanks |
|
| Back to top |
|
|
| Carla Viragh |
| Posted: Wed Jan 21, 2004 11:01 am Post subject: |
|
|
Voyager
Joined: 31 Oct 2003
Posts: 92
Location: São Paulo - Brasil
|
| techno wrote: |
When MQPUT is done and when the msg is persistent, it is written to both log and queue file. Isn't it?
Thanks |
Yes.
But I asked why there is a delay on Q file (after a lot of minutes a persistent message is in a local queue, MQ writes the message to Q file) and we think it´s MQ structure, probably to save time.
_________________
Carla Viragh |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Jan 22, 2004 2:02 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Just to give a high level answer, MQ's concern is that should the power be pulled at any point in time, all committed persistent messages are retained. The other aim of MQ is to perform as fast as possible, and that means minimize the disk i/os. Because of this there is no need to write to the Q file *if* replaying the logs gives you the same position. Similarly though we cant hold the whole of every queue in memory, so there are buffer implications as to what gets written when.
This changes release on release as more and more complex optimizations boost performance. You should not care what is inside MQ's internal data strucutres nor files, and certainly not rely on them |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Jan 22, 2004 10:05 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Jason,
Hence your comment in another thread about rebuilding the Logs from another install being 'dangerous' these days.
Thanks for the insights.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
