java - WSDL 第一个启用 MTOM 的 cxf 2.7 Web 服务客户端导致大型附件出现 Java 堆空间错误

Question

我正在使用 MTOM 的 CXF2.7.7 构建一个 WSDL-first java web 服务。我的目的是能够通过此网络服务上传大(多个千兆字节)文件下面是我的 WSDL 的片段

 <!-- WSDL for MTOM service -->
    <wsdl:types>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 
xmlns:tns="http://objectstoreservice.example.com/" attributeFormDefault="unqualified"  
elementFormDefault="unqualified" targetNamespace="http://objectstoreservice.example.com/">
        <xs:element name="objectReqParam" type="tns:objectReqParam"/>
        <xs:element name="objectRespParam" type="tns:objectRespParam"/>
        <xs:complexType name="objectReqParam">
            <xs:sequence>
                 <xs:element minOccurs="0" name="objName" type="xs:string"/> 
                <xs:element minOccurs="0" maxOccurs="1" name="ObjData" 
type="xs:base64Binary" xmime:expectedContentTypes="application/octet-stream"/>
            </xs:sequence>
        </xs:complexType>
        <xs:complexType name="objectRespParam">
            <xs:sequence>
                <xs:element minOccurs="0" name="respCode" type="xs:string"/>
            </xs:sequence>
        </xs:complexType>
    </xs:schema>
</wsdl:types>
<wsdl:message name="objectUploadRequest">
    <wsdl:part name="objectReqParam" element="tns:objectReqParam">
</wsdl:part>
</wsdl:message>
<wsdl:message name="objectUploadResponse">
    <wsdl:part name="objectRespParam" element="tns:objectRespParam">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="ObjectStoreService">
    <wsdl:operation name="uploadObject">
        <wsdl:input name="objectUploadRequest" message="tns:objectUploadRequest"/>
        <wsdl:output name="objectUploadResponse" message="tns:objectUploadResponse"/>
    </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ObjectStoreServiceServiceSoapBinding" type="tns:ObjectStoreService">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="uploadObject">
        <soap:operation soapAction="" style="document"/>
        <wsdl:input name="objectUploadRequest">
            <soap:body use="literal"/>
        </wsdl:input>
        <wsdl:output name="objectUploadResponse">
            <soap:body use="literal"/>
        </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:service name="ObjectStoreServiceService">
    <wsdl:port name="ObjectStoreServicePort"         
              binding="tns:ObjectStoreServiceServiceSoapBinding">
        <soap:address location="http://localhost:9090/ObjectStoreServicePort"/>
    </wsdl:port>
</wsdl:service>
    </wsdl:definitions>

