[QPID-7959] [Java Broker] Running out of threads within HTTP management does not stop the Broker

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: qpid-java-broker-7.0.0
• Fix Version/s: Future
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 06/Oct/17 07:46
• Updated: 09/Oct/17 09:16

Description

If the process runs out of threads normally the Java Broker stops itself. This does not apply in the case of Jetty. The exception is reported to the log but the process continues. Otherwise the service seems to be not impacted.

2017-10-05 07:40:49,569 WARN  [qtp756037577-62] (o.e.j.u.t.QueuedThreadPool) -
java.lang.OutOfMemoryError: unable to create new native thread
        at java.lang.Thread.start0(Native Method)
        at java.lang.Thread.start(Thread.java:717)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.startThreads(QueuedThreadPool.java:476)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.access$200(QueuedThreadPool.java:49)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:635)
        at org.apache.qpid.server.management.plugin.HttpManagement$QBBTrackingThreadPool.lambda$newThread$5(HttpManagement.java:880)
        at java.lang.Thread.run(Thread.java:748)