problem with the operation uploadContent in the web service ContentService

Hi,

I have a problem with the operation uploadContent in the web service ContentService, when I try to upload a file to Livelink greater than 4Mb.

I use the method Large Documents (Java) described in https://knowledge.opentext.com/knowledge/llisapi.dll/open/15628099#link13, but it generates the following error:

com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:130)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:294)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:173)
    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 $Proxy39.uploadContent(Unknown Source)
    at com.atos.servlets.Carga.doPost(Carga.java:107)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Thread.java:619)

Any idea about how to resolve it?

thanks

Find more posts tagged with

Comments

modus_ponens

I work on the same project of Jeison, and we finally discovered that the ‘Unsupported content-type’ error occurred on the client side, and was a reaction after receiving a response from the server which was encoded in html, and not in xml as a Soap message would be. The HTML response was the following:

<html><head><title>Apache Tomcat/6.0.18 - Error report</title><style></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html>

Which simply indicates an internal error in the Tomcat server during the execution of the service call. In ‘catalina.<date>.log’ it can be found then:

GRAVE: caught throwable

java.lang.OutOfMemoryError: Java heap space

at java.util.Arrays.copyOfRange(Arrays.java:3209)

at java.lang.String.<init>(String.java:216)

at java.lang.StringBuffer.toString(StringBuffer.java:585)

at com.sun.org.apache.xerces.internal.dom.TextImpl.getWholeText(TextImpl.java:157)

at com.sun.xml.ws.streaming.DOMStreamReader.next(DOMStreamReader.java:776)

at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:225)

at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:358)

at com.sun.xml.bind.v2.runtime.BridgeImpl.unmarshal(BridgeImpl.java:120)

at com.sun.xml.bind.api.Bridge.unmarshal(Bridge.java:233)

at com.sun.xml.ws.server.sei.EndpointArgumentsBuilder$DocLit.readRequest(EndpointArgumentsBuilder.java:507)

at com.sun.xml.ws.server.sei.EndpointArgumentsBuilder$Composite.readRequest(EndpointArgumentsBuilder.java:188)

at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:243)

at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)

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.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)

at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)

at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)

at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)

at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129)

at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160)

at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

So it seems a problem of memory management on server side. I have confirmed that, with a Tomcat server with a JVM working with a –Xmx256m parameter (256 M of memory), the maximum file length that can be sent without error is of 15 M approximately, and even this quantity decreases in consecutive calls. I have discovered that the problem is not from MTOM or other JAXWS related problem, because in a different project we have created JAXWS web service clients which can receive files much larger than 15 M. It seems that Livelink Web Service code on server side does not manage correctly memory allocation, and produces those ‘Java heap space’ errors.

Can you please help us? Thanks in advance.

sgrasley

First of all, let me apologize for not posting a response earlier to the initial post. Somehow it wasn't included in my email notifications.

Secondly, this is a very timely post as I've been pursuing this very problem. In JAX-WS 2.1.2 there is a bug involving MTOM and memory usage. The JAX-WS libraries included with Enterprise Web Services 9.7.1 includes a fix for this issue, but it seems there is still a problem.

I'm continuing to look into this but I'd recommend using an HTTP POST method of transferring large files.

Thanks,

Scott

modus_ponens

Thanks for your response. Can you please explain me how could I transfer a file into Livelink repository using directly a HTTP operation?

Yun_Zhang

Scott,

I have the similar issue to use the content service, but i could not even create an instance of the ContentService with error:

{"Method ContentService.UploadContent can not be reflected."}

Do you have any idea?

I am using c# .NET VS 2005 or 2008.

Thansk!

Yun

Yun_Zhang

I find this is because I am using a server without have Livelink installed as the Web services server. If I use the Livelink server as the EWS server, it will be OK. Do you think is it possible to use this kind of server as the EWS server?

Thanks!

Yun

sgrasley

Hi, Yun.

Are you asking if you can deploy the EWS web services on a server other than that which has Livelink installed? If so, you would haved to edit the Web.config or web.xml file (for .NET or Java, respectively) to point the web services at the Livelink server and port.

thanks,

Scott

sgrasley

A web search seems to suggest that that error could occur if you try using a .NET 1.1 or 2.0 client to access a WCF web service.

Yun_Zhang

Thank you Scott. It seems I could not use the content service with document manage service together. What I did now is use the Document management service only. Now I can upload a document with 4 mb, do you think I have to use the content service to upload a document larger tahn 4 mb? If so, do you have some sample code to do it. The posted sample code for .NET part is not so clear to me.

Thanks!

Yun

sgrasley

Hi, Yun.

I'm not sure of the problem you're experiencing with the ContentService. Can you provide a sample of your code? If you're using the DocumentManagement service only, you'll find that there's a limit to the size of document you can transfer before you run out of memory.

For the 4 MB limit, this is the default limitation for the size of requests for ASP.NET. You can configure this in the Web.config file for les-services:

    <system.web>
        <httpRuntime maxRequestLength="65536"/>
    </system.web>

Thanks,

Scott

sgrasley

The documentation here discusses using an HTTP POST operation to upload large documents.

https://knowledge.opentext.com/knowledge/llisapi.dll/open/15628099#link14

Scott

Kyle_Swidrovich

Attached is sample code written by myself outlining a CreateDocument request using the MTOM context method.

Please make special note of the notes in the headers outlining necessary changes to the WCF configuration.

Philippe Gauvin

For the httpUpload method in JAVA, you have to look at the documentation of OCS 10, the code is the same as 971. With this method, you can upload large file (tested with 1G file for me) without the Java Heap Size exception. I opened a ticket at OpenText support for the httpUpload in Java and they said "there is not an example for Java and HTTP uploading unfortunately". That's OT!!

knowledge.opentext.com/knowledge/llisapi.dll/fetch/2001/15080935/-15106263/15106294/16376487/17990637/17990649/17990650/18047148/clientguide.html#content.http

Kobi_Kohavi

hi,

i have used your code and was able to upload a txt file.

but for some Reason i can't find the uploaded file by it's name....

how can i find it?

Guy_Pomerleau

does the code could work with "Windows authentication" and "livelink directory services" because in your code you use a "username" and "password"

Me Ra

Kyle,

I have followed your example as well as the upload example for Content Web Services but i am still unable to upload files greater than 4MB. I am getting the following error on contentserviceclient.UploadContent:
"The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error."

Are you familiar if any changes are required on the actual server hosting CWS?

Quoted Kyle Swidrovich on 12/09/2015 12:12 PM:

Attached is sample code written by myself outlining a CreateDocument request using the MTOM context method.

Please make special note of the notes in the headers outlining necessary changes to the WCF configuration.

Guy_Pomerleau

Look at my answer here in a previous post: https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=48523367&objAction=viewincontainer&ShowReplyEntry=48665921#forum_topic_48665921

You have to look at you IIS configuration and CWS config. two parameter you need to look at: maxRequestLength and maxAllowedContentLength