In fact, now that I look for it, that’s already happening in my code, I just 
didn’t realize it. So problem solved.

Cheers,

E.
--
Eliot Kimber
http://contrext.com


On 10/7/17, 8:18 AM, "[email protected] on behalf of 
Eliot Kimber" <[email protected] on behalf of 
[email protected]> wrote:

    I can certainly experiment with that.
    
    Cheers,
    
    E.
    --
    Eliot Kimber
    http://contrext.com
     
    
    
    On 10/7/17, 7:41 AM, "[email protected] on behalf of 
Geert Josten" <[email protected] on behalf of 
[email protected]> wrote:
    
        Hi Eliot,
        
        I heard the other day that it should be possible to capture such 
timeouts
        with a try catch within the code itself. That gives an extra 10 seconds
        delay which might be sufficient to send out an alert email, or raise 
some
        other flag. After those few extra seconds, the timeout gets rethrown if
        you don¹t finish in time..
        
        Might be worth investigating?
        
        Cheers,
        Geert
        
        On 10/7/17, 12:10 AM, "[email protected] on behalf
        of Eliot Kimber" <[email protected] on behalf of
        [email protected]> wrote:
        
        >Using current ML 9:
        >
        >I¹ve set up a little client-server application where the client spawns 
a
        >large number of tasks on a remote cluster. Each remote task reports its
        >status back to the client via HTTP.
        >
        >However, if one of the tasks times out in the Task Server there¹s no 
way
        >for it to report its own failure and there doesn¹t seem to be anything
        >else other than the task server that can detect the failure and report 
it.
        >
        >Is there any built-in mechanism by which a task time limit exceeded
        >failure can be detected in a way that would allow me to the report back
        >to the calling client? For example, something that gets the task¹s
        >current call stack at the time of failure, which would give me the 
info I
        >need to report back to the calling client.
        >
        >Unfortunately, the code I¹m running in these tasks is pre-existing
        >processing that I¹m building this remote processing around so I can¹t
        >easily do something like provide a heartbeat signal for each running 
task
        >that a separate process could poll in order to detect terminated
        >processes, although I¹m guessing that¹s the most likely solution now 
that
        >I think about it.
        >
        >I do report to the client when each task starts so I guess I could
        >presume that if a task hasn¹t finished some time after the configured 
max
        >time limit that it is presumed to have failed.
        >
        >Thanks,
        >
        >Eliot  
        >--
        >Eliot Kimber
        >http://contrext.com
        > 
        >
        >
        >
        >_______________________________________________
        >General mailing list
        >[email protected]
        >Manage your subscription at:
        >http://developer.marklogic.com/mailman/listinfo/general
        
        _______________________________________________
        General mailing list
        [email protected]
        Manage your subscription at: 
        http://developer.marklogic.com/mailman/listinfo/general
        
    
    
    _______________________________________________
    General mailing list
    [email protected]
    Manage your subscription at: 
    http://developer.marklogic.com/mailman/listinfo/general
    





_______________________________________________
General mailing list
[email protected]
Manage your subscription at: 
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to