APPARENT DEADLOCK Issue

[CHASEONHO]

we made chart like following picture.

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

[supandey]

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?

[CHASEONHO]

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

[supandey]

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?

[CHASEONHO]

H2 is used.
Is this a problem?
Will it be resolved by increasing the queue to infinity?

[supandey]

@CHASEONHO I'm still missing information on how much resource you have provided to the ThingWorx instance. Meaning CPU, RAM esp. the one assigned to Tomcat process. etc.

[CHASEONHO]

Wher can i get a information on how much resource you have provided to the ThingWorx instance?

[supandey]

You can find out if you have defined the initial / max memory parameters for the Tomcat JVM e.g.

-Xms512m
-Xmx1024m

If tomcat is running on windows os you could check the Monitor Tomcat configuration e.g.

BTW, are you using your installation for the production environment?