TREP API: [CIRCULAR REFERENCE:com.reuters.rfa.common.DeactivatedException]

Thank you @josa,

You are on the latest RFA Java.

This is the application log, not RFA trace?

Can you enable low level trace log in your application and upload the resultant trace?

This can be done by setting the ipcTraceFlags to 7 in your connection parameters as well as setting mountTrace=true

This should result in a log file with a default name of RFA_RSSL*.log or RFA_SSL*.log depending on your connection type.

For further details on the above and related parameters please refer to the RFAJ_ConfigLoggingGuide.pdf which comes with the RFAJ API package.

If the file is large, please zip before uploading.

Will try to learn more.

---

If you are seeing the above exception on uninitialization/shutdowm, review your unitialization code for consistency, if it is threaded, make sure that unitialization is consistent for all threads.

Hi @josa,

I have taken a look at the code you have shared. I do not see anything wrong. I do not see deactivate or unregister called. I know it's in diiferent part of your app.

My line of thought is that if the order of uninitialization, at some point, is not observed, it may result in teh exception you are seeing. Roughly, it is as demonstrated in our consumer examples:

if ( _connIntSpecHandle != null )
        _ommConsumer.unregisterClient(_connIntSpecHandle);


        // unregister all items
        if (_itemManager != null)
            _itemManager.closeRequest();


        // unregister login
        // Allow conditional login unregister.
        // loginCleanup flag is set to false if cleanup is called after login
        // failure.
        if (_loginClient != null && doLoginCleanup)
            _loginClient.closeRequest();


        if (_ommConsumer != null)
            _ommConsumer.destroy();


        _eventQueue.deactivate();
        _session.release();
        Context.uninitialize();

If you are running this from multiple threads, two approaches to find the issue, to me, are:

• Put breakpoints before the key steps indicated above->debug->step-by-step try to see if you dispatch after deactivation, or any other unexpected behavior is happening
• Put print statements before key points and try to detect "out-of-ordering" this way

If you need more help, and if you/your organization is a TRDC member, open a TRDC ticket, and have our experts look at the complete code.

Hello @josa,

I would put a logging statement as the very first line of cleanup method, and carefully examine the output, to make sure your application only calls it once.

In the trace, that I find attached, MarketPrice for CLH9 is returned to the consumer:

-> login request
<- login accpet
-> directory request
<- directory IFC, ELEKTRON_DD
-> request MarketPrice CLH9, non-streaming
<- refresh MarketPrice CLH9 ***
-> Close request MarketPrice
-> Close request Login   

But it seems that you are saying that nothing is returned?

Does the trace attached before correspond to the run when you get "DeactivatedException"?

--------

Deactivated exception, happens when the application tries to access a deactivated queue. For example, cleanup was run already ( from one request) and then you try to run cleanup again (from another request, usually on a different thread). This is the reasoning for my suggestions above on how to approach debugging.

--------

Yes, it is possible that a consumer will run differently on connecting to a different system. If the timing is different, an issue in the consumer code can be masked on one and exhibit prominently on the other.

--------

If you get nothing with third party account(?) and not the refresh that I see in trace, I would test third party account with a standard client. For example, StarterConsumer that came with RFA Java SDK. Make sure you get a response for the RIC you request. Then move on to the custom consumer testing.

I will take a look.

To clarify what I am reviewing:

Is this trace with "third party account" + Deactivated exception?

Have a you had a chance to test "third party account" + StarterConsumer from SDK?

Thanks

Thanks, this should help

To clarify:

When you run the client you have developer with reuters test account, you get back the data and see no issues?

When you run the client you have developed with third party client account you get no data and get Deactivated exception?

In your last attached trace:

MarketPrice Batch View request for 6 items:

"CLH9" "HOU8" "IBM.N" "JPY=" "MSFT.OQ" "TRI.N"

view: "BID" and "ASK"

I see refresh responses for CLH9 and HOU8, and no refresh responses for the rest. The there is close requests for all 6 MP streams and login close.

Are you seeing and paring these refresh responses?

Does Deactivation exception happen after that?

Please confirm the client account you use to consume is permissioned for the rest of the instruments and should be receiving them, do you register for and parse "not entitled" status?

Any feedback after checking the result?