Kubernetes中JPA EntityManagerFactory初始化失败：文件必须存在错误

运行一个包含读写两个独立数据源的应用，本地运行无任何错误，但部署到Kubernetes集群后，出现JPA EntityManagerFactory初始化失败的错误。

Failed to initialize JPA EntityManagerFactory: File must exist : /proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/1/cwd/proc/self/task/7/cwd/proc/sys/net/ipv4/tcp_autocorking

Building JPA container EntityManagerFactory for persistence unit 'default'

PersistenceUnitInfo [
    name: default
    persistence provider classname: null
    classloader: org.springframework.boot.loader.LaunchedURLClassLoader@8bd1b6a
    excludeUnlistedClasses: true
    JTA datasource: null
    Non JTA datasource: HikariDataSource (null)
    Transaction type: RESOURCE_LOCAL
    PU root URL: file:/Users/berkin.akaydin/IdeaProjects/sendingmethods-api/target/sendingmethods-api-XXX.XXX.jar
    Shared Cache Mode: UNSPECIFIED
    Validation Mode: AUTO
    Jar files URLs []
    Managed classes names [
        com.berkin.sendingmethodsapi.domain.connection.persistance.model.write.OrderEntity
        com.berkin.sendingmethodsapi.domain.connection.persistance.model.write.TbbLogEntity
        com.berkin.sendingmethodsapi.domain.connection.persistance.model.write.WriteConnectionEntity
        ]
    Mapping files names []
    Properties []
]

@Configuration
@EnableTransactionManagement
@EnableJpaRepositories(
    basePackages = ["com.berkin.sendingmethodsapi.domain.connection.persistance.repository.read"],
    entityManagerFactoryRef = "readEntityManagerFactory",
    transactionManagerRef = "readTransactionManager"
)
class readConfiguration {

    @Bean("readDataSourceProperties")
    @ConfigurationProperties("spring.datasource.read")
    fun readDataSourceProperties() = DataSourceProperties()

    @Bean("readDataSource")
    fun readDataSource(
        @Qualifier("readDataSourceProperties") readDataSourceProperties: DataSourceProperties
    ): DataSource =
        readDataSourceProperties.initializeDataSourceBuilder().build()

    @Bean("readTransactionManager")
    fun readTransactionManager(
        @Qualifier("readEntityManagerFactory") readEntityManagerFactory: LocalContainerEntityManagerFactoryBean
    ) = readEntityManagerFactory.`object`?.let { JpaTransactionManager(it) }

    @Bean("readEntityManagerFactory")
    fun readEntityManagerFactory(
        @Qualifier("readDataSource") dataSource: DataSource
    ): LocalContainerEntityManagerFactoryBean {
        val entityManagerFactory = LocalContainerEntityManagerFactoryBean()
        entityManagerFactory.dataSource = dataSource
        entityManagerFactory.setPackagesToScan("com.berkin.sendingmethodsapi.domain.connection.persistance.model.read")
        entityManagerFactory.persistenceProvider = HibernatePersistenceProvider()
        entityManagerFactory.jpaVendorAdapter = HibernateJpaVendorAdapter()
        return entityManagerFactory
    }
}

jpa:
    open-in-view: false
    hibernate.ddl-auto: validate
    database: MySQL

FROM amazoncorretto:17-alpine as builder
ARG JAR_FILE=*.jar
COPY ${JAR_FILE} application.jar
RUN java -Djarmode=layertools -jar application.jar extract

FROM amazoncorretto:17-alpine
COPY --from=builder dependencies/ ./
COPY --from=builder snapshot-dependencies/ ./
COPY --from=builder spring-boot-loader/ ./
COPY --from=builder application/ ./
ENTRYPOINT ["java", "org.springframework.boot.loader.JarLauncher"]

错误核心是路径出现无限循环嵌套，推测是Hibernate在Alpine Linux环境下解析类路径时，误将/proc下的特殊文件当作普通文件处理，导致路径解析进入死循环。以下是可行解决方向：

1. 更换基础镜像 #

Alpine使用musl libc，与GNU libc存在差异，部分JVM应用会出现文件系统相关问题。建议切换为基于GNU libc的Corretto镜像：

FROM amazoncorretto:17 as builder
# 后续步骤保持不变

FROM amazoncorretto:17
# 后续步骤保持不变

2. 显式排除Hibernate类路径扫描规则 #

在application.properties中添加配置，强制Hibernate跳过/proc目录扫描：

spring.jpa.properties.hibernate.classpath.excludes=/proc/**

或在EntityManagerFactory配置中手动添加属性：

entityManagerFactory.setJpaProperties(Properties().apply {
    put("hibernate.classpath.excludes", "/proc/**")
})

3. 调整Spring Boot类加载器配置 #

容器中文件结构可能导致类路径解析逻辑变化，可在启动命令中添加JVM参数调整行为：
修改Dockerfile的ENTRYPOINT：

ENTRYPOINT ["java", "-Dspring.boot.classpath.index=none", "org.springframework.boot.loader.JarLauncher"]

4. 检查K8S数据源配置完整性 #

确认K8S的ConfigMap或Secret是否正确注入了所有数据源参数（如spring.datasource.read.url、username、password），配置缺失可能触发异常路径解析。

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