java.util.concurrent.ExecutionException

java.io.IOException: No such asset wlcontent://users@134.226.14.32:8080/admin/admin/art/WC.kmz/WC.kmz.dep

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web592

  • via Google Groups by Gene Dalton, 6 months ago
    java.io.IOException: No such asset wlcontent://users@134.226.14.32:8080/admin/admin/art/WC.kmz/WC.kmz.dep
  • com.floragunn.searchguard.authentication.AuthException: No user admin or wrong password (digest: plain/none)
  • java.io.IOException: Cannot run program "phantomjs" (in directory "/Users/pedrompg/Documents/Tenants/vhosts/discoverint"): error=2, No such file or directory
  • Stack trace

    • java.util.concurrent.ExecutionException: java.io.IOException: No such asset wlcontent://users@134.226.14.32:8080/admin/admin/art/WC.kmz/WC.kmz.dep at java.util.concurrent.FutureTask.report(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at org.jdesktop.wonderland.client.cell.CellCacheBasicImpl$URLDownloader.run(CellCacheBasicImpl.java:913) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: No such asset wlcontent://users@134.226.14.32:8080/admin/admin/art/WC.kmz/WC.kmz.dep at org.jdesktop.wonderland.client.protocols.wlcontent.WlContentURLConnection.getInputStream(WlContentURLConnection.java:80) at java.net.URL.openStream(Unknown Source) at org.jdesktop.wonderland.client.cell.CellCacheBasicImpl$URLDownloader$1.call(CellCacheBasicImpl.java:938) at org.jdesktop.wonderland.client.cell.CellCacheBasicImpl$URLDownloader$1.call(CellCacheBasicImpl.java:931) ... 4 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.