Michael,
I tried to increase the open/close/send/receive timeout on both the client
and service side and it does not work. The error message still complains the
"configured timeout (00:01:00)" even though I set them longer than that.
I found the service actually received the call add returned the value. If
the message is small, the client will get the reply immediately. However, if
I increased the message to a certain size (I tried to increase the size), the
client will no longer get it and experience a timeout. My guess is the size
of the message might caused the problem. Any idea to correct it?
Thanks.
Roy
> Hello Roy,
>
[quoted text clipped - 49 lines]
> >> R> is the reason for it and how to resolve it?
> >> R>
I enabled tracing. On the service side, I got
<Exception><ExceptionType>System.ServiceModel.CommunicationException,
System.ServiceModel, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The socket connection
was aborted. This could be caused by an error processing your message or a
receive timeout being exceeded by the remote host, or an underlying network
resource issue. Local socket timeout was '00:01:00'.</Message><StackTrace>
at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32
offset, Int32 size, Boolean immediate, TimeSpan timeout)
at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer,
Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, BufferManager
bufferManager).....
On client side, I got
<ExceptionString>System.ServiceModel.CommunicationException: The maximum
message size quota for incoming messages (65536) has been exceeded. To
increase the quota, use the MaxReceivedMessageSize property on the
appropriate binding element. --->
System.ServiceModel.QuotaExceededException: The maximum message size quota
for incoming messages (65536) has been exceeded. To increase the quota, use
the MaxReceivedMessageSize property on the appropriate binding element.
--- End of inner exception stack trace
---</ExceptionString><InnerException><ExceptionType>System.ServiceModel.QuotaExceededException,
System.ServiceModel, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The maximum message
size quota for incoming messages (65536) has been exceeded. To increase the
quota, use the MaxReceivedMessageSize property on the appropriate binding
element.</Message><StackTrace> at
System.ServiceModel.Channels.ClientDuplexConnectionReader.DecodeMessage(Byte[]
buffer, Int32& offset, Int32& size, Boolean& isAtEOF, TimeSpan
timeout)
at
System.ServiceModel.Channels.SessionConnectionReader.DecodeMessage(TimeSpan
timeout)
at
System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)
at System.ServiceModel.Channels.SocketConnection.FinishRead()
at
System.ServiceModel.Channels.SocketConnection.AsyncReadCallback(Boolean
haveResult, Int32 error, Int32 bytesRead)....
I increased maxReceivedMessageSize. But it still not work. Any ideas?
Noah - 22 May 2008 20:21 GMT
I've run into this same issue. Has anyone found a solution to this? I've
tried increasing message sizes, changing up the config files, and a number of
other things, but I consistently get the same issue.