[jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-1315) CMS content rendered with wrong tx on thread

CMS content rendered with wrong tx on thread -------------------------------------------- Key: JBPORTAL-1315 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1315 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha2 Reporter: David Allen This might be a problem in "core" or somewhere else, but this only occurs with windows containing CMS content. The exact steps which cause it are: 1. Display a page with a CMS content window in a new browser window. 2. Click on the login link on the dashboard. 3. When the same page is rendered after successful login (now under authsec), the following exception occurs and the CMS content is not displayed (replaced with exception): 2007-03-09 16:02:06,874 ERROR [org.jboss.portal.server.servlet.PortalServlet] Unexpected exception java.lang.IllegalStateException: Wrong tx on thread: expected TransactionImpl:XidImpl[FormatId=257, GlobalId=tines/83, BranchQual=, localId=83], actual TransactionImpl:XidImpl[FormatId=257, GlobalId=tines/84, BranchQual=, localId=84] at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:162) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87) at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262) at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) at org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:381) If more of the stack trace is needed, let me know. The rest doesn't look that useful -- just the usual processing. The same exception causes many different classes to log the error along the way, so I hope I picked up the right log message here.