Maximum file sizes

Hi,

when reading the documentation/FAQ, I can see there are three options when uploading files.

Small Documents: The Web Service API has an Attachment class that consists of meta-data about the document and a byte array holding the contents. As such, the entire contents must be read into memory when uploading or downloading documents. The attachment object is created and passed in as a parameter to the method.
Large Documents (MTOM client): A client that supports MTOM must use the *Context() methods to first store the meta-data of the operation on the server. Then the ContentService is used to stream the contents to/from the Livelink server. See the example in the Client Guide.
Large Documents (HTTP client): A client that does not support MTOM must use the HTTP interface for streaming documents. As in the MTOM client, the client must use the *Context() methods to first store the meta-data of the operation on the server. Then the HTTP servlet (Java) or HTTP Handler (.NET) is used to stream the contents to/from the Livelink server. See the example in the Client Guide.

What is the actual range of small/large?

For instance, when I am uploading documents via webservices of 1MB, all goes fine, but when I try to upload a document/file of around 5MB, I get the following exception:

javax.xml.ws.WebServiceException: java.io.IOException: Error writing to server

at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:258)

at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:151)
        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:88)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
        at com.sun.xml.ws.client.Stub.process(Stub.java:248)
        at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:134)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:244)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:224)
        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:117)
        at $Proxy40.uploadContent(Unknown Source)
        at com.opentext.livelink.module.MultiUploadApplet$FileUploadTask.run(MultiUploadApplet.java:346)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: Error writing to server
        at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:438)
        at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:450)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:981)
        at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
        at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:221)
        ... 14 more

I assume this has something to do with file size ?

Thanks and regards,

Coen Damen (Logica)

Find more posts tagged with

Comments

Sjaak_Hoeijenbos

By the way, I am using the exact example from the guidelines to upload large files using MTOM.

Only small files succeed using this code though.

Regards,

Coen

sgrasley

Hi, Coen.

Do you have the web services deployed under IIS or Tomcat? Do you have any monthly patches installed for Livelink?

Thanks,

Scott

sgrasley

Also, what exception are you seeing on the server?

Thanks,

Scott

Sjaak_Hoeijenbos

Hi Scott,

I am using Netbeans IDE 6.7.1 using VMware. The VMware image contains livelink 9.7.

I run a Java Applet via Netbeans' AppletViewer, I can deploy to an IIS but this should make no difference as I am directly connecting to the livelink server endpoints. The "small files upload" works fine using the (non-deployed) applet and I can connect to each endpoint.

The livelink knowzone/log folder does not show me any information on the webservice calls. I checked each file's modification date and inspected those files.

I tried to upgrade the client to java 6. The livelink server is running on java 5.

Regards,

Coen Damen (Logica)

Sjaak_Hoeijenbos

I also upgraded to the last version of jax-ws, which gave me the same exception

javax.xml.ws.WebServiceException: java.io.IOException: Error writing to server
        at com.sun.xml.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:212)
        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:162)
        at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:94)
        at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:116)
        at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
        at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
        at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
        at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
        at com.sun.xml.ws.client.Stub.process(Stub.java:222)
        at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
        at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
        at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
        at $Proxy40.uploadContent(Unknown Source)
        at com.opentext.livelink.module.MultiUploadApplet$FileUploadTask.run(MultiUploadApplet.java:348)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: Error writing to server
        at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:453)
        at sun.net.www.protocol.http.HttpURLConnection.writeRequests(HttpURLConnection.java:465)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1047)
        at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
        at com.sun.xml.ws.transport.http.client.HttpClientTransport.readResponseCodeAndMessage(HttpClientTransport.java:209)
        ... 15 more.

sgrasley

Hi, Coen.

Are you using Livelink 9.7.0 or Livelink 9.7.1? Do you have any monthly patches installed? Could you please elaborate on how you've deployed the web services?

Thanks,

Scott

Gavin_Harte

We have Livelink 9.7.1. installed.

I should check for the patches.

sgrasley

Where have you deployed Enterprise Web Services? Tomcat or IIS?

Thanks,

Scott

Sjaak_Hoeijenbos

Hi Scott,

we were able to solve the issue by modifying the web.config accordingly:

Regards,

Coen Damen (Logica)

sgrasley

Thanks for the update, Coen.

Scott