Hi Mike,

I think lock contention is not involved. I don't have any directories (no
auto create, no last-modified, none manually created). (Doc and frag count
is equal, so clearly no properties either, just to save some space.)

It is a bit of a guess, but I think multiple threads are processing a set
of files, and it can have overlap. And say, thread 1 writes A and B, but
thread 2 writes B first and A second, they could end up waiting for each
other.

But it also seems to be occurring with just one thread now and then, which
is (supposed to) not do(ing) any spawning, invoking, evaluating
whatsoever. It could also just be one of the many http-gets taking way too
long to end (despite a timeout)..

I'm going to rewrite a relevant part anyhow, so let's see whether this
still occurs after this. I'll definitely try your suggestions in that
case, thnx!

Kind regards,
Geert

> -----Oorspronkelijk bericht-----
> Van: [email protected] [mailto:general-
> [email protected]] Namens Michael Blakeley
> Verzonden: zaterdag 11 februari 2012 19:02
> Aan: MarkLogic Developer Discussion
> Onderwerp: Re: [MarkLogic Dev General] Stack button on Task Server
Status
> screen of Admin
>
> Do you think it's a server internal deadlock or could it be lock
contention
> between concurrent requests?
>
> If it might be coming from your query, set the group file-log-level to
DEBUG.
> Then monitor the log to see if there are debug-level XDMP-DEADLOCK
> messages. If you see those, but aren't sure why your code would create
> deadlocks, you might also find it useful to add xdmp:log messages before
each
> update call. An xdmp:query-trace(true()) at the top of your code might
help too.
>
> -- Mike
>
> On 11 Feb 2012, at 09:52 , Geert Josten wrote:
>
> > Ah, that also explains why I wasn't seeing anything appear. I have
some
> > long running threads that doesn't seem to return. I am suspecting a
> > dead-lock of some kind.. :(
> >
> > Thnx,
> > Geert
> >
> >> -----Oorspronkelijk bericht-----
> >> Van: [email protected] [mailto:general-
> >> [email protected]] Namens Michael Blakeley
> >> Verzonden: zaterdag 11 februari 2012 18:41
> >> Aan: MarkLogic Developer Discussion
> >> Onderwerp: Re: [MarkLogic Dev General] Stack button on Task Server
> > Status
> >> screen of Admin
> >>
> >> The '[stack]' feature uses the debug API to attach to the request,
get
> > the request
> >> stack, detach, and render the stack as an HTML page. This is
sometimes
> > useful
> >> when you are looking at a long-lived request and wondering what it is
> > doing.
> >>
> >> The debug API needs to have enough time to do its work on the
request,
> > so this
> >> works best if the request is long-lived. With short-lived requests
> > you'll probably
> >> just see a "request not found" message. It also works best when
> > evaluating in-
> >> memory XQuery expressions. If the request happens to be in a function
> > call or
> >> XPath expression that requires a database lookup, the debug request
will
> > block
> >> until that database lookup comes back.
> >>
> >> -- Mike
> >>
> >> On 11 Feb 2012, at 01:36 , Geert Josten wrote:
> >>
> >>> If you go to a Task Server Status screen, and hit the Show More
> > button, it
> >>> shows a list of all currently running threads. Behind there is a
> > [cancel]
> >>> button, but also a [stack] button. What is it supposed to do?
> >>>
> >>> Kind regards,
> >>> Geert
> >>>
> >>> drs. G.P.H. (Geert) Josten
> >>> Senior Developer
> >>>
> >>>
> >>>
> >>> Dayon B.V.
> >>> Delftechpark 37b
> >>> 2628 XJ Delft
> >>>
> >>> T +31 (0)88 26 82 570
> >>>
> >>> [email protected]
> >>> www.dayon.nl
> >>>
> >>> De informatie - verzonden in of met dit e-mailbericht - is afkomstig
> > van
> >>> Dayon BV en is uitsluitend bestemd voor de geadresseerde. Indien u
dit
> >>> bericht onbedoeld hebt ontvangen, verzoeken wij u het te
verwijderen.
> > Aan
> >>> dit bericht kunnen geen rechten worden ontleend.
> >>> _______________________________________________
> >>> General mailing list
> >>> [email protected]
> >>> http://developer.marklogic.com/mailman/listinfo/general
> >>>
> >>
> >> _______________________________________________
> >> General mailing list
> >> [email protected]
> >> http://developer.marklogic.com/mailman/listinfo/general
> > _______________________________________________
> > General mailing list
> > [email protected]
> > http://developer.marklogic.com/mailman/listinfo/general
> >
>
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to