<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 21, 2016, at 6:37 AM, Tomek <<a href="mailto:tomek.w.gran.chaco@gmail.com" class="">tomek.w.gran.chaco@gmail.com</a>> wrote:</div><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><div class=""><div class=""><span class=""><div class=""><br class=""></div></span><div class="">How large is the core? How long does it take to reach this end?</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">There are two cores for last three days:</div><div class=""><div class="">-rw------- 1 root root 10272768 Jan 19 11:02 core-tao_cosnotifica-11-50-51-11986-1453201332</div><div class="">-rw------- 1 root root 28766208 Jan 19 11:48 core-tao_cosnotifica-11-50-51-1719-1453204100</div></div><div class=""><br class=""></div><div class="">Since then tao_cosnotification works stable.</div><div class=""><br class=""></div></div></div></div></div></div></blockquote><div><br class=""></div><div>OK. That looks like roughly 10mb and 28mb, not particularly large. And it looks like they occurred within the same hour. Given that latter fact, can you think of any external events related to the host running the notify service?</div><div><br class=""></div><div>Are these the only crashes you've seen, or are there a history of them?</div><div><br class=""></div><div>The point of failure in your stack is deep in the ORB core, nothing specific to the notify service, and ordinarily just works. It is likely a side-effect of some other problem. What that might be is unknown at this time.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;" class=""><div class=""><div class=""><span class=""><div class=""><br class=""></div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class="">warning: core file may not match specified executable file.</div><div class="">[New LWP 2038]</div><div class="">[New LWP 1719]</div><div class="">[Thread debugging using libthread_db enabled]</div><div class="">Using host libthread_db library "/lib64/libthread_db.so.1".</div><div class="">Core was generated by `/SA/tao/bin/tao_cosnotification -NoNameSvc -IORoutput /SA/data/fp1/ca/tmp/ntfy.'.</div><div class="">Program terminated with signal 11, Segmentation fault.</div><div class="">#0 reset_event_loop_thread (this=0x84f3188) at ../tao/Leader_Follower.inl:128</div><div class="">128 ../tao/Leader_Follower.inl: No such file or directory.</div><div class="">Missing separate debuginfos, use: debuginfo-install ace+tao-6.3.1-1.i686</div><div class="">(gdb) bt full</div><div class="">#0 reset_event_loop_thread (this=0x84f3188) at ../tao/Leader_Follower.inl:128</div><div class=""> <span class="Apple-converted-space"> </span>tss = 0x0</div></div></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div></span><div class="">This means the ORB Core was not able to retrieve thread-specific storage. I don't have an explanation as to why not at this time, this is a very unusual situation.</div><div class=""><br class=""></div><div class="">A common pit fall with the Notify service is the use of defaulted proxies/admins for short-lived suppliers and consumers without destroying the server-side objects when done. In those cases the abandoned objects are effectively leaked, and at some point the notify server hits a resource limit and crashes. Is this something you might be doing?</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">Well, in fact and there may be a sequence of several restarts of consumer in short period of time - but not all such sequences cause tao_cosnotification crash. </div><div class="">I will check this again but I am pretty sure that all resources are released correctly. What in particular should I pay attention to?</div><div class=""><br class=""></div></div></div></div></div></div></blockquote><div><br class=""></div><div>OK. The signature of the pitfall I mentioned is using new_for_consumers() to get an admin and ignoring the id, likewise with the proxy. However for this to be a problem, your core files would be much larger, assuming the core file size reflects the total memory footprint for the process.</div><div><br class=""></div></div>Are you using any QoS options?<div class=""><br class=""></div><div class="">Are you able to use the ORBDebuglevel settings to get some output? As I said above, this is a very unusual situation, so I really don't know what to look for at this point.</div><div class=""><br class=""></div><div class="">-Phil</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div style="font-size: 12.8px;" class=""><div style="margin: 0px; padding: 0px; border: 0px;" class=""><span style="font-family: arial, helvetica, sans-serif; font-size: large;" class="">--</span></div><div style="margin: 0px; padding: 0px; border: 0px;" class=""><span style="font-family: arial, helvetica, sans-serif; font-size: large;" class="">Phil Mesnier</span><br class=""></div></div><div style="font-size: 12.8px;" class=""><div style="font-size: 12.8px;" class=""><font face="arial, helvetica, sans-serif" size="2" class="">Principal Engineer & Partner</font></div><div style="font-size: 12.8px;" class=""><font face="arial, helvetica, sans-serif" class=""><br class=""></font></div><div style="font-size: 12.8px;" class=""><span style="font-family: arial, helvetica, sans-serif;" class=""><font size="2" color="#000000" class="">OCI | WE ARE SOFTWARE ENGINEERS.</font></span></div><div style="font-size: 12.8px;" class=""><span style="font-family: arial, helvetica, sans-serif; font-size: x-small;" class="">tel +1.314.579.0066 x225</span><br class=""></div><div style="font-size: 12.8px;" class=""><a href="http://ociweb.com/" target="_blank" class="">ociweb.com</a></div><div class=""><br class=""></div></div></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></div></body></html>