Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

A way to intercept REBOL/Command crash

 [1/3] from: coussement::c::itc::mil::be at: 24-Jan-2001 14:50

Hi REBOLians, I need bady a solution to the following problem: For the system I made, which is transaction-intensive, the REBOL file-server crashes under particuliar conditions. In order to prevent it I would like to find a generic solution to intercept the exception which causes the crash, so the processes could go further after a exception report. Does anybody know any use of catch/throw-on-error which placed on a strategic place in the script could help me out of this ? Can throw-on-error prevent a process to be killed by an -unidentified- exception ? Because the crash conditions have not already been clearly identified, I'm not yet in state of giving more details about it. Best Regards, chr==

 [2/3] from: ptretter:norcom2000 at: 24-Jan-2001 8:39

You should use the functions 'try and 'disarm. After disarming and error you can continue to operate in most cases. if error? error-open-port: try [open port][error-open-port: disarm error-open-port] I hope that helps. Also you may want to check out the errors chapter of the Core.pdf appendix B pages B3-B5. Paul Tretter ----- Original Message ----- From: "CRS - Psy Sel/SPO, COUSSEMENT Christophe, CPN" <[COUSSEMENT--C--ITC--mil--be]>

 [3/3] from: coussement:c:itc:mil:be at: 24-Jan-2001 16:00

Thanks : I already did use this on most functions, but not to check the port opening. I try it directly ! CU, chr==