You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/10/06 07:47:00 UTC
[jira] [Updated] (QPID-7959) [Java Broker] Running out of threads
within HTTP management does not stop the Broker
[ https://issues.apache.org/jira/browse/QPID-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7959:
-----------------------------
Affects Version/s: qpid-java-broker-7.0.0
> [Java Broker] Running out of threads within HTTP management does not stop the Broker
> ------------------------------------------------------------------------------------
>
> Key: QPID-7959
> URL: https://issues.apache.org/jira/browse/QPID-7959
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-broker-7.0.0
> Reporter: Keith Wall
>
> 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)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org