BulkLoad using GenericDocumentManager is throwing ClientHandlerException

[marklogic]

BulkLoad using GenericDocumentManager is throwing ClientHandlerException

[kcoleman-marklogic]

Sravan noted the problem goes away if he comments out his JSON document. I wonder if it could be a Jackson interaction. Below is my working example of a heterogeneous batch that uses StringHandle for JSON instead of JacksonHandle, and it works fine.

    static void example4() {
        // Synthesize input content
        StringHandle jsonContent = new StringHandle(
            "{\"key\": \"value\"}").withFormat(Format.JSON);
        StringHandle xmlContent = new StringHandle(
            "<data>some xml content</data>").withFormat(Format.XML);
        String filename = new String("C:/Users/kcoleman/Downloads/nelf.jpg");
        FileHandle binaryContent = 
            new FileHandle().with(new File(filename)).withMimetype("image/jpeg");

        // Create and build up the batch
        GenericDocumentManager gdm = client.newDocumentManager();
        DocumentWriteSet batch = gdm.newWriteSet();
        batch.add("doc1.json", jsonContent);
        batch.add("doc2.xml", xmlContent);
        batch.add("doc3.jpg", binaryContent);
        gdm.write(batch);

        // Verify results
        System.out.println("doc1.json exists as: " + gdm.exists("doc1.json").getFormat().toString());
        System.out.println("doc2.xml exists as: " + gdm.exists("doc2.xml").getFormat().toString());
        System.out.println("doc3.jpg exists as: " + gdm.exists("doc3.jpg").getFormat().toString());
    }

[ehennum]

I get the same error if I do a single document write with DocumentMetadataHandle + JacksonHandle. That's also a multipart write under the covers. Write of JacksonHandle alone succeeds as does write of DocumentMetadataHandle + StringHandle.

[ehennum]

Turning off resendability in the JacksonHandle (to force digest authentication before the write) and turning on HttpClient logging shows what's going on.

When StringHandle is used, the terminating boundary for the multipart is sent:

[DEBUG] wire - >> "--Boundary_1_1277304478_1403790142585[\r][\n]"
[DEBUG] wire - >> "Content-Type: application/json[\r][\n]"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] wire - >> "5f[\r][\n]"
[DEBUG] wire - >> "{"object":{"key":"value"},"array":["item1","item2"]}[\r][\n]"
[DEBUG] wire - >> "--Boundary_1_1277304478_1403790142585--[\r][\n]"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] wire - >> "0[\r][\n]"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] wire - << "HTTP/1.1 204 Content Updated[\r][\n]"

When JacksonHandle is used, the terminating boundary is written after HttpClient has already closed the stream, triggering the error:

[DEBUG] wire - >> "--Boundary_1_1409826334_1403790513065[\r][\n]"
[DEBUG] wire - >> "Content-Type: application/json[\r][\n]"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] wire - >> "34[\r][\n]"
[DEBUG] wire - >> "{"object":{"key":"value"},"array":["item1","item2"]}"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] wire - >> "0[\r][\n]"
[DEBUG] wire - >> "[\r][\n]"
[DEBUG] DefaultClientConnection - Connection closed
[DEBUG] DefaultHttpClient - Closing the connection.
[DEBUG] DefaultClientConnection - Connection closed
[INFO] DefaultHttpClient - I/O exception (java.io.IOException) caught when processing request: Stream closed

[sammefford]

Fixed on branch dev, as part of the pojoFacade branch/commit. I configured JacksonBaseHandle to set to false both JsonGenerator.Feature.AUTO_CLOSE_TARGET and JsonParser.Feature.AUTO_CLOSE_SOURCE.

[sravanr]

Verified in the dev branch.