Has anyone ever experienced timeouts with core service? At times, we experience timeouts while simply reading, getting a list of components. We are using the netTcp binding and we have adjusted timeout settings in the applications config file. This has not helped though. Any thoughts?
I ran a trace on WCF and this is the error I received; 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:05:00.0000001'.
I normally get this when I bump up the timeout to 10 minutes
Here are the settings in my app.config;
<netTcpBinding> <binding name="netTcp" closeTimeout="00:3:00" openTimeout="00:3:00" receiveTimeout="00:3:00" sendTimeout="00:3:00" hostNameComparisonMode="StrongWildcard" maxBufferSize="10485760" maxBufferPoolSize="524288" maxReceivedMessageSize="10485760" transferMode="Buffered"> <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" /> </binding> </netTcpBinding> </bindings>
I am reading through 4100 components.
Actually reading the components went fine. I encountered no timeouts this time. However, when updating, I always get a timeout. Sometimes it is right away and sometimes it times out server components in. Why am I updating components this way? We have a large amount of content that needs ported to another environment/database. The developers of this content do not clean up there invalid components. So, I am searching there content folders for invalid components. I then send them a report on what to fix.
I spoke with our DBAs and they ensure me that there are no problems with the database. I wish I could see for myself. :) No permissions to run performance queries against the CM database.
I am checking into Siva's post. This might be the answer to our issue as well.