Skip to main content
C
CHASEONHO18-Opal
18-Opal
July 17, 2018
Question

APPARENT DEADLOCK Issue

  • July 17, 2018
  • 1 reply
  • 3179 views

we made chart like following picture.

image 2.png

a chart get about 5000~10000 data.

and divide 500 row using some rule

sometimes when i call this service, thingworx display error log

"com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@7345aa02 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!"

 

why? how to fix it?

i want never see error log again

1 reply

S
supandey5-Regular Member
5-Regular Member
July 17, 2018

Hi @CHASEONHO what kind of service is it? I'm not sure if this is really a deadlock issue could be just because you are doing lot of in-memory calculation which could be leading to out of memory condition.

 

Would it be possible to attach the tomcat & application log?

C
CHASEONHO18-OpalAuthor
18-Opal
July 17, 2018

Here are today log file.

my service get infotable about 10000.

and if infotable rows are above 500 it will convert to new infotable under 500 rows

S
supandey5-Regular Member
5-Regular Member
July 19, 2018

Thank you @CHASEONHO for attaching the logs how much resource is assigned to the instance running ThingWorx? There's not much but defintely there are some tasks in ValueStream thats queued up.

 

Which persistence provider are you using for ThingWorx?

Terms & ConditionsAccessibility statement