Bugs item #2636813, was opened at 2009-02-25 15:51 Message generated for change (Comment added) made by shcheklein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2636813&group_id=129076
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: Sedna (current) >Status: Closed >Resolution: Duplicate Priority: 9 Private: No Submitted By: Dmitry A. Shaporenkov (dsha) Assigned to: Nobody/Anonymous (nobody) Summary: Sedna Processes and Reliability Initial Comment: There are currently (build 3.1.175) multiple issues with regard to Senda reliability as a server-side DBMS. My OS is Windows Server 2003. 1) se_trn.exe process may crash because of (say) infinite recursion in XQuery (apparently causing stack overflow), invalid characters and so on. When a crash happens, the system dialog shows up prompting to debug the process. Suggestion: Add something like top-level exception handler to se_trn.exe code, so that even if fatal exception occurs, the process still finishes gracefully with appropriate diagnostic information. On Windows, the event log is a good place where to submit diagnostic information. 2) Under no condition should a crash in se_trn.exe take down the whole Sedna governor process, se_gov.exe, with all the databases it governs and all other se_trn.exe processes executing clients' queries. It's an absolute shame that this still happens at the moment of writing. This behavior is absolutely unacceptable for any server-side system. After all, process isolation is all about security and reliability, and here we observe the opposite picture. Suggestion: se_gov.exe should survive and databases continue to run regardless what happens to any of se_trn.exe process. ---------------------------------------------------------------------- >Comment By: Ivan Shcheklein (shcheklein) Date: 2009-02-26 12:52 Message: Dmitry, thank you for this bug report and your valuable suggestions! 1) Independent bug report has been added: see PR/2640943 ( https://sourceforge.net/tracker2/?func=detail&aid=2640943&group_id=129076&atid=713730 ) 2) This a well known shortcoming of the current Sedna's architecture. I suppose this can't be considered as a bug. However, it has been accepted as a feature request :). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2636813&group_id=129076 ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Sedna-discussion mailing list Sedna-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sedna-discussion
