Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-21409

Update org.jboss.as.jpa.container.NonTxEmCloser.popCall to check for null container managed stateless session/entity manager

XMLWordPrintable

      I noticed the following server output while running some tests with TRACE logging enabled for "org.jboss.as.jpa" and I think we should add a null check for null entity manager + null stateless session in org.jboss.as.jpa.container.NonTxEmCloser.popCall

      2026-01-29 11:02:32,149 INFO [stdout] (default task-2) ran test
      2026-01-29 11:02:32,150 TRACE [org.jboss.as.jpa] (default task-2) Could not close (non-transactional) container managed stateless session. This shouldn't impact application functionality (only read operations occur in non-transactional mode): java.lang.NullPointerException: Cannot invoke "java.lang.AutoCloseable.close()" because "statelessSession" is null
      at org.jboss.as.jpa@40.0.0.Beta1-SNAPSHOT//org.jboss.as.jpa.container.NonTxEmCloser.popCall(NonTxEmCloser.java:61)
      at org.jboss.as.jpa@40.0.0.Beta1-SNAPSHOT//org.jboss.as.jpa.interceptor.WebNonTxEmCloserAction.teardown(WebNonTxEmCloserAction.java:32)
      at org.wildfly.extension.undertow@40.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1439)
      at org.wildfly.extension.undertow@40.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1437)
      at org.wildfly.extension.undertow@40.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1437)
      at org.wildfly.extension.undertow@40.0.0.Beta1-SNAPSHOT//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1437)
      at io.undertow.servlet@2.0.0.Alpha2//io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:251)
      at io.undertow.servlet@2.0.0.Alpha2//io.undertow.servlet.handlers.ServletInitialHandler.lambda$new$1(ServletInitialHandler.java:99)
      at io.undertow.core@2.4.0.Alpha1//io.undertow.server.Connectors.executeRootHandler(Connectors.java:418)
      at io.undertow.core@2.4.0.Alpha1//io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:901)
      at org.jboss.threads@3.9.2//org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
      at org.jboss.threads@3.9.2//org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2651)
      at org.jboss.threads@3.9.2//org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2630)
      at org.jboss.threads@3.9.2//org.jboss.threads.EnhancedQueueExecutor.runThreadBody(EnhancedQueueExecutor.java:1622)
      at org.jboss.threads@3.9.2//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1589)
      at org.jboss.xnio@3.8.16.Final//org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1282)
      at java.base/java.lang.Thread.run(Thread.java:1474)

              smarlow1@redhat.com Scott Marlow
              smarlow1@redhat.com Scott Marlow
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: