question

Upvotes
Accepted
18 0 0 4

EMA:dictionary retrieval failed (timed out after waiting 45000 milliseconds) for 192.168.1.133:14002)

loggerMsg

ClientName: EmaConsumer_15

Severity: Error

Text: dictionary retrieval failed (timed out after waiting 45000 milliseconds) for 192.168.1.133:14002)

loggerMsgEnd

three question:

one:Why does this happen?

two:How do I catch this exception error?

three:How to handle this error? (Code examples would be great)

service-dictionary
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

· Write an Answer
Upvotes
Accepted
73k 226 49 71

@zhangqingfeng

It is a dictionary request timeout, as mentioned on this thread. You may need to check the error in the LPC log file.

This error is thrown in the OmmInvalidUsageException with the OmmInvalidUsageException.ErrorCode.DICTIONARY_REQUEST_TIME_OUT error code. You can catch this exception in the code.

1658129682191.png

To handle it, you need to create a new consumer. Otherwise, you can load dictionary from the local files instead.

<Dictionary>
            <Name value="Dictionary_2"/>
            <DictionaryType value="DictionaryType::FileDictionary"/>
            <!-- dictionary names are optional: defaulted to RDMFieldDictionary and enumtype.def -->
            <RdmFieldDictionaryFileName value="./RDMFieldDictionary"/>
            <EnumTypeDefFileName value="./enumtype.def"/>
        </Dictionary>

1658129682191.png (23.2 KiB)
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.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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