o Juha Heinanen on 12/13/2011 03:39 PM:
i made mysql.connect() fail because of wrong arguments. i then try to
catch the exception, but so far no luck. i have tried
transition "mysql error" (start,session_started) - test($errno!="") / log(1, MySQL
connection error); stop(true) -> end;
and
transition "mysql error" (start,session_started) - exception / log(1, MySQL
connection error); stop(true) -> end;
but in both case i get to syslog:
Dec 13 16:37:20 sip sems[31556]: [#b51a0b70] [processEventsCatchExceptions,
AmSession.cpp:392] ERROR: 500 unexpected exception.
document dsm_errorhandling.txt also shows throwOnError(); calls, but
according to Readme.mod_mysql.txt, mysql calls do not throw exceptions,
but just set error variables.
can you please run it in gdb or somehow else try to see what kind of
exception is thrown and where? you might even find it in the log.
mysql.connect catches mysqlpp::ConnectionFailed and
mysqlpp::Exception, and in my mysql++ mysqlpp::Exception is the base
class for all other exceptions. could it be that this exceptions is
thrown somewhere else?
Stefan
-- juha
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
--
tel:+491621366449
sip:[email protected]
mailto/xmpp:[email protected]
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
