How to find document causing solr problems

[dhd]

Hi,

I have a test Share site to which I have uploaded a large number of test files.  I am getting the following every few seconds in catalina.out:

25-May-2012 16:02:34 org.alfresco.solr.tracker.CoreTracker trackRepository
SEVERE: Tracking failed
org.json.JSONException: Unterminated string at character 1192
        at org.json.JSONTokener.syntaxError(JSONTokener.java:413)
        at org.json.JSONTokener.nextString(JSONTokener.java:244)
        at org.json.JSONTokener.nextValue(JSONTokener.java:344)
        at org.json.JSONObject.<init>(JSONObject.java:206)
        at org.json.JSONTokener.nextValue(JSONTokener.java:347)
        at org.json.JSONObject.<init>(JSONObject.java:206)
        at org.json.JSONTokener.nextValue(JSONTokener.java:347)
        at org.json.JSONArray.<init>(JSONArray.java:125)
        at org.json.JSONTokener.nextValue(JSONTokener.java:351)
        at org.json.JSONObject.<init>(JSONObject.java:206)
        at org.alfresco.solr.client.SOLRAPIClient.getNodesMetaData(SOLRAPIClient.java:725)
        at org.alfresco.solr.tracker.CoreTracker.indexNode(CoreTracker.java:1879)
        at org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1410)
        at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:491)
        at org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
        at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Indexing is not working, and therefore those aspects of Share that rely on this are not working either.  I am guessing that there is some particular uploaded file that is causing this.  Could anyone please suggest a method by which I might locate the file?  For example, could I get more detailed information in the log?

Thanks!

[afaust]

Hello,

the best way to get to the document causing the problem is by intercepting the traffic between the repository and SOLR, and analyzing the corrupt JSON. Since all SSL certificates of the involved services are within your reach, you should have no problem decyphering the SSL protected request/response contents.

Regards
Axel