Happened all of the time for us at 4.2.0.
PQ62760 probably explains your problem: "The expiration process may fail to
end in a timely manner
when the duration parameter threshold is reached or a
cancel is manually issued"

Not sure what level this is first fixed at but it is included in 5.1.6.1
(which we just upgraded to!).

Tim Rushforth
City of Winnipeg

-----Original Message-----
From: Michael Raine [mailto:Michael.Raine AT ALLFIRST DOT COM]
Sent: Tuesday, March 18, 2003 9:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Duration timeout during Expiration


Hello All,


I currently have a duration limit set while running expiration.
Occasionally
while the processes is running the limit is ignored or not rezognized and
expiration continues over the assigned specified time limit (currently set
for 4
hours and the last expiration process ran for 9 hours).

This causes migration processes that are scheduled after the expiration is
scheduled to finish to fail with lock failures.

Has anyone else experienced this problems

Thanks