Hi,

if adding also the SERVICE_INFO_FILTER and content, I get an exception on the consumer EMA while de-serializesthe message: the consumer api tries to notify a null UpdateMsg (DirectoryCallbackClient.cpp::1206).

Would it be possible to have a working example of provider sending Updates on the directory domain?

Thanks

Best Regards,

Paolo

Please find some details below about this new test:

Provider message body:

UpdateMsg msg; msg.domainType(MMT_DIRECTORY).filter(SERVICE_INFO_FILTER | SERVICE_STATE_FILTER). payload(Map(). addKeyUInt(2, MapEntry::AddEnum, FilterList(). add(SERVICE_INFO_ID, FilterEntry::UpdateEnum, ElementList(). addAscii(ENAME_NAME, "DIRECT_FEED"). addArray(ENAME_CAPABILITIES, OmmArray(). addUInt(MMT_MARKET_PRICE). addUInt(MMT_MARKET_BY_PRICE). complete()). addArray(ENAME_DICTIONARYS_USED, OmmArray(). addAscii("RWFFld"). addAscii("RWFEnum"). complete()). complete()). add(SERVICE_STATE_ID, FilterEntry::UpdateEnum, ElementList(). addUInt(ENAME_SVC_STATE, i % 2 ? SERVICE_UP : SERVICE_DOWN). addUInt(ENAME_ACCEPTING_REQS, i % 2 ? SERVICE_YES : SERVICE_NO). complete()). complete()). complete()); provider.submit(msg, 0);

Consumer message received in attachmentEmaTrace.txt

Hi @Paolo Parlapiano,

I have tested the same scenario on ADS. ADS will send Directory response containing empty MapEntry in payload, when there is no available service on ADS. Below is the sample of message.

<refreshMsg domainType="RSSL_DMT_SOURCE" streamId="2" containerType="RSSL_DT_MAP" flags="0x168 (RSSL_RFMF_HAS_MSG_KEY|RSSL_RFMF_SOLICITED|RSSL_RFMF_REFRESH_COMPLETE|RSSL_RFMF_CLEAR_CACHE)" groupId="0" dataState="RSSL_DATA_OK" streamState="RSSL_STREAM_OPEN" code="RSSL_SC_NONE" text=""  dataSize="5">
    <key  flags="0x8 (RSSL_MKF_HAS_FILTER)"  filter="63"/>
    <dataBody>
        <map flags="0x0" countHint="0" keyPrimitiveType="RSSL_DT_UINT" containerType="RSSL_DT_FILTER_LIST" >
        </map>
    </dataBody>
</refreshMsg>

However, when I tried to create the same Directory message, EMA returns invalid usage exception.

    event.getProvider().submit(RefreshMsg().domainType(MMT_DIRECTORY).filter(SERVICE_INFO_FILTER | SERVICE_STATE_FILTER).
        payload(Map().complete()).solicited(true), event.getHandle());

Hi @Paolo Parlapiano

It is possible you may have discovered a bug in the API and I am sure my colleague Veerapath will deal with that scenario accordingly.

However, as side step - I just wanted to understand your required usage scenario. You mention that the availability of service(s) depends on the availability of external sources.

Is this non-availability of external sources typically transient in nature or longer-term/unlikely to change in the (near) future?

I ask because if it is of a transient nature, then perhaps publishing an empty Directory message may not be the best approach - depending on your implementation requirements...

As you may be aware, when populating a Directory message entry for a particular service, you can set the ServiceState and AcceptingRequests elements in the State filter entry work together to indicate the ability of a particular service to provide data:

• ServiceState indicates whether the source of the data is accepting requests.

• AcceptingRequests indicates whether the immediate upstream provider (the provider to which the consumer is directly connected) can accept new requests. If False, new requests are rejected while existing streams remain unaffected (reissue requests can still be made for any item streams that are currently open to the provider).

So, if it is a transient situation, you could set ServiceState:Down and AcceptingRequests:No - in the short term, until such a time as when the external source does become available - at which point you would change these values accordingly (e.g. Up & Yes)

If the non-availability of external sources is longer-term in nature, then it would be more appropriate to publish an empty directory - once the exception issue is resolved.

Hi @Umer Nalla,

thanks for the provided details.
To answer to your question: apart from "long term" misconfigurations of the provider, this non-availability of external sources is a transient condition.
Basically the provider can be also configured at runtime to add services, therefore theoretically I can have the case of startup with no services at all, I just wanted to cover it.
Apart from this, I've also investigated the ServiceState and AcceptingRequests flags that you are referring to, as they could be useful to me anyway.
However, when using them I've experienced another issue. Thinking about a possible misuse of the API, I didn't investigate further, but know I'd like to put here are my findings.

To test the programmatic usage of the ServiceState and AcceptingRequests flags, I've setup a scenario as follows:

