Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Forums Home > Identity Management Forums > Identity Lifecycle Manager > MA Sequencer hang while thread executed complete
Ask a questionAsk a question
Search Forums:
 

AnswerMA Sequencer hang while thread executed complete

  • Thursday, October 29, 2009 9:43 AMcortex93 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi all,

    I'm using the MA Sequencer from ResKit. From times to times, it continues to run doing nothing (0% cpu) while in the log it says Threads have completed the execution, all MAs are in an idle state and MA history report that everything goes well.
    As the log file is locked, the next call to the sequencer will not function and the whole process is then stuck...

    Does any one had this same issue ?
     

Answers

  • Monday, November 02, 2009 10:16 PMPaul LoonenMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    not really. Is it possible that some other process is locking your log file? Also, I will presume that you are running the MASequencer through the Windows scheduler. You do have the option to end a process if it is running longer than a certain time, which might solve your problem.
    Paul Loonen (Avanade)
     

All Replies

  • Monday, November 02, 2009 10:16 PMPaul LoonenMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    not really. Is it possible that some other process is locking your log file? Also, I will presume that you are running the MASequencer through the Windows scheduler. You do have the option to end a process if it is running longer than a certain time, which might solve your problem.
    Paul Loonen (Avanade)
     
  • Tuesday, November 03, 2009 7:46 AMcortex93 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    The sequencer is run as part of a sql job. I checked with process explorer and the file is opened only by the sequencer. I just have to kill his process and everything returns to normal.
    I have two job, one which run at midnight with full import and synchro. And another one, which runs each 15 minutes from 8am to 19pm on a delta basis. Sql job guarantee that the same job cannot run twice at the same time, and I have configured the sequencer to log to a different file for each job.
    The fact is that after the sequencer step in full job, there is some steps that need to be run, to prepare the delta job.

    Thanks for your feedback, I'll search around when it happens again.

    Is there any more verbose mode on the sequencer ?