thread.QueuedThreadPool在Neo4j的

我使用的Neo4j社區-2.2.3。 neo4J有2,220,700個節點和4,334,748個關係。突然，neo4j不能正常工作。以下是console.log中的錯誤日誌。thread.QueuedThreadPool在Neo4j的

16:43:04.225 [qtp814955981-22324] WARN o.e.j.util.thread.QueuedThreadPool - 
java.lang.IllegalStateException: org.eclipse.jetty.util.SharedBlockingCallback$BlockerTimeoutException 
     at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.failed(SharedBlockingCallback.java:184) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpChannel$CommitCallback.failed(HttpChannel.java:852) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:103) ~[jetty-io-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:620) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:540) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at java.lang.Thread.run(Thread.java:745) [na:1.7.0_80] 
Caused by: org.eclipse.jetty.util.SharedBlockingCallback$BlockerTimeoutException: null 
     at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:216) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:133) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpOutput.close(HttpOutput.java:163) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.Response.closeOutput(Response.java:1017) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:421) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) ~[jetty-io-9.2.4.v20141103.jar:9.2.4.v20141103] 
     ... 3 common frames omitted 
16:43:04.226 [qtp814955981-22324] WARN o.e.j.util.thread.QueuedThreadPool - Unexpected thread death: [email protected] in qtp814955981{STARTED,1 
2<=28<=28,i=0,q=1466} 
16:43:04.227 [qtp814955981-22351] WARN o.e.j.util.thread.QueuedThreadPool - 
java.lang.IllegalStateException: org.eclipse.jetty.util.SharedBlockingCallback$BlockerTimeoutException 
     at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.failed(SharedBlockingCallback.java:184) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpChannel$CommitCallback.failed(HttpChannel.java:852) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:103) ~[jetty-io-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:620) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:540) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at java.lang.Thread.run(Thread.java:745) [na:1.7.0_80] 
Caused by: org.eclipse.jetty.util.SharedBlockingCallback$BlockerTimeoutException: null 
     at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:216) ~[jetty-util-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:133) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpOutput.close(HttpOutput.java:163) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.Response.closeOutput(Response.java:1017) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:421) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103] 
     at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) ~[jetty-server-9.2.4.v20141103.jar:9.2.4.v20141103]

請指教！提前謝謝了！

來源

2015-12-09 molly

是當你啓動數據庫或者有一些關於它的操作會發生？ –

這聽起來像你已經超過了可用於網絡服務器處理請求的線程的最大數量。在您提交查詢時，查詢將佔用Web服務器線程，直到它返回或超時爲止。如果你有很多需要一段時間才能運行的查詢，你可能會用盡線程。可用於http服務器的線程數量是可配置的。見the server browser configuration documentation：

指定使用的Neo4j的Web服務器來控制服務器將業務併發的HTTP請求級別的線程數。

org.neo4j.server.webserver.maxthreads = 200

但是，如果這是一個經常發生，你可能需要在爲什麼你查詢要花這麼長時間來執行或整體服務器負載密切關注更多。

來源

2015-12-10 00:29:18

thread.QueuedThreadPool在Neo4j的

回答

相關問題