2 Replies Latest reply: Jun 10, 2015 12:13 PM by chandra sarva RSS

    Error: QDS did not respond to request

    Syed Shah

      Hi,

       

      Apparently, All the services seem to be running fine and all reload and distribution tasks are going through. However, when I was checking the Qlikview management service logs, I found a lot of error entries like

       

      22.5.2015 09:12:06.5114825    Error    System.ServiceModel.CommunicationException: QDS did not respond to request.

      Last exception (for http://qv11dist2:4720/QDS/Service): An error occurred while receiving the HTTP response to http://qv11dist2:4720/QDS/Service. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. ---> System.ServiceModel.CommunicationException: An error occurred while receiving the HTTP response to http://qv11dist2:4720/QDS/Service. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host ||    at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) ||    --- End of inner exception stack trace --- ||    at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) ||    at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size) ||    at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead) ||    --- End of inner exception stack trace --- ||    at System.Net.HttpWebRequest.GetResponse() ||    at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) ||    --- End of inner exception stack trace --- ||  || Server stack trace:  ||    at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason) ||    at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout) ||    at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout) ||    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) ||    at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) ||    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) ||  || Exception rethrown at [0]:  ||    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) ||    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) ||    at PIX.Services.IQDS.GetEDXStatus(Guid execId) ||    at PIX.Services.ClientSupport.QDSClientImpl.<>c__DisplayClass30.<GetEDXStatus>b__2f(IQDS i) ||    at PIX.Services.ClientSupport.ClusterBase`1.Invoke[TR](CallType callType, Func`2 func, List`1 allResults, QlikMethodBehavior methodBehavior) ||    --- End of inner exception stack trace --- ||    at PIX.Services.ClientSupport.ClusterBase`1.Invoke[TR](CallType callType, Func`2 func, List`1 allResults, QlikMethodBehavior methodBehavior) ||    at PIX.Services.ClientSupport.ClusterBase`1.Invoke[TR](CallType callType, Func`2 func) ||    at QMSBackendCore.Communication.DistributionService.GetEDXResult(DistributionServiceResource qdsResource, Guid execId)

        • Re: Error: QDS did not respond to request
          Bill Britt

          Hi,

           

          Think of it this way. Your phone rings and you answer it. The person on the phone needs information that you need to look up. You put the person on hold to get the information. When you pick the phone back up to give the information the person has hung up.

           

           

          Bill

            • Re: Error: QDS did not respond to request
              chandra sarva

              Hi Bill,

               

              so what you saying is nothing much to worry about these errors ?

              we have the same issue after upgraded to 11.2 SR10 we see lot of these communication errors but services and servers seems to all working fine.  Even tasks are running fine.

              FYI.....the logging levels before and after upgrade are the same and no change in configurations. Except we have performance logging on QVS cluster enabled after the upgrade and not sure if it has any impacts on management service logs.

               

              Please suggest.

               

              Thanks

              Chandra