loggerMsg
ClientName: EmaConsumer_9
Severity: Error
Text: Call to rsslReactorDispatchLoop() failed. The _state is set to OmmImplState.NOT_INITIALIZED
loggerMsgEnd
This error occurs when I call OmmConsumer's uninitialize()
one:Why does this happen?
two:How do I catch this exception error?
three:How to handle this error? (Code examples would be great)
We did not hear back from you yet- if your question was answered outside of these forums, we would appreciate a brief update, that would enable other developers with same or similar questions be helped on their way to a solution.
-AHS
hi @zhangqingfeng ,
I'm afraid we haven't heard from you in a while and we cannot provide further assistance without the details asked for. I'm closing this thread. If you need any further assistance, please start a new thread or if the question was answered outside of these forums, we would appreciate a brief update that would help other developers who are facing a similar question on their way to a solution.
Thanks,
AHS
It looks like a race condition. I assume that when calling the OmmConsumer's uninitialize() method, the API set the state of the channel to NOT_INITIALIZED. However, the API still called the rsslReactorDispatchLoop() method to dispatch events of the NOT_INITIALIZED channel which can trigger that error.
However, I am unable to replicate the issue. To verify the problem, please provide the following information.
1. The version of EMA Java used by the application
2. The snippet code that shows how the application uses EMA
3. The EMA configuration file
If so, are you able to provide the information requested by Jirapongse?
Thanks.
