com.reuters.rfa.internal.connection.rssl.RSSLConnection processTransportData
SEVERE: com.reuters.rfa.connection.rssl.myNS.RSSLconnection
Caught internal exception java.util.NoSuchElementException.
java.util.HashMap$HashIterator.nextNode(Unknown Source)
java.util.HashMap$ValueIterator.next(Unknown Source)
com.reuters.rfa.internal.connection.rssl.RSSLClientConnection.NotifySessionComponentVersionInfo(Unknown Source)
com.reuters.rfa.internal.connection.rssl.RSSLLoginHandler.connectionLogin(Unknown Source)
RFA Java does not use Windows registry direclty, but Java preferences API to manage the configuration. Since you mention that your application is multi-threaded, so I suppose it is some kind of race around condition. Try adding pause within your application to see if any thread is trying to access login state/data before its available.
We are migrating to RFAJ 8, and existing program is multi-threaded, so after start, there are multiple threads concurrently trying to connect to the service, and sometimes we got this exception. It's hard to reproduce this scenario but I feel it may related to login stage, when wait for response event and waiting time is too short. Anything wrong with Windows Registry usage?QuickStartConsumer works fine.
@Gurpreet We are migrating to RFAJ 8, and existing program is multi-threaded, so after start, there are multiple threads concurrently trying to connect to the service, and sometimes we got this exception. It's hard to reproduce this scenario but I feel it may related to login stage, when wait for response event and waiting time is too short. Anything wrong with Windows Registry usage?QuickStartConsumer works fine.