Author |
Message
|
sadmin234 |
Posted: Tue Dec 02, 2003 6:11 pm Post subject: Log question replay messages |
|
|
Newbie
Joined: 02 Dec 2003 Posts: 1
|
I want replay messages from time t1 to time t2 for a certain queue. The logs are linear and saved. What are the different methods I can use.
Thank you |
|
Back to top |
|
 |
EddieA |
Posted: Wed Dec 03, 2003 9:30 am Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
The logs are not available for 'replay' purposes. They are only used to allow message persistence across failures, and if you use linear, recovery from damaged objects.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
justinaron |
Posted: Wed Dec 03, 2003 6:43 pm Post subject: |
|
|
Newbie
Joined: 03 Dec 2003 Posts: 1
|
|
Back to top |
|
 |
Michael Dag |
Posted: Thu Dec 04, 2003 2:25 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
amaverick |
Posted: Thu Jan 22, 2004 5:19 am Post subject: Replay |
|
|
Newbie
Joined: 22 Jan 2004 Posts: 9
|
|
Back to top |
|
 |
sanvaranasi |
Posted: Thu Mar 25, 2004 12:42 am Post subject: Dont want to use a tool. Want to do it myself |
|
|
 Novice
Joined: 24 Feb 2004 Posts: 10 Location: india
|
Hi,
Most of you have mentioned third party tools for replaying messages from time t1 to time t2. Is there anyone who has done it without use of third party tools? What is the mechanism.
sanjay |
|
Back to top |
|
 |
Frank Nellion |
Posted: Thu Mar 25, 2004 12:55 am Post subject: |
|
|
 Newbie
Joined: 29 Jan 2004 Posts: 5 Location: UK
|
Well then its back to your own drawing board lots of time effort, and of course maintenance if/when things change. Using API's and standard code and protocols, identify where and what in the log you can rely on, and create some user code. |
|
Back to top |
|
 |
markt |
Posted: Thu Mar 25, 2004 9:20 am Post subject: |
|
|
 Knight
Joined: 14 May 2002 Posts: 508
|
Even persistent messages might not be written to the log. (There are times when it is safe not to do so, and hence performance improves.) So don't rely on the logs as any level of historical guarantee of what messages were transmitted. |
|
Back to top |
|
 |
Nick Beckson |
Posted: Thu Mar 25, 2004 11:08 am Post subject: Log question replay messages |
|
|
Newbie
Joined: 23 Jan 2004 Posts: 1
|
Hi,
In what circumstances would a persistent message that is commited not be written to the recovery log ? |
|
Back to top |
|
 |
Remco |
Posted: Fri Mar 26, 2004 1:45 am Post subject: |
|
|
Acolyte
Joined: 19 Mar 2002 Posts: 68 Location: Capelle aan den IJssel (Rotterdam)
|
Yes..... could someone please explain this ???
Remco |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Mar 26, 2004 4:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Well, why should the system write a persistant message to the log file if there is an application with the queue open for reading?
That is, if the message shows up on a queue and is about to be consumed... then why delay how long it takes for the message to get consumed? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Frank Nellion |
Posted: Fri Mar 26, 2004 4:31 am Post subject: |
|
|
 Newbie
Joined: 29 Jan 2004 Posts: 5 Location: UK
|
I am getting confused now - I thought the whole point of Persistant messages being put to the MQ log was so you could, if needs be, track and identify on behalf of the Application where they have been, and if they fail (or not get delivered on time) for some unknown reason then you can identify where and why. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Mar 26, 2004 4:37 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Frank Nellion wrote: |
I am getting confused now - I thought the whole point of Persistant messages being put to the MQ log was so you could, if needs be, track and identify on behalf of the Application where they have been, and if they fail (or not get delivered on time) for some unknown reason then you can identify where and why. |
No. The logs are transaction logs, designed to ensure that the message can get delivered to the queue storage file.
They're not history logs (transaction history or otherwise), nor are they system event logs- at least as I understand it. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
JasonE |
Posted: Fri Mar 26, 2004 4:44 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Every disk i/o hits performance. MQ write to the logs and queue files the minimum it has to in order to be able to guarantee that after a failure, no committed persistent messages are lost. As to how it does this - its magic (ok - extremely complex!), and changes over time as more subtle optimizations arise. |
|
Back to top |
|
 |
Frank Nellion |
Posted: Fri Mar 26, 2004 4:45 am Post subject: |
|
|
 Newbie
Joined: 29 Jan 2004 Posts: 5 Location: UK
|
Jeff, I understand that they are not "actually" history logs in that sense, but as each message is date/time stamped, and if my code can handle that, surely I can store this somewhere and then manipulate the data to create a "history" file of my own, and if needs be model, simulate and compare? |
|
Back to top |
|
 |
|