@yajnasteju

You should try adding a try/catch in side the callback function (onRefresh, onUpdate, etc.) and see if it catch the exception.

The log suggests that the exception was thrown in EMA dispatching thread. This could means the exception was thrown in callback function.

@Warat B. Hi, I encountered the same problem and now added try/catch in the callback function body.

One more question, is there anyway application can detect some core thread in ema sdk still alive ? If accidental events that try/catch still not works occur cause these core threads crash but my other threads still live, I expect to catch such message to take my own action, for example try to exit the whole application to make it reboot and register rics again ? Many thanks, expecting your reply.

@wangfugen

It looks like you want to catch unhandled exception yourself, correct?

There is a parameter named "CatchUnhandledException" you can set in the Ema Configuration file. If you set it to 0 (default is 1) the EMA passes unhandled exceptions to the operating system. In this case, I think the application layer can catch such an error to take your own action.

Please find the details of the parameter from Ema CPP Configuration Guide (EMACPP_ConfigGuide.pdf) section 3.1.4 (based on ESDK1.3.0.L1 package)

@moragodkrit Thanks for your replay. According to your advice,

First I should modify EmaConfig.xml to add two following consumer entries, right?

Second, if ema passes unhandled exception to the operation sysstem, How can I catch it or just let the operating system handle it , maybe crash my application?

If I try in my main() function like this:

int main(){
    try{
        AppClient client; 
        // put all register RIC code here
    } catch(const emaaccess::OmmException& excp)
    {
        // Will UnhandledException runs here ?
    }
}

Can my application catch the exception via OmmException ? Thanks