When I try to create a new topic, I'm getting a SQL timeout. I've been investigating using Profiler and have traced it down to the following:
During the topic creation, the following command is sent to SQL Server:
exec sp_executesql N'select umbracoNode.id, umbracoNode.parentId, umbracoNode.sortOrder, cmsContentXml.xml from umbracoNode inner join cmsContentXml on cmsContentXml.nodeId = umbracoNode.id and umbracoNode.nodeObjectType = @type order by umbracoNode.level, umbracoNode.sortOrder',N'@type uniqueidentifier',@type='C66BA18E-EAF3-4CFF-8A22-41B16D66A972'
This takes approximately 8 minutes to return. In my site's database, that command returns over 7k rows.
Obviously, this is where the xml of the forum post gets insert into cmsContentXml. The problem is (I think) cmsContentXml is locked from the prior command. So it times out attempting the insert.
The end result is that the new topic is mostly created, but never gets published. I can log into umbraco and publish it myself, but obviously it's a deal breaker for me if users can't create their own topics without admin interaction.
I've tried toying with the indexes on the umbracoNode table, but to no avail, and I don't love this approach anyway, since now I'm modifying part of umbraco's core installation.
Still struggling with this one. I think it's somewhat of a race condition going on in the code that publishes a topic. I downloaded the source and started tinkering with that method...
What I've found is that if I issue a Thread.Sleep command in between publishing the topic and publishing the first post, it works.
SQL timeout creating new topic
When I try to create a new topic, I'm getting a SQL timeout. I've been investigating using Profiler and have traced it down to the following:
During the topic creation, the following command is sent to SQL Server:
This takes approximately 8 minutes to return. In my site's database, that command returns over 7k rows.
The next command is the following:
Obviously, this is where the xml of the forum post gets insert into cmsContentXml. The problem is (I think) cmsContentXml is locked from the prior command. So it times out attempting the insert.
The end result is that the new topic is mostly created, but never gets published. I can log into umbraco and publish it myself, but obviously it's a deal breaker for me if users can't create their own topics without admin interaction.
I've tried toying with the indexes on the umbracoNode table, but to no avail, and I don't love this approach anyway, since now I'm modifying part of umbraco's core installation.
Any help would be greatly appreciated.
Still struggling with this one. I think it's somewhat of a race condition going on in the code that publishes a topic. I downloaded the source and started tinkering with that method...
What I've found is that if I issue a Thread.Sleep command in between publishing the topic and publishing the first post, it works.
Obviously, putting this in production code scares me.
Is this just an issue with the size of my site? I have about 7,000 published nodes and I'm attempting to integrate the forum into that.
is working on a reply...