<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Afternoon all,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We are experimenting with live synch in a clustered deployment and have come across some situations where it experiences a fatal error and moves to a suspended state. The most recent error we received was the following after container reboot: <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>GUI Results:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=746 height=583 style='width:7.7708in;height:6.0729in' id="Picture_x0020_1" src="cid:image001.png@01D8D7F5.CE36B200"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Operation: com.evolveum.midpoint.repo.common.activity.run.LocalActivityRun.runLocally<o:p></o:p></p><p class=MsoNormal>Status: FATAL_ERROR<o:p></o:p></p><p class=MsoNormal>Message: <o:p></o:p></p><p class=MsoNormal>Bucket PCV(4531):[PP({.../common/common-3}sequentialNumber):[PPV(Integer:1)], PP({.../common/common-3}state):[PPV(WorkBucketStateType:COMPLETE)], PP({.../common/common-3}content):[PPV(NullWorkBucketContentType:com.evolveum.midpoint.xml.ns._public.common.common_3.NullWorkBucketContentType@6e57bf8b[])]] is not ready<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have also attached the stack trace from the logs. Is it possible to configure Midpoint to continue subsequent runs after permanent errors? Additionally, have others experienced similar behavior?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Jeremiah Haywood<o:p></o:p></p><p class=MsoNormal>Lead IAM Administrator<o:p></o:p></p><p class=MsoNormal>Office of Technology Solutions | Illinois State University<o:p></o:p></p><p class=MsoNormal>Phone Number (309) 438-3829<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>