Lars@Addicticks

@chavalit.jintamalit

Issue Resolved. In the event queue, first of all I am receiving STATUS_RESP message event, so in the example code they are closing the request. When I commented this.closeRequest(); It is processing the next events Now I am getting my data.

if (respMsg.getMsgType() == OMMMsg.MsgType.STATUS_RESP)
{
// If receive STATUS_RESP, display the message and close the request
GenericOMMParser.parse(respMsg);
this.closeRequest();
}

Yeah, well. The SDK examples show you to fire off item requests before just about anything is ready. As everything in the API is asynchronous it means you can do things in (almost) any order, but it doesn't mean you should. Just my two cents.

In other words I suggest to wait for the directory response before you start firing off item requests. Otherwise you may for a short while see this message. The API doesn't yet know if the service is really up or down.

Another reason may be that TREP has lost upstream connectivity to the source app for IDN_RDF. But I'm leaning towards my first explanation. :-)

Lars

Addicticks

On another note I'm thinking that you may also get some help by comparing your own results to that of TRexplorer.

TRexplorer is also based on RFA Java.

Step 1: Make sure Output Window is visible.

Step 2: When configuring your connection make sure message tracing is enabled.

Step 3: Connect

Step 4: Have a look in the Output window. You'll see all messages exchanged.

Now compare this with your own development. The answer is in the difference.

You already confirmed that you received all the event.

So I think the session was not ready when you tried to put the item request.

        // 4. Acquire a Session
        _session = Session.acquire( "myNamespace::consSession" );
        if ( _session == null )
        {
            System.out.println( "Could not acquire session." );
            Context.uninitialize();
            System.exit(1);
        }

	Thread.sleep(5000);  // << wait for the session to be ready

        // 5. Create an OMMConsumer event source
        _consumer = (OMMConsumer) _session.createEventSource(EventSource.OMM_CONSUMER, "myOMMConsumer", true);

If you add waiting period for it like the sample code above, you should not get the information message.

Hello @applicationdevelopment

This error can happen when the application makes an item request to a service that is not available (i.e. service down, or non-existing service),RFA will immediately respond with Open-Suspect status with the status text shown above.

To fix this problem, please contact

- your Thomson Reuters Account team if you connect to Thomson Reuters Server

or

-your server's admin if you connect to your company server.

to confirm if IDN_RDF is a correct service name and it is still up.