nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Content Server 10.0.0 Update 3 threading issues

Kai Chow

I am working on the Correspondence Tracking module. Certain operations in our module takes a really really long time to execute when running as a Service. It also happens in Update 1. It seems like all the threads hang when one of the DistributedAgent sleeps. One of the requests takes about 3 to 4 minutes to execute. The following is the list of DistributedAgent threads when they are about to go to sleep. Anyh help is appreciated. Please let me know if you need more info. Thanks. BTW, it works fine in the Builder as it has only one thread.

connect105.log(346): 08/09/2011 15:13:36 INFO [2201016136] 0000001816: CAPI.Log: DistributedAgentLog: ....Going to sleep for 1000 ms.
connect105.log(375): 08/09/2011 15:13:37 INFO [2202020377] 0000002190: CAPI.Log: DistributedAgentLog: ....Going to sleep for 2000 ms.
connect105.log(411): 08/09/2011 15:13:39 INFO [2204037195] 0000003049: CAPI.Log: DistributedAgentLog: ....Going to sleep for 3000 ms.
connect105.log(441): 08/09/2011 15:13:42 INFO [2207046712] 0000003130: CAPI.Log: DistributedAgentLog: ....Going to sleep for 5000 ms.
connect105.log(463): 08/09/2011 15:13:47 INFO [2212053091] 0000003821: CAPI.Log: DistributedAgentLog: ....Going to sleep for 8000 ms.
connect105.log(485): 08/09/2011 15:13:55 INFO [2220055545] 0000003892: CAPI.Log: DistributedAgentLog: ....Going to sleep for 13000 ms.
connect105.log(507): 08/09/2011 15:14:08 INFO [2233073666] 0000003957: CAPI.Log: DistributedAgentLog: ....Going to sleep for 21000 ms.
connect105.log(529): 08/09/2011 15:14:29 INFO [2254076338] 0000004028: CAPI.Log: DistributedAgentLog: ....Going to sleep for 34000 ms.
connect106.log(346): 08/09/2011 15:13:36 INFO [2201550674] 0000002162: CAPI.Log: DistributedAgentLog: ....Going to sleep for 1000 ms.
connect106.log(375): 08/09/2011 15:13:37 INFO [2202566758] 0000002558: CAPI.Log: DistributedAgentLog: ....Going to sleep for 2000 ms.
connect106.log(405): 08/09/2011 15:13:39 INFO [2204578849] 0000003078: CAPI.Log: DistributedAgentLog: ....Going to sleep for 3000 ms.
connect106.log(435): 08/09/2011 15:13:42 INFO [2207592936] 0000003159: CAPI.Log: DistributedAgentLog: ....Going to sleep for 5000 ms.
connect106.log(457): 08/09/2011 15:13:47 INFO [2212598719] 0000003842: CAPI.Log: DistributedAgentLog: ....Going to sleep for 8000 ms.
connect106.log(479): 08/09/2011 15:13:55 INFO [2220601580] 0000003913: CAPI.Log: DistributedAgentLog: ....Going to sleep for 13000 ms.
connect106.log(501): 08/09/2011 15:14:08 INFO [2233611356] 0000003978: CAPI.Log: DistributedAgentLog: ....Going to sleep for 21000 ms.
connect106.log(523): 08/09/2011 15:14:29 INFO [2254622746] 0000004075: CAPI.Log: DistributedAgentLog: ....Going to sleep for 34000 ms.
connect107.log(338): 08/09/2011 15:13:37 INFO [2202109529] 0000002528: CAPI.Log: DistributedAgentLog: ....Going to sleep for 1000 ms.
connect107.log(360): 08/09/2011 15:13:38 INFO [2203112231] 0000003013: CAPI.Log: DistributedAgentLog: ....Going to sleep for 2000 ms.
connect107.log(382): 08/09/2011 15:13:40 INFO [2205124576] 0000003099: CAPI.Log: DistributedAgentLog: ....Going to sleep for 3000 ms.
connect107.log(404): 08/09/2011 15:13:43 INFO [2208136584] 0000003180: CAPI.Log: DistributedAgentLog: ....Going to sleep for 5000 ms.
connect107.log(434): 08/09/2011 15:13:48 INFO [2213145925] 0000003871: CAPI.Log: DistributedAgentLog: ....Going to sleep for 8000 ms.
connect107.log(456): 08/09/2011 15:13:56 INFO [2221147457] 0000003936: CAPI.Log: DistributedAgentLog: ....Going to sleep for 13000 ms.
connect107.log(486): 08/09/2011 15:14:09 INFO [2234159024] 0000004007: CAPI.Log: DistributedAgentLog: ....Going to sleep for 21000 ms.
connect107.log(516): 08/09/2011 15:14:30 INFO [2255171844] 0000004104: CAPI.Log: DistributedAgentLog: ....Going to sleep for 34000 ms.

Find more posts tagged with

Comments

David Templeton

Kai

What OS is this running on? You know this road :-) How many cores? What is the CPU saturation level?

David

Kai Chow

2800 Mhz, 2 Core(s), 4 Logical Processor(s)

Windows 7 Professional 64-bit

Disk Usage: 3% to 20%

If you need more info., please let me know. Dave, thanks for looking into this.

Raymond_Tsui

Windows 7 is not a supported server platform for CS 10.

Ray

Nathaniel_Law

Ray,

That is understand, but this is for development and regardless the issue happens on Windows 2008 & R2 which is where it was first reported.

Nate

David Templeton

Kai

if you reduce the number of worker agents

[distributedagent]
lib=.\bin\lljob.dll
name=lljob
prio=critical
timeout=5000
number=3
info=.\config\opentext.ini;distributedagent
StartScript=.\scripts\llfull.lxe
JobScript=.\scripts\distributedagent_run.e
SleepIntervalSec=30
PercentUsage=80
TaskBlockSize=100

to 1 or 2 does it get better?

david

Kai Chow

Reducing the number of worker threads to 1 or 2 does not work either. In fact, it seems slower than setting it to 3.

David Templeton

ok very stupid question, comment out the loader lines

#load_distributedagent=distributedagent
#load_daagent=daagent
does that make a difference?

Is this MSSQL????? If so, do you have snapshot isolation on?

Kai Chow

Nope. Commenting out the distributedagent and the daagent does not make a difference.

I am using MSSQL 2008 R2. Snapshot isolation is not on. Thanks, Dave. There is no stupid questions!!

Kai Chow

Commented out the two lines also generated trace files as well.

David Templeton

that is never good :-)

Kai Chow

Dave, Hans was suggesting disabling HT mode. Do you how to do that? No harm to try it out.

David Templeton

that would be in the bios, afaik

David