如何为org.jvnet.mimepull配置自定义临时目录解决空间不足问题

我在Java应用中使用org.jvnet.mimepull实现文件下载功能，处理小文件时一切正常，但下载4GB以上的大文件时，出现java.io.IOException: No space left on device错误。排查服务器后发现，容量为4GB的/tmp文件系统被大量MIME*.tmp文件占满。已知org.jvnet.mimepull会在下载过程中将临时目录作为暂存空间，请问如何配置使其使用自定义临时目录而非/tmp？

完整错误栈 #

Error handling a request: efd18e645be47f96
java.io.IOException: No space left on device
    at java.base/java.io.RandomAccessFile.writeBytes(Native Method)
    at java.base/java.io.RandomAccessFile.write(RandomAccessFile.java:559)
    at org.jvnet.mimepull.WeakDataFile.writeTo(WeakDataFile.java:122)
    at org.jvnet.mimepull.DataFile.writeTo(DataFile.java:95)
    at org.jvnet.mimepull.FileData.<init>(FileData.java:57)
    at org.jvnet.mimepull.FileData.createNext(FileData.java:91)
    at org.jvnet.mimepull.Chunk.createNext(Chunk.java:64)
    at org.jvnet.mimepull.DataHead.addBody(DataHead.java:87)
    at org.jvnet.mimepull.MIMEPart.addBody(MIMEPart.java:243)
    at org.jvnet.mimepull.MIMEMessage.makeProgress(MIMEMessage.java:270)
    at org.jvnet.mimepull.MIMEMessage.parseAll(MIMEMessage.java:189)
    at org.jvnet.mimepull.MIMEMessage.getAttachments(MIMEMessage.java:115)
    at org.glassfish.jersey.media.multipart.internal.MultiPartReaderClientSide.getMimeParts(MultiPartReaderClientSide.java:272)
    at org.glassfish.jersey.media.multipart.internal.MultiPartReaderClientSide.readMultiPart(MultiPartReaderClientSide.java:231)
    at org.glassfish.jersey.media.multipart.internal.MultiPartReaderServerSide.readMultiPart(MultiPartReaderServerSide.java:91)
    at org.glassfish.jersey.media.multipart.internal.MultiPartReaderClientSide.readFrom(MultiPartReaderClientSide.java:183)
    at org.glassfish.jersey.media.multipart.internal.MultiPartReaderClientSide.readFrom(MultiPartReaderClientSide.java:93)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.invokeReadFrom(ReaderInterceptorExecutor.java:256)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:235)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:155)
    at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundReadFrom(MappableExceptionWrapperInterceptor.java:74)
    at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:155)
    at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1085)
    at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:874)
    at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:808)
    at org.glassfish.jersey.server.ContainerRequest.readEntity(ContainerRequest.java:234)
    at org.glassfish.jersey.media.multipart.internal.FormDataParamValueFactoryProvider$ValueFactory.getEntity(FormDataParamValueFactoryProvider.java:126)
    at org.glassfish.jersey.media.multipart.internal.FormDataParamValueFactoryProvider$FormDataParamValueFactory.provide(FormDataParamValueFactoryProvider.java:280)
    at org.glassfish.jersey.server.spi.internal.ParamValueFactoryWithSource.provide(ParamValueFactoryWithSource.java:71)
    at org.glassfish.jersey.server.spi.internal.ParameterValueHelper.getParameterValues(ParameterValueHelper.java:90)
    at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$AbstractMethodParamInvoker.getParamValues(JavaResourceMethodDispatcherProvider.java:127)
    at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
    at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
    at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
    at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
    at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
    at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
    at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
    at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
    at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)

解决方案 #

方法1：通过系统属性全局配置 #

org.jvnet.mimepull支持通过系统属性指定临时目录，有两种实现方式：

• 启动时添加JVM参数：

-Dmimepull.tmpdir=/path/to/your/custom/temp/dir

• 代码中提前设置（需在mimepull初始化前执行）：

System.setProperty("mimepull.tmpdir", "/path/to/your/custom/temp/dir");

方法2：针对Jersey Multipart的专属配置 #

从错误栈可看出你使用了Jersey的Multipart扩展，可直接通过Jersey配置项指定临时目录：

• Java代码配置：

import org.glassfish.jersey.media.multipart.MultiPartFeature;
import org.glassfish.jersey.media.multipart.internal.MultiPartProperties;
import org.glassfish.jersey.server.ResourceConfig;

// 服务器端配置示例
ResourceConfig config = new ResourceConfig();
config.register(MultiPartFeature.class);
// 设置自定义临时目录
config.property(MultiPartProperties.MULTIPART_TEMP_DIR, "/path/to/your/custom/temp/dir");

• Web.xml配置（适用于Web应用）：

<servlet>
    <servlet-name>Jersey Servlet</servlet-name>
    <servlet-class>org.glassfish.jersey.servlet.ServletContainer</servlet-class>
    <init-param>
        <param-name>jersey.config.server.provider.classnames</param-name>
        <param-value>org.glassfish.jersey.media.multipart.MultiPartFeature</param-value>
    </init-param>
    <init-param>
        <param-name>jersey.config.server.media.multipart.tempDir</param-name>
        <param-value>/path/to/your/custom/temp/dir</param-value>
    </init-param>
</servlet>

方法3：自定义DataFileFactory（高级灵活控制） #

如果需要更精细的临时文件管理逻辑，可自定义DataFileFactory：

import org.jvnet.mimepull.DataFile;
import org.jvnet.mimepull.DataFileFactory;
import java.io.File;

public class CustomTempFileFactory implements DataFileFactory {
    private final String tempDirPath;

    public CustomTempFileFactory(String tempDirPath) {
        this.tempDirPath = tempDirPath;
        // 确保目录存在，不存在则创建
        File tempDir = new File(tempDirPath);
        if (!tempDir.exists()) {
            tempDir.mkdirs();
        }
    }

    @Override
    public DataFile createDataFile(String prefix, String suffix) {
        // 指定自定义目录创建临时文件
        return new DataFile(prefix, suffix, new File(tempDirPath));
    }
}

// 在应用初始化时设置自定义工厂
org.jvnet.mimepull.MIMEMessage.setDataFileFactory(new CustomTempFileFactory("/path/to/your/custom/temp/dir"));

注意事项 #

• 确保自定义临时目录有足够的磁盘空间，且应用进程拥有读写权限
• 正常情况下，mimepull会在MIME消息处理完成后自动删除临时文件；若应用异常终止，可能会残留临时文件，建议定期清理
• 集群部署时，若需要共享临时文件，可使用网络共享存储；否则每个节点配置独立的临时目录即可

内容的提问来源于stack exchange，提问作者Michael