<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">
<!--
p
{margin-top:0;
margin-bottom:0}
p
{margin-top:0;
margin-bottom:0}
p
{margin-top:0;
margin-bottom:0}
-->
</style>
</head>
<body>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Hi,<br>
<br>
Can someone help me on this? Sample simulation is attached herewith.<br>
<br>
Thanks and regards,<br>
Shashank<br>
<div style="font-family:Times New Roman; color:#000000; font-size:16px">
<hr tabindex="-1">
<div id="divRpF791968" style="direction:ltr"><font size="2" color="#000000" face="Tahoma"><b>From:</b> Lothe Shashank<br>
<b>Sent:</b> Friday, October 11, 2013 1:20 PM<br>
<b>To:</b> rabbitmq-discuss@lists.rabbitmq.com<br>
<b>Subject:</b> Re: [rabbitmq-discuss] Rabbitmq-C amqp_basic_publish crash on connection loss<br>
</font><br>
</div>
<div></div>
<div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Hi Alan,<br>
<br>
Thanks for the clarification. I am attaching the simulation herewith. I don't have a stack trace. It was abort as I couldn't get the next console print. On similar lines, for a listner, if I stop rabbitmq broker using rabbitmq_ctl stop_app, amqp_maybe_release_buffers(conn)
API crashed. I believe that due to abrupt connection loss the conn value becomes invalid (though not changed) and amqp_basic_publish and amqp_maybe_release_buffers APIs fail.<br>
<br>
Could you throw some light on this and help me to understand how can I handle abrupt connection loss during publish and listen?<br>
<br>
Thanks and regards,<br>
Shashank<br>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
<br>
<hr>
<font face="Arial" color="Navy" size="2"><br>
DISCLAIMER:<br>
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or
all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.<br>
</font>
</body>
</html>