[jboss-jira] [JBoss JIRA] (WFLY-5212) IllegalStateException: no transaction associated with thread after undeploy

[Michal Vinkler (JIRA)]

Michal Vinkler created WFLY-5212:
------------------------------------

             Summary: IllegalStateException: no transaction associated with thread after undeploy
                 Key: WFLY-5212
                 URL: https://issues.jboss.org/browse/WFLY-5212
             Project: WildFly
          Issue Type: Bug
          Components: Clustering
            Reporter: Michal Vinkler
            Assignee: Paul Ferraro
            Priority: Minor


Intermittent failure, so far seen in only this scenario:
ejb-ejbservlet-undeploy-dist-sync

Setup: 4 node cluster, one node at time undeploys application (clusterbench-ee7.ear), while standalone clients keep calling the application.

Right after undeploying the application servers perf19,20,21 logged this error approx. 50 times:
{code}
[JBossINF] [0m[31m18:37:43,800 ERROR [io.undertow.request] (default task-111) UT005023: Exception handling request to /clusterbench/ejbservlet: java.lang.IllegalStateException: no transaction associated with thread
[JBossINF] 	at org.infinispan.transaction.tm.DummyBaseTransactionManager.rollback(DummyBaseTransactionManager.java:94)
[JBossINF] 	at org.wildfly.clustering.ee.infinispan.ActiveTransactionBatch.discard(ActiveTransactionBatch.java:57)
[JBossINF] 	at org.wildfly.clustering.web.undertow.session.DistributableSessionManager.getSession(DistributableSessionManager.java:131)
[JBossINF] 	at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:725)
[JBossINF] 	at io.undertow.servlet.spec.HttpServletRequestImpl.getSession(HttpServletRequestImpl.java:367)
[JBossINF] 	at org.jboss.weld.servlet.SessionHolder.requestInitialized(SessionHolder.java:47)
[JBossINF] 	at org.jboss.weld.servlet.HttpContextLifecycle.requestInitialized(HttpContextLifecycle.java:231)
[JBossINF] 	at org.jboss.weld.servlet.WeldInitialListener.requestInitialized(WeldInitialListener.java:152)
[JBossINF] 	at io.undertow.servlet.core.ApplicationListeners.requestInitialized(ApplicationListeners.java:216)
[JBossINF] 	at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:281)
[JBossINF] 	at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:261)
[JBossINF] 	at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:80)
[JBossINF] 	at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:172)
[JBossINF] 	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
[JBossINF] 	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:778)
[JBossINF] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[JBossINF] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JBossINF] 	at java.lang.Thread.run(Thread.java:745)
{code}

Server log:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-ejbservlet-undeploy-dist-sync/5/console-perf20/



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)