I understand that this error is the result of WSA not being able to understand or determine an error on the page, and so it gives up. Please advise... full detail below...

java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.net.www.http.ChunkedInputStream.readAheadBlocking(Unknown Source)
at sun.net.www.http.ChunkedInputStream.readAhead(Unknown Source)
at sun.net.www.http.ChunkedInputStream.read(Unknown Source)
at java.io.FilterInputStream.read(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(Unknown Source)
at com.agilemind.commons.io.IOUtils.readBytes(IOUtils.java:156)
at com.agilemind.commons.io.URLPageReader.a(URLPageReader.java:82)
at com.agilemind.commons.io.URLPageReader.getContent(URLPageReader.java:62)
at com.agilemind.commons.io.cache.a.retrieve(a.java:1)
at com.agilemind.commons.io.cache.a.retrieve(a.java:2)
at com.agilemind.commons.io.cache.Cache.get(Cache.java:11)
at com.agilemind.commons.io.cache.CachedPageReader.getContent(CachedPageReader.java:7)
at com.agilemind.commons.io.PageReader.getContent(PageReader.java:32)
at com.agilemind.commons.io.PageReader.readPage(PageReader.java:38)
at com.agilemind.commons.io.PageReader.readPage(PageReader.java:24)
at com.agilemind.commons.io.PageReader.readPage(PageReader.java:19)
at com.agilemind.commons.io.PageReader.readPage(PageReader.java:12)
at com.agilemind.commmons.io.searchengine.analyzers.fb.a(fb.java:42)
at com.agilemind.commmons.io.searchengine.analyzers.fb.check(fb.java:12)
at com.agilemind.commmons.io.searchengine.analyzers.c.a(c.java:4)
at com.agilemind.commmons.io.searchengine.analyzers.c.worker(c.java:5)
at com.agilemind.commons.io.impl.Proxifier.query(Proxifier.java:9)
at com.agilemind.commmons.io.searchengine.analyzers.e.check(e.java:4)
at com.agilemind.sitescan.util.SiteScanLinkAnalyzerCache$SearchEngineFactorCache.a(SiteScanLinkAnalyzerCache.java:6)
at com.agilemind.sitescan.util.SiteScanLinkAnalyzerCache$SearchEngineFactorCache.retrieve(SiteScanLinkAnalyzerCache.java:2)
at com.agilemind.commons.io.cache.c.retrieve(c.java:3)
at com.agilemind.commons.io.cache.c.retrieve(c.java:1)
at com.agilemind.commons.io.cache.Cache.get(Cache.java:11)
at com.agilemind.commons.io.cache.URLInfoCache.get(URLInfoCache.java:4)
at com.agilemind.sitescan.util.operations.f.execute(f.java:7)
at com.agilemind.commons.application.modules.concurrent.util.operations.Operation.executeOperation(Operation.java:32)
at com.agilemind.commons.application.modules.concurrent.util.c.run(c.java:4)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at com.agilemind.commons.util.concurrent.a.a(a.java:7)
at com.agilemind.commons.util.concurrent.a.run(a.java:12)
at java.lang.Thread.run(Unknown Source)

Hi Linky,

I had the same problem, that cantwebsteve mentioned above - unfortunately twice!

The first time I ran V3 of web-auditor, the software crashed out at approximately 25,000 URLs (pulling just the default data) and the second time it crashed out at 22414 URLs (without pulling any data i.e. ONLY URLs).

The first time (approx. 15 hours), the "out of memory message" popped up saying that software had to be closed.

The second time, the software just stopped processing data after two hours - it got stuck, it seems (i.e. at 7 hours, it was on the same 5 tasks, that it was on at 2 hours or so).
I stopped the process and pushed finish - which after 10 minutes led to the pop-up "out of memory" message again!

Any idea on how this problem can be fixed, so that websites with a larger number of URLs / Pages can be checked?

Thanks and cheers, Asiaplay


PS: My computer was at 76% free space and the CPU at 25 to 30% - so it seems there is a bug in the software itself and not a lack of PC resources!