Query Service Optional Functionality

Data Service proxy attempts to communicate with Query Service in three different optional ways. To configure these options, add a line of code as indicated below, to Miner.Responder.DataServices.exe.config, located in the Responder\Server install location. In this file, look for the following code to add the optional configurations.

<miner.responder.server.configuration default="ConfigurationName">
    <multicast group="" port="6679" ttl="2"/>
    <queryService server="ServerName" port="2063" enabled="false"/>


If reviveOnFailure is set to false, the Data Service proxy tries to reach the specified server once. If it cannot be reached, it logs a message to the event log and switches to using Data Services. This prevents the proxy from continually trying to reach an unavailable server.

If Query Services is restarted, the proxy will again try to reach the server before switching to Data Services.

If reviveOnFailure is set to true, the proxy will try to reach the specified server every 2 seconds, logging a message to the event log for each failure.

<queryService server="localhost" port="2063" enabled="true" reviveOnFailure="false">


revivalInterval is the number of milliseconds between attempts to reconnect to a Query Service. The proxy tries to connect to the Query Service until the Query Service is available. The default is 2 seconds.


queryTimeout is the number of milliseconds to wait for a request until the proxy considers the query as having timed out. The default is 30 seconds.

For example, in the code below a proxy starts and checks for the Query Service, then waits 15 seconds before determining it is unreachable. After 60 seconds, the proxy tries again. This is repeated until the Query Service is reached.

<queryService server="localhost" port="2063" enabled="true" revivalInterval="60000" queryTimeout="15000">
QR code for this page

Was this helpful?