[MarkLogic Dev General] Timeout in a CPF pipeline?

[Danny Sokolsky]

And one other thing I recently found out, Florent:

As of 4.1-4, XDMP-EXTIME is a caught exception.  So if you are running 4.1-4 or later, it should just work.

-Danny

-----Original Message-----
From: general-bounces at developer.marklogic.com [mailto:general-bounces at developer.marklogic.com] On Behalf Of Geert Josten
Sent: Wednesday, March 24, 2010 2:40 PM
To: General Mark Logic Developer Discussion
Subject: RE: [MarkLogic Dev General] Timeout in a CPF pipeline?

Hi Florent,

If you wrap your code in an xdmp:eval, you can set a time-limit that is smaller than the default task limit. That should result the doc being given the error state. You could also wrap the eval in a try-catch to do some additional work before rethrowing the error..

Kind regards,
Geert

>


drs. G.P.H. (Geert) Josten
Consultant


Daidalos BV
Hoekeindsehof 1-4
2665 JZ Bleiswijk

T +31 (0)10 850 1200
F +31 (0)10 850 1199

mailto:geert.josten at daidalos.nl
http://www.daidalos.nl/

KvK 27164984

P Please consider the environment before printing this mail.
De informatie - verzonden in of met dit e-mailbericht - is afkomstig van Daidalos 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.

> From: general-bounces at developer.marklogic.com
> [mailto:general-bounces at developer.marklogic.com] On Behalf Of
> Florent Georges
> Sent: woensdag 24 maart 2010 22:34
> To: General Mark Logic Developer Discussion
> Subject: Re: [MarkLogic Dev General] Timeout in a CPF pipeline?
>
> Danny Sokolsky wrote:
>
>   Thanks for your fast response!
>
> > Ah, I see the problem now.  The timeout exception is not caught, so
> > the document never enters the error state, nor does it
> advance to the
> > next state (because it is not successful).
>
>   Exactly...
>
> > This is a tricky situation.  I can think of a few things to
> counteract
> > it.
>
>   Yes, this is quite a corner case, but we did run into such
> a problem a few days ago and we found it only by chance (if I
> understood correctly, I don't have the full story).
>
>   A nice solution would have been to be able to, say, send an
> email or any kind of alert for manual inspection, i.e to be
> notified in some way.  Maybe a batch on the error log could
> achieve that.
>
>   At least that confirm what I thought.  Thanks again,
>
> --
> Florent Georges
> http://www.fgeorges.org/
>
>
>
>
> _______________________________________________
> General mailing list
> General at developer.marklogic.com
> http://xqzone.com/mailman/listinfo/general
>
_______________________________________________
General mailing list
General at developer.marklogic.com
http://xqzone.com/mailman/listinfo/general