我的目的是使用 MTOM(从元素 type="xs:base64Binary"xmime:expectedContentTypes="application/octet-stream 可以明显看出)通过此服务上传对象。

我还配置了我的 jax WS 端点以使用 MTOM，如下面的服务器端 Spring 配置文件片段所示

<beans xmlns="http://www.springframework.org/schema/beans" 
... />
<jaxws:endpoint xmlns:objectstore="http://objectstoreservice.example.com/"
    id="ObjectStoreServiceHTTP" address="http://localhost:9090/ObjectStoreServicePort"
    serviceName="objectstore:ObjectStoreServiceService"   
endpointName="objectstore:ObjectStoreServiceEndpoint"
    implementor="com.example.objectstoreservice.server.ObjectStoreServiceImpl">
    <jaxws:properties>
    <!-- MTOM properties -->
    <entry key="mtom-enabled" value="true"/>
    <entry key="attachment-directory" value="/tmp/mtomattachments"/>
            <entry key="attachment-memory-threshold" value="100000"/>
    </jaxws:properties>
</jaxws:endpoint>
</beans>

同样，我也将我的 jax-ws 客户端配置为使用 MTOM，如下面的客户端 spring 配置文件所示

<beans xmlns="http://www.springframework.org/schema/beans ..../>
<jaxws:client id="objectStoreService" 
    serviceName="objectstore:ObjectStoreServiceService" 
    endpointName="objectstore:ObjectStoreServiceEndpoint"
    address="http://localhost:9090/ObjectStoreServicePort" 
    serviceClass="com.example.objectstoreservice.ObjectStoreService">
    <jaxws:properties>
    <!-- MTOM properties -->
    <entry key="mtom-enabled" value="true"/>
    <entry key="attachment-memory-threshold" value="100000"/>
    <entry key="attachment-directory" value="/tmp/mtomattachments"/>
    <entry key="javax.xml.ws.client.connectionTimeout" 
                            value="10000000" />
            <entry key="javax.xml.ws.client.requestTimeout" 
                            value="10000000" />
    <jaxws:properties>
</jaxws:client>

我还在下面为客户端提供了我的 Java 代码的相关片段

/* ---      Web-service client 
*************************************************************************** */

package com.example.objectstoreservice.client;

import java.util.List;
import java.awt.Image;
import java.io.ByteArrayInputStream;
import java.io.File;

import java.io.InputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
import javax.activation.DataHandler;
import javax.activation.FileDataSource;
import javax.xml.namespace.QName;


import com.example.objectstoreservice.ObjectStoreService;
import com.example.objectstoreservice.ObjectReqParam;
import com.example.objectstoreservice.ObjectRespParam;
import javax.xml.ws.Binding;
import javax.xml.ws.BindingProvider;

public final class ObjectStoreServiceTester {

ObjectStoreService objectStoreService;
Binding binding ;

public ObjectStoreService getObjectStoreService() {
    return objectStoreService;
}

// I haven't shown the code that sets the port object - objectStoreService 
// Take my worrd for it - I have the right port object 
public void setObjectStoreService(ObjectStoreService objectStoreService) {
    this.objectStoreService = objectStoreService;
}

public void enableMTOM () {
 binding = ((BindingProvider)objectStoreService).getBinding();
 ((SOAPBinding)binding).setMTOMEnabled(true);

}


public void testObjectStoreService() 
{
            enableMTOM();

            System.out.println("Now uploading a data file to  service");

    ObjectReqParam objReqParam = new ObjectReqParam() ;
    objReqParam.setObjName("File");
            String fileName="C:/root/opt/files/ToSend.jpg";
            FileDataSource inFileDataSource=new FileDataSource(fileName);
    DataHandler dataHandler = new DataHandler(inFileDataSource);
    System.out.println("Check content-type from dataHandler : " + dataHandler.getContentType());
    System.out.println("Check obj signature from dataSource : " + dataHandler.getDataSource());
    System.out.println("Check file-name from dataSource : " + dataHandler.getDataSource().getName());

    objReqParam.setObjData(dataHandler);
    System.out.println("Now uploading file:" + fileName);
    objectStoreService.uploadObject(objReqParam);
    System.out.println("Object upload successful");


}

}

运行时 - 该客户端对于小附件运行良好，但对于大附件会出现以下错误(基于我分配的 JVM 堆空间)

** 执行 Java 类时发生异常。 null:InvokingTargetException:Java 堆空间 **

下面是完整的堆栈跟踪。 *如果您发现问题或我是否应该做一些不同的事情，请告诉我**- 顺便说一句，我看过其他一些有类似问题的帖子，想知道是否有人对大文件做过 MTOM。有没有一种方法可以显式强制它流式传输文件或强制它以小块形式发送？
*

MTOM: An exception occured while executing the Java class. null
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:217)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu 
ild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:409)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.MojoExecutionException: An exception occured
while executing the Java class. null
    at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:346)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:209)
    ... 19 more
Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:291)
    at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.OutOfMemoryError: Java heap space
    at com.sun.xml.bind.v2.util.ByteArrayOutputStreamEx.readFrom(ByteArrayOu
tputStreamEx.java:75)
    at com.sun.xml.bind.v2.runtime.unmarshaller.Base64Data.get(Base64Data.ja
va:196)
    at com.sun.xml.bind.v2.runtime.unmarshaller.Base64Data.writeTo(Base64Dat
a.java:312)
    at com.sun.xml.bind.v2.runtime.output.UTF8XmlOutput.text(UTF8XmlOutput.j
ava:312)
    at com.sun.xml.bind.v2.runtime.XMLSerializer.leafElement(XMLSerializer.j
ava:356)
    at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$PcdataImpl.
