It looks like you turned it on. You have the logging feature enabled, or you have explicitly added the LoggingOutInterceptor somewhere. Unless we have some mechanism that does this by default that I'm not aware of.
On Thu, Dec 17, 2009 at 7:58 AM, surajchhetry <[email protected]> wrote: > > Could you tell me how to do that? > > bimargulies wrote: >> >> Better turn off the logging interceptor. >> >> On Thu, Dec 17, 2009 at 6:28 AM, surajchhetry <[email protected]> >> wrote: >>> >>> Iam using CXF 2.2.5 version and try to upload around 5 GB and got >>> following >>> error. >>> Here is the stack trace >>> >>> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space >>> at java.util.Arrays.copyOf(Arrays.java:2882) >>> at >>> java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100) >>> at >>> java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390) >>> at java.lang.StringBuilder.append(StringBuilder.java:119) >>> at >>> org.apache.cxf.io.CachedOutputStream.writeCacheTo(CachedOutputStream.java:334) >>> at >>> org.apache.cxf.io.CachedOutputStream.writeCacheTo(CachedOutputStream.java:286) >>> at >>> org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback.onClose(LoggingOutInterceptor.java:152) >>> at >>> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:182) >>> at >>> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) >>> at >>> org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:637) >>> at >>> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) >>> at >>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) >>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:483) >>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:309) >>> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:261) >>> at >>> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) >>> at >>> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124) >>> at $Proxy57.uploadVideo(Unknown Source) >>> at >>> com.suraj.core.ws.VideoWebServiceTester.testVideoUpload(VideoWebServiceTester.java:70) >>> at >>> com.suraj.core.ws.VideoWebServiceTester.main(VideoWebServiceTester.java:44) >>> >>> >>> dkulp wrote: >>>> >>>> >>>> This error sounds like a classloader thing. Check the classpath and >>>> such >>>> for >>>> and activation jars. If you are on Java6, try removing the activation >>>> jar we >>>> ship and such and using the stuff built into the jdk. >>>> >>>> Dan >>>> >>>> >>>> On Sat November 28 2009 3:50:59 pm baeschtu baeschtu wrote: >>>>> I was getting a step forward while using the reference implementation >>>>> large_upload from https://jax-ws.dev.java.net/2.1.7/ >>>>> Now I have the following problem. (I'm using maven) >>>>> >>>>> Nov 28, 2009 9:44:32 PM org.apache.cxf.phase.PhaseInterceptorChain >>>>> doIntercept >>>>> WARNING: Application has thrown exception, unwinding now >>>>> org.apache.cxf.interceptor.Fault: loader constraint violation: loader >>>>> (instance of <bootloader>) previously initiated loading for a different >>>>> type with name "javax/activation/DataHandler" >>>>> at >>>>> org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker. >>>>> java:148) >>>>> >>>>> Any help would be appreciated! >>>>> >>>>> >>>>> >>>>> 2009/11/27 baeschtu baeschtu <[email protected]> >>>>> >>>>> > Hi list >>>>> > for a fileupload I need a mtom enabled webservice (wsdl first.) I >>>>> managed >>>>> > to write a working wsdl with wsdl2java >>>>> > When I send large binaries ~5GB I got a: >>>>> > >>>>> > WARNING: Interceptor has thrown exception, unwinding now >>>>> > org.apache.cxf.interceptor.Fault: Unmarshalling Error: Java heap >>>>> space >>>>> > >>>>> > When I check with wireshark, for small files it looks like SwA seams >>>>> to >>>>> > work: >>>>> > MIME Multipart Media Encapsulation, Type: multipart/related, >>>>> Boundary: >>>>> > "uuid:910305cf-e4c6-45cd-a0f6-4f083b49c6c4" >>>>> > >>>>> > When trying to upload large files I see only "Continuation or >>>>> non-HTTP >>>>> > traffic" and then follows the OutOfMemory exception. >>>>> > 35506 5625.427090 127.0.0.1 127.0.0.1 HTTP >>>>> Continuation >>>>> or >>>>> > non-HTTP traffic. >>>>> > >>>>> > I also have the xmime:expectedContentTypes="application/octet-stream" >>>>> in >>>>> > and DataHandlers are generated. >>>>> > Has someone a working example, or some hints? >>>>> > >>>>> > Thanks >>>>> > Bast >>>>> >>>> >>>> -- >>>> Daniel Kulp >>>> [email protected] >>>> http://www.dankulp.com/blog >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://old.nabble.com/MTOM-OutOfMemory-tp26544421p26826658.html >>> Sent from the cxf-user mailing list archive at Nabble.com. >>> >>> >> >> > > -- > View this message in context: > http://old.nabble.com/MTOM-OutOfMemory-tp26544421p26827626.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
