CQSE related error | Community
Skip to main content
A
askdctm
Level 9
October 16, 2015
Solved

CQSE related error

  • October 16, 2015
  • 7 replies
  • 1745 views

Hi All,

We are facing cq slowness for quite some days now in production and we observed

*WARN* [CQSE Listener [0.0.0.0:4502]] servletengine Maximum thread number reached: 200  in logs.

Can you please let us know 

- What all things to check, to find out what is going wrong .

- Can we increase thread number directly?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

You need to analyze the threaddumps and find the bottleneck. [1] looks like a good source to learn howto read thread dumps.

kind regards,
Jörg

 

[1] http://www.javacodegeeks.com/2012/03/jvm-how-to-analyze-thread-dump.html

7 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 16, 2015

Hi,

The web container of the CQSE is limited to 200 concurrent threads, which is a good upper limit. If you hit this limit, this normally means, that there's something wrong. In most cases request processing is stuck either because of lock contention or endless loops. The best way to analyze such issues is to create threaddumps and then analyze them. These dumps provide enough information to better understand the issue and also where to look further on.

kind regards,
Jörg

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

Have you read through the performance optimization documentation located here:

https://docs.adobe.com/docs/en/cq/current/deploying/performance.html

https://docs.adobe.com/docs/en/cq/current/deploying/performance.html#Performance Monitoring

As discussed in these topics - there could be various reasons. 

A
askdctmAuthor
Level 9
October 16, 2015

Hi Jorg,

Thanks a lot for your reply. 

Daily its going down around a particular time. We have been going through dumps but not getting anything concrete.

What are all the things we can look at, for this issue.

A
askdctmAuthor
Level 9
October 16, 2015

Hi Scott,

Thank you for your reply.

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

You need to analyze the threaddumps and find the bottleneck. [1] looks like a good source to learn howto read thread dumps.

kind regards,
Jörg

 

[1] http://www.javacodegeeks.com/2012/03/jvm-how-to-analyze-thread-dump.html

A
askdctmAuthor
Level 9
October 16, 2015

Hi Jorg,

Thank you for your reply.

this-that-the-otter
this-that-the-otter
Level 4
August 21, 2016

FYI - RE: 21.08.2016 17:50:58.164 *WARN* [CQSE Listener [0.0.0.0:4503]] servletengine Maximum thread number reached: 200

I have also seen this WARN as the built-in online backup tool freezes & locks when it's completing its backup.

After the backup completes and the backupInProgress.txt file disappears from where the backup is written, the instance recovered.

 

Regards,

Bill

Terms & ConditionsAccessibility statement

Loading footer...