On 7/2/08 10:03 AM, "Pete Aven" <[EMAIL PROTECTED]> wrote: > Try running xdmp:document-properties() on the document to check its > current state; if it's 'active', then it is still being processed by > something. > > You might also want to check the Task Server status and your App Server > status in the Admin UI to see if anything has been running for awhile.
Pete, Thanks for the tips, particularly checking the Task Server/App Server status in the admin. I saw a bunch of old requests in the App Server that varied in length from 2 hours to 24 hours, which are almost certainly my attempts to access this file. I also think I have the root problem figured out. I'd been working on a query that would both update some documents on the server, and then copy/archive them elsewhere. When I combined the update/copy actions into a single script, that's when I started seeing this behavior. I'll be taking the Grouch Marx approach and "Not Doing That" anymore. The only other question I'd have here (for anyone) would be, is there a way to kill those old requests that are hanging around the server (short of a reboot)? I've tried clicking the [cancel] link/button for all of them, but they're pretty insistent on sticking around. Pete, thanks again for your help! -- Alan Storm [EMAIL PROTECTED] Rubicon International _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
