Jakarta EE 10多租户场景下如何用拦截器自动关闭EntityManager

一、自动关闭EntityManager：完善拦截器的finally块 #

当前拦截器仅实现了EntityManager的打开逻辑，只需在finally块中调用关闭方法，即可确保无论业务方法执行成功还是抛出异常，EntityManager都会被自动关闭。同时需要修复Stateless EJB池化导致的线程安全问题：

public class ServiceInterceptor {

    @AroundInvoke
    public Object handleEntityManager(InvocationContext ctx) throws Exception {
        BaseService service = (BaseService) ctx.getTarget();
        try {
            service.openEntityManager();
            return ctx.proceed();
        } finally {
            service.closeEntityManager();
            // 重置成员变量，避免EJB实例复用时的线程冲突
            service.entityManager = null;
        }
    }
}

二、修复核心线程安全隐患 #

当前BaseService将entityManager作为成员变量存储，而Stateless EJB是池化复用的，多个请求会共享同一个EJB实例，必然导致EntityManager的线程安全问题。建议改为ThreadLocal存储，保证每个线程拥有独立的EntityManager：

public class BaseService extends BaseBean {

    @Resource
    private SessionContext context;

    @PersistenceUnit
    private EntityManagerFactory entityManagerFactory;

    // ThreadLocal存储每个线程独立的EntityManager
    private final ThreadLocal<EntityManager> entityManagerHolder = new ThreadLocal<>();

    public void openEntityManager() {
        if (entityManagerHolder.get() == null) {
            String clientIdentifier = getClientIdentifierForCurrentUser();
            final MultiTenantResolver tenantResolver = (MultiTenantResolver) ((SessionFactoryImplementor) entityManagerFactory).getCurrentTenantIdentifierResolver();
            tenantResolver.setTenantIdentifier(clientIdentifier);
            EntityManager em = entityManagerFactory.createEntityManager();
            entityManagerHolder.set(em);
        }
    }

    public void closeEntityManager() {
        EntityManager em = entityManagerHolder.get();
        if (em != null && em.isOpen()) {
            em.close();
        }
        // 清理ThreadLocal引用，防止内存泄漏
        entityManagerHolder.remove();
    }

    // 提供业务层获取EntityManager的方法
    protected EntityManager getEntityManager() {
        return entityManagerHolder.get();
    }
}

三、更优的EntityManager注入方案：CDI生产者 #

通过CDI生产者方法实现EntityManager的动态创建与生命周期自动管理，业务层无需继承BaseService，直接依赖注入即可，更符合Jakarta EE的设计理念：

1. 编写CDI生产者类 #

@ApplicationScoped
public class EntityManagerProducer {

    @PersistenceUnit
    private EntityManagerFactory entityManagerFactory;

    @Resource
    private SessionContext sessionContext;

    @Produces
    @RequestScoped // 每个请求创建独立的EntityManager
    public EntityManager createEntityManager() {
        String clientIdentifier = getClientIdentifierForCurrentUser();
        final MultiTenantResolver tenantResolver = (MultiTenantResolver) ((SessionFactoryImplementor) entityManagerFactory).getCurrentTenantIdentifierResolver();
        tenantResolver.setTenantIdentifier(clientIdentifier);
        return entityManagerFactory.createEntityManager();
    }

    // CDI自动调用该方法销毁EntityManager
    public void destroyEntityManager(@Disposes EntityManager em) {
        if (em != null && em.isOpen()) {
            em.close();
        }
    }

    // 复用原有租户ID获取逻辑
    private String getClientIdentifierForCurrentUser() {
        Principal principal = sessionContext.getCallerPrincipal();
        return getTenantIdByUsername(principal.getName());
    }

    private String getTenantIdByUsername(String username) {
        // 实现租户ID与用户名的映射逻辑
        return "";
    }
}

2. 业务层直接注入使用 #

@Stateless
public class UserService {

    @Inject
    private EntityManager entityManager;

    public User getUserById(Long id) {
        return entityManager.find(User.class, id);
    }
}

四、优化多租户Resolver设计 #

避免手动设置租户标识符，让Resolver自动从上下文获取租户ID，代码更简洁：

public class MultiTenantResolver implements CurrentTenantIdentifierResolver {

    @Inject
    private SecurityContext securityContext;

    @Override
    public String resolveCurrentTenantIdentifier() {
        Principal principal = securityContext.getCallerPrincipal();
        if (principal == null) {
            throw new IllegalStateException("用户未登录");
        }
        return getTenantIdByUsername(principal.getName());
    }

    @Override
    public boolean validateExistingCurrentSessions() {
        return true;
    }

    private String getTenantIdByUsername(String username) {
        // 实现租户ID映射逻辑
        return "";
    }
}

在persistence.xml中配置该Resolver：

<persistence-unit name="MyPU" transaction-type="JTA">
    <!-- 其他配置项 -->
    <properties>
        <property name="hibernate.multiTenancy" value="DATABASE"/>
        <property name="hibernate.tenant_identifier_resolver" value="com.yourpackage.MultiTenantResolver"/>
    </properties>
</persistence-unit>

五、Wildfly 29适配建议 #

• 若使用JTA事务，可结合@PersistenceContext注入EntityManager，配合上述自动Resolver，由容器管理EntityManager生命周期。
• 针对多租户场景，可配置Wildfly的多数据源池，或使用Hibernate的多租户连接提供者优化数据库连接管理。

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