<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>
<!-- Template generated by Exclaimer Mail Disclaimers on 04:14:17 Dienstag, 29 Mai 2012 -->
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">P.a1d10a9a-8fc5-4a21-a03e-34c3b99affb0 {
MARGIN: 0cm 0cm 0pt
}
LI.a1d10a9a-8fc5-4a21-a03e-34c3b99affb0 {
MARGIN: 0cm 0cm 0pt
}
DIV.a1d10a9a-8fc5-4a21-a03e-34c3b99affb0 {
MARGIN: 0cm 0cm 0pt
}
TABLE.a1d10a9a-8fc5-4a21-a03e-34c3b99affb0Table {
MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
page: Section1
}
</style>
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1747997612;
mso-list-type:hybrid;
mso-list-template-ids:218954026 67567631 67567641 67567643 67567631 67567641 67567643 67567631 67567641 67567643;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="DE" link="blue" vlink="purple">
<p class="a1d10a9a-8fc5-4a21-a03e-34c3b99affb0"></p>
<div class="WordSection1">
<p class="MsoNormal">Hi there,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">we have here a corosync/pacemaker cluster running tomcat. Sometimes our application running inside tomcat fails and tomcat dies.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">This – for some reason I don’t understand – leads to an “unmanaged failed” state for tomcat diplayed in crm_mon. This would not been to bad, but at this point the cluster “decides” not to failover the resource to the
second node.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">My questions:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">Is this a standard behaviour? Should a failover stop (or not take place at all), if a resource runs into an unmanaged failed state?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">What conditions have to apply, before a resource is called “unmanaged failed”?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><![if !supportLists]><span lang="EN-US"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span lang="EN-US">Is there any way of an “automatic recover” of a resource that ran into an “unmanaged failed” state?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Andreas<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial","sans-serif";color:gray;mso-fareast-language:DE">--<br>
CONET Solutions GmbH<br>
Andreas Stallmann, <br>
Theodor-Heuss-Allee 19, 53773 Hennef<br>
Tel.: +49 2242 939-677, Fax: +49 2242 939-393<br>
Mobil: +49 172 2455051<br>
Internet: http://www.conet.de, mailto: </span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:gray;mso-fareast-language:DE"><a href="mailto:AStallmann@CONET.DE"><span lang="EN-US" style="color:blue">AStallmann@CONET.DE</span></a></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:gray;mso-fareast-language:DE">
</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p></p>
<p class="a1d10a9a-8fc5-4a21-a03e-34c3b99affb0"> </p>
<p class="a1d10a9a-8fc5-4a21-a03e-34c3b99affb0">----------------------------<br>
CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.<br>
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136)<br>
Geschäftsführer/Managing Director: Anke Höfer </p>
<p class="a1d10a9a-8fc5-4a21-a03e-34c3b99affb0"> ----------------------------</p>
<p class="a1d10a9a-8fc5-4a21-a03e-34c3b99affb0"> </p>
<p class="a1d10a9a-8fc5-4a21-a03e-34c3b99affb0"></p>
</body>
</html>