[teiid-issues] [JBoss JIRA] (TEIID-5139) Reached maximum thread count "10" for worker pool "async-teiid-threads"

Steven Hawkins (JIRA) issues at jboss.org
Wed Nov 15 09:01:00 EST 2017


    [ https://issues.jboss.org/browse/TEIID-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490433#comment-13490433 ] 

Steven Hawkins commented on TEIID-5139:
---------------------------------------

I've had a chance to look at this more.  This is a bug with the initialization logic.  It should not be looking for the parent thread pool element / node to be defined to use the attribute value.  I'll correct this and the warning message.

> 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)



More information about the teiid-issues mailing list