Randomly (it appears), I get this error and then the application fails
to respond. This error appears on the web server (web service client):
Message: Operation Timed Out
Source: Microsoft.Web.Services2
Target Site: Microsoft.Web.Services2.SoapEnvelope
SendRequestResponse(System.String,
Microsoft.Web.Services2.SoapEnvelope)
StackTrace: at
Microsoft.Web.Services2.Messaging.SoapClient.SendRequestResponse(String
methodname, SoapEnvelope envelope)
at
Microsoft.Web.Services2.Security.SecurityTokenServiceClient.RequestSecurityToken(SecurityTokenMessage
request, String methodName)
at
Microsoft.Web.Services2.Security.SecurityContextTokenServiceClient.RequestSecurityContextToken(SecurityToken
baseToken, SecurityToken issuerToken, AppliesTo appliesTo)
at
Microsoft.Web.Services2.Security.SecurityContextTokenServiceClient.IssueSecurityContextTokenAuthenticated(SecurityToken
baseToken, SecurityToken issuerToken)
at
Comerica.CAS.Services.WSDelegate.WSEEncryptionFilter.ProcessMessage(SoapEnvelope
envelope)
at
Microsoft.Web.Services2.Pipeline.ProcessOutputMessage(SoapEnvelope
envelope)
at Microsoft.Web.Services2.OutputStream.Close()
at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
I haven't yet nailed out a sequence to simulate it, but it does appear
to be happening when multiple users use certain screens simultaneously.
I am using WSE2.0 SP3. I am also using WS-SecureConversation. On the
client side, I setup a WSEEncryptionFilter in the pipeline to perform
the encryption tasks. This WSEEncryptionFilter is a singleton. I tried
not making it a singleton and it did not help. It also appears that
when I run both the webservice and the web service client on the same
machine, this error does not occur.
Please help.
Thanks.
Raj.
Satchi - 20 Feb 2006 05:48 GMT
Change the TimeOut value in your client configuration file to a higher value. This shall solve your problem.