java.io.IOException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • GitHub comment 196#237605926
    via GitHub by Muffinman
    ,
  • insufficient data written
    via GitHub by wonderfly
    ,
  • Issue Insufficient data written
    via GitHub by wonderfly
    ,
  • Insufficient data written when inserting rows
    via Stack Overflow by rd3n
    ,
    • java.io.IOException: insufficient data written at sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.close(HttpURLConnection.java:3501)[?:1.8.0_101] at com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:81)[google-http-client-1.20.0.jar:1.20.0] at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:972)[google-http-client-1.20.0.jar:1.20.0] at fr.pilato.elasticsearch.crawler.fs.client.ElasticsearchClient.bulk(ElasticsearchClient.java:231)[fscrawler-2.2-SNAPSHOT.jar:?] at fr.pilato.elasticsearch.crawler.fs.client.ElasticsearchClient.bulk(ElasticsearchClient.java:243)[fscrawler-2.2-SNAPSHOT.jar:?] at fr.pilato.elasticsearch.crawler.fs.client.BulkProcessor.execute(BulkProcessor.java:136)[fscrawler-2.2-SNAPSHOT.jar:?] at fr.pilato.elasticsearch.crawler.fs.client.BulkProcessor.executeWhenNeeded(BulkProcessor.java:123)[fscrawler-2.2-SNAPSHOT.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[?:1.8.0_101] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[?:1.8.0_101] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[?:1.8.0_101] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[?: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]

    Users with the same issue

    Unknown visitor1 times, last one,