The publishing App developed using RFA Java got disconnected from the ADH. The logs in the ADH is as below
Dismounting application:
Received source message with invalid stream ID -17098. Source stream ID is -1.
11.3k
●25 ●9 ●14
Hi @jalaj.mehta
I'm able to replicate the issue by publishing a source directory message with new token generated from generateToken() function. It seems that ADH expects that the source directory messages should be published only on one item stream. Once application has tried to publish a source Directory message on new item stream, ADH will close the connection and log the "Received source message with invalid stream ID -17098. Source stream ID is -1." error.
This means that the application needs to store the token generated used for the first source directory message and then reuse it for subsequent source directory messages.
Please verify the JRFAPublisher.sendDirectoryImage function if it reuses the token for directory message publishing.
665
●3 ●5 ●6
Hello @jalaj.mehta
When a publishing application is disconnected it is possible that some errors are logged as a result of the disconnection, rather than the cause, depending on events occurring at the time e.g. stream-id invalidated by a disconnect. To make sure of root cause do you have logging for the application as well as the ADH at that time?
5
●0 ●1 ●4
Thanks Dave, we do not really have any logs from the ADH at the time of issue. But we have asked the App team if they have anything at their end.
5
●0 ●1 ●4
Hi Dave, the limited logs from App
15:00:58,470 INFO pub-adh-nip-gdex_SessionEventsDispatcher JRFAPublisher.sendDirectoryImage:277 Directory reply sent for [GDEX]
15:00:58,470 INFO Thread-1722 MDPubServiceEntry.syncCacheWithInfra:802 Sync'ing cache with infra..
15:00:58,472 INFO pub-adh-nip-gdex_SessionEventsDispatcher JRFAPublisher.sendDirectoryImage:277 Directory reply sent for [GDEX]
15:00:58,473 INFO pub-adh-nip-gdex_SessionEventsDispatcher JRFAPublisher.sendDirectoryImage:277 Directory reply sent for [GDEX]
15:00:58,477 INFO pub-adh-nip-gdex_SessionEventsDispatcher JRFAPublisher.processEvent:474 Connection Down: [Connection to <hostname deleted due to security>:14303 failed in connection _Default::pub-adh-nip-gdex_connection3; Channel disconnected]
15:00:58,483 ERROR pub-adh-nip-gdex_SessionEventsDispatcher JRFAPublisher.processEvent:412 Received OMMCmd ERROR EVENT for publisher [GDEX] for id: 24885814 : No connection available for publish
Feb 07, 2018 3:00:58 PM com.reuters.mainloop.channel.ChannelMainLoop processException
SEVERE: Caught internal exception [java.lang.NullPointerException]
in thread [_Default::pub-adh-nip-gdex Session EventQueueGroup]
com.reuters.rfa.internal.session.omm.OMMItemPubSubmitMsg.release(Unknown Source)
com.reuters.rfa.internal.session.ommp.OMMNonInteractiveProviderEventSourceHandler.processRequestMessage(Unknown Source)
com.reuters.rfa.internal.common.RequestMessage.dispatch(Unknown Source)
{5}
15:00:58,498 ERROR pub-adh-nip-gdex_SessionEventsDispatcher JRFAPublisher.processEvent:412 Received OMMCmd ERROR EVENT for publisher [GDEX] for id: 24885837 : No connection available for publish
Feb 07, 2018 3:00:58 PM com.reuters.mainloop.channel.ChannelMainLoop processException
SEVERE: Caught internal exception [java.lang.NullPointerException]
in thread [_Default::pub-adh-nip-gdex Session EventQueueGroup]
com.reuters.rfa.internal.session.omm.OMMItemPubSubmitMsg.release(Unknown Source)
com.reuters.rfa.internal.session.ommp.OMMNonInteractiveProviderEventSourceHandler.processRequestMessage(Unknown Source)
com.reuters.rfa.internal.common.RequestMessage.dispatch(Unknown Source)
{5}
….
15:00:58,572 ERROR pub-adh-nip-gdex_SessionEventsDispatcher JRFAPublisher.processEvent:412 Received OMMCmd ERROR EVENT for publisher [GDEX] for id: 24886094 : No connection available for publish
Feb 07, 2018 3:00:58 PM com.reuters.mainloop.channel.ChannelMainLoop processException
SEVERE: Caught internal exception [java.lang.NullPointerException]
in thread [_Default::pub-adh-nip-gdex Session EventQueueGroup]