• IProvider, handling directory requests for a single service
• Consumer, loading the dictionary from files, and handling directory messages in the application code (dictionary loaded from files so that I could play with the AcceptingRequests flag without causing the OmmConsumer to be unable to be created)

Aim: test my provider and look closer to the directory messages received on consumer side. Result: refresh messages on the Directory domain are correctly received by the consumer, however further updates are not notified.
Note: enabling the log tracing on the consumer (XmlTraceToFile), I can see the updates on the directory domain.

I'm pretty sure that I'm doing something wrong here, perhaps the UpdateMsgs are built incorrectly?
Please find an excerpt of the provider (baseline is IProv331) and an excerpt of the consumer.

Thank you for your help
Best Regards,

Paolo

Provider relevant code

void AppClient::processDirectoryRequest(const ReqMsg&, const OmmProviderEvent& event)
{
	event.getProvider().submit(RefreshMsg().domainType(MMT_DIRECTORY).filter(SERVICE_INFO_FILTER | SERVICE_STATE_FILTER).
		payload(Map().
			addKeyUInt(2, MapEntry::AddEnum, FilterList().
				add(SERVICE_INFO_ID, FilterEntry::SetEnum, ElementList().
					addAscii(ENAME_NAME, "DIRECT_FEED").
					addArray(ENAME_CAPABILITIES, OmmArray().
						addUInt(MMT_MARKET_PRICE).
						addUInt(MMT_MARKET_BY_PRICE).
						complete()).
					addArray(ENAME_DICTIONARYS_USED, OmmArray().
						addAscii("RWFFld").
						addAscii("RWFEnum").
						complete()).
					complete()).
				add(SERVICE_STATE_ID, FilterEntry::SetEnum, ElementList().
					addUInt(ENAME_SVC_STATE, SERVICE_UP).
					addUInt(ENAME_ACCEPTING_REQS, SERVICE_NO).
					complete()).
				complete()).
			complete()).complete().solicited(true), event.getHandle());

	directoryRequestReceived = true;
}
int main()
{
	try
	{
		AppClient appClient;
		OmmProvider provider( OmmIProviderConfig().adminControlDirectory( OmmIProviderConfig::UserControlEnum ), appClient );
		while (directoryRequestReceived == false) sleep(1000);
		for (Int32 i = 0; i < 10; i++)
		{
			provider.submit(UpdateMsg().domainType(MMT_DIRECTORY).filter(SERVICE_INFO_FILTER | SERVICE_STATE_FILTER).
				payload(Map().
					addKeyUInt(2, MapEntry::UpdateEnum, FilterList().
						add(SERVICE_STATE_ID, FilterEntry::UpdateEnum, ElementList().
							addUInt(ENAME_SVC_STATE, i % 2 ? SERVICE_UP : SERVICE_DOWN).
							addUInt(ENAME_ACCEPTING_REQS, i % 2 ? SERVICE_YES : SERVICE_NO).
							complete()).
						complete()).
					complete()), 0);
			sleep(1000);
		}
	}
	catch ( const OmmException& excp )
	{
		cout << excp << endl;
	}
	return 0;
}

Consumer relevant code

void ServiceNotifier::onRefreshMsg(const RefreshMsg& refreshMsg, const OmmConsumerEvent& ommConsEvent)
{
	handleServiceStatus(refreshMsg.getPayload());
}
void ServiceNotifier::onUpdateMsg(const UpdateMsg& updMsg, const OmmConsumerEvent& ommConsEvent)
{
	handleServiceStatus(updMsg.getPayload());
}
void ServiceNotifier::handleServiceStatus(const Payload& serviceInfo)
{
	if (DataType::MapEnum == serviceInfo.getDataType())
	{
		const Map& map = serviceInfo.getMap();
		bool serviceReady = false;
		bool serviceAcceptingRequests = true;
		while (map.forth())
		{
			const MapEntry& me = map.getEntry();
			if (me.getLoadType() == DataType::FilterListEnum)
			{
				const FilterList& fl = me.getFilterList();
				while (fl.forth())
				{
					const FilterEntry& fe = fl.getEntry();
					switch (fe.getFilterId())
					{
					case SERVICE_STATE_FILTER:
					{
						if (fe.getLoadType() == DataType::ElementListEnum)
						{
							const ElementList& eList = fe.getElementList();
							while (eList.forth())
							{
								const ElementEntry& ee = eList.getEntry();
								if (ee.getName() == ENAME_SVC_STATE)
								{
									serviceReady = ee.getUInt() == 1 ? true : false;
								}
								else if (ee.getName() == ENAME_ACCEPTING_REQS)
								{
									serviceAcceptingRequests = ee.getUInt() == 1 ? true : false;
								}
							}
						}
						break;
					}
					default:
						break;
					}
				}
			}
		}
		if (serviceReady)
		{
			notify();
		}
	}
}