question

Upvotes
3 0 0 1

EMA:Call to rsslReactorDispatchLoop() failed. The _state is set to OmmImplState.NOT_INITIALIZED

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)

consumer
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvote
53k 137 44 63

@zhangqingfeng

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


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

@zhangqingfeng is the issue still outstanding?

If so, are you able to provide the information requested by Jirapongse?

Thanks.