This stack trace is on the client side trying to send the message, not on the
server side. The cxf.xml and such you sent is for the server side.
What is the code you are using in testVideoUpload?
I think the key line is:
org.apache.cxf.io.CachedOutputStream.writeCacheTo(CachedOutputStream.java:286)
It only gets there if:
if (totalLength < limit || limit == -1) {
Thus, it looks like the configuration of the LoggingOutInterceptor (or logging
feature) is setting a very high limit (or no limit).
The default limit on the Logging interceptors is 100K. I think you have to
go out of your way to set it to something else. Definitely check your client
code.
Dan
On Thu December 17 2009 6:28:50 am surajchhetry 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:1
> 00) 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:3
> 34) at
> org.apache.cxf.io.CachedOutputStream.writeCacheTo(CachedOutputStream.java:2
> 86) at
> org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback.onClose(Lo
> ggingOutInterceptor.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$MessageSenderEndingInte
> rceptor.handleMessage(MessageSenderInterceptor.java:62) at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChai
> n.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(VideoWebServiceTest
> er.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(AbstractInvok
> >>er. 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
