Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by poseidonqiu
, 1 year ago
via Stack Overflow by user1172468
, 2 years ago
via Google Groups by Unknown author, 3 months ago
java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method)[?:1.8.0_101] at java.lang.Thread.start(Thread.java:714)[?:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)[?:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357)[?:1.8.0_101] at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)[?:1.8.0_101] at org.xbib.pipeline.SimplePipelineExecutor.execute(SimplePipelineExecutor.java:100)[elasticsearch-jdbc-2.3.4.1.jar:?] at org.xbib.tools.JDBCImporter.execute(JDBCImporter.java:240)[elasticsearch-jdbc-2.3.4.1.jar:?] at org.xbib.tools.JDBCImporter.run(JDBCImporter.java:149)[elasticsearch-jdbc-2.3.4.1.jar:?] at java.lang.Thread.run(Thread.java:745)[?:1.8.0_101] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[?:1.8.0_101] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[?:1.8.0_101] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[?:1.8.0_101] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[?:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[?:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[?:1.8.0_101] at java.lang.Thread.run(Thread.java:745)[?:1.8.0_101]