Issue

• will increasing max threads of short-running-threads potentially solve
  • server.log entries similar to

ERROR [<connector package>] T[895] - Error org.jboss.threads.ExecutionTimedOutException, error code: 1: javax.resource.spi.work.WorkRejectedException: org.jboss.threads.ExecutionTimedOutException, error code: 1
    at org.jboss.jca.core.workmanager.WorkManagerImpl.scheduleWork(WorkManagerImpl.java:591)
    ...
        at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:218)
    at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
    at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:806) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
    at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
    at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:847) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
    at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
Caused by: org.jboss.threads.ExecutionTimedOutException
    at org.jboss.threads.QueueExecutor.executeBlocking(QueueExecutor.java:312) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1]
    ...

• Why the current thread count is always 0 for long-running-threads?
• Are short-running-threads allocated directly to the max value at jboss startup and immediately active?
• Is core threads = max threads valid?