writeLeafElement(RuntimeBuiltinLeafInfoImpl.java:183)
    at com.sun.xml.bind.v2.runtime.MimeTypedTransducer.writeLeafElement(Mime
TypedTransducer.java:96)
    at com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTrans
ducedAccessorImpl.writeLeafElement(TransducedAccessor.java:256)
    at com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty.serial
izeBody(SingleElementLeafProperty.java:130)
    at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBean
InfoImpl.java:361)
    at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerialize
r.java:696)
    at com.sun.xml.bind.v2.runtime.property.SingleElementNodeProperty.serial
izeBody(SingleElementNodeProperty.java:158)
    at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(Eleme
ntBeanInfoImpl.java:161)
    at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(Eleme
ntBeanInfoImpl.java:131)
    at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(Element
BeanInfoImpl.java:333)
    at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(Element
BeanInfoImpl.java:340)
    at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(Element
BeanInfoImpl.java:76)
    at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.j
ava:494)
    at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:
323)
    at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.jav
a:251)
    at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshal
lerImpl.java:95)
    at org.apache.cxf.jaxb.JAXBEncoderDecoder.writeObject(JAXBEncoderDecoder
.java:612)
    at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.ja
va:240)
    at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:169)
    at org.apache.cxf.interceptor.AbstractOutDatabindingInterceptor.writePar
ts(AbstractOutDatabindingInterceptor.java:114)
    at org.apache.cxf.interceptor.BareOutInterceptor.handleMessage(BareOutIn
terceptor.java:68)
    at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercept
orChain.java:272)
    at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:565)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:474)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:377)
    at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:330)
    at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)

还有一件奇怪的事情如果我检查 SOAP 消息，我仍然看到附件“内联”为 base64 编码，而不是作为单独的部分...至少 CXF 日志记录向我表明了这一点...

Answer 1

这个问题是由于一些奇怪的原因，与 MTOM 相关的 spring 配置没有被拾取的结果 - 虽然我还没有弄清楚为什么 - 我可以通过以编程方式添加设置 MTOM 相关属性到我的绑定(bind)类来缓解这个问题 - 然后 MTOM 工作正常。但有一点需要注意 - 我现在取消了 https 传输(正在使用纯 http 传输)

// In My Web-service client code .... 

import javax.xml.ws.Binding;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.soap.SOAPBinding;
import com.sun.xml.ws.developer.JAXWSProperties; 

// ... REST of my code 

// After I create my Port - - did following for Enabling MTOM");
        Binding binding = ((BindingProvider)port).getBinding();
        if (binding == null) {
            System.out.println("port .getBinding  failed!!");
            System.exit(-1);
        }
        ((SOAPBinding) binding).setMTOMEnabled(true);

        if (debugFlag)
        System.out.println(" Port - setting chunking and other properties");
        //Map contextMap=((BindingProvider)port).getRequestContext();

               ((BindingProvider)port).getRequestContext().put(JAXWSProperties.HTTP_CLIENT_STREAMING_CHUNK_SIZE,32768);
            ((BindingProvider)port).getRequestContext().put(JAXWSProperties.MTOM_THRESHOLOD_VALUE,16000);
        ((BindingProvider)port).getRequestContext().put(JAXWSProperties.REQUEST_TIMEOUT,0);
        ((BindingProvider)port).getRequestContext().put(JAXWSProperties.CONNECT_TIMEOUT ,0);