[
https://issues.jboss.org/browse/TEIID-5139?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5139:
---------------------------------------
The first thing that needs addressed is that the warning message is incorrect. In the
TEIID-3519 change we didn't differentiate between the dqp worker pool and the async
pool.
Already tried what is explained here but applied for the standalone
mode without any success.
I see there was a dangling question that wasn't answered there, so there may be
something amiss. It looks like you are running in standalone mode though. What did you
attempt to change those attributes to? Did you use the cli or a direct edit to the
standalone.xml?
Unfortunately none of the thread dumps show anywhere close to 10 active async workers, so
it's hard to say why things are waiting in the queue.
Reached maximum thread count "10" for worker pool
"async-teiid-threads"
-----------------------------------------------------------------------
Key: TEIID-5139
URL:
https://issues.jboss.org/browse/TEIID-5139
Project: Teiid
Issue Type: Bug
Affects Versions: 10.0
Environment: Teiid 10.0.0
Wildfly 11
RHEL 7.2
Reporter: Pedro InĂ¡cio
Assignee: Steven Hawkins
Attachments: teiid.7z
Cannot configure system to remove the following warning:
*TEIID30009 Reached maximum thread count "10" for worker pool
"async-teiid-threads" with a queue size high of "44". Queued work
waited 500 ms prior to executing. To avoid queuing of work you may consider increasing
"max-threads" or decreasing the "max-active-plans" in the
"standalone-teiid.xml" file.*
Already tried what is explained [
here|https://developer.jboss.org/thread/275761] but
applied for the standalone mode without any success.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)