[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1580) Transaction won't commit from MDB Seam2 component

Gavin King (JIRA) jira-events at lists.jboss.org
Thu Jun 28 20:53:57 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBSEAM-1580?page=all ]

Gavin King closed JBSEAM-1580.
------------------------------

    Resolution: Done
      Assignee: Gavin King

> Transaction won't commit from MDB Seam2 component
> -------------------------------------------------
>
>                 Key: JBSEAM-1580
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1580
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.BETA1
>            Reporter: Daniel Young
>         Assigned To: Gavin King
>             Fix For: 2.0.0.CR1
>
>
> I have an MDB annotated with @Name, which worked fine in 1.2.1.GA.
> But now, when the app server attemps to commit following a successful message, I get this...
> Code:
> 10:12:29,703 INFO  [DownloadManager] Finished processing file: c:\download\received\2AZ3MQ_200606271
> 34443
> 10:12:29,703 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_2] TwoPhas
> eCoordinator.beforeCompletion - failed for com.arjuna.ats.internal.jta.resources.arjunacore.Synchron
> izationImple at f66eac
> java.lang.IllegalStateException: No application context active
> 	at org.jboss.seam.Component.forName(Component.java:1690)
> 	at org.jboss.seam.Component.getInstance(Component.java:1740)
> 	at org.jboss.seam.Component.getInstance(Component.java:1735)
> 	at org.jboss.seam.Component.getInstance(Component.java:1712)
> 	at org.jboss.seam.Component.getInstance(Component.java:1707)
> 	at org.jboss.seam.core.Events.instance(Events.java:154)
> 	at org.jboss.seam.transaction.SynchronizationRegistry.beforeTransactionCompletion(SynchronizationRe
> gistry.java:51)
> 	at org.jboss.seam.transaction.EjbTransaction.beforeCompletion(EjbTransaction.java:43)
> 	at org.jboss.ejb3.stateful.SessionSynchronizationInterceptor$SFSBSessionSynchronization.beforeCompl
> etion(SessionSynchronizationInterceptor.java:71)
> 	at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(Synchroni
> zationImple.java:114)
> 	at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:
> 249)
> 	at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88)
> 	at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
> 	at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(Transa
> ctionImple.java:1256)
> 	at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:1
> 35)
> 	at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.jav
> a:87)
> 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession$XATransactionDemarcationStrategy.end(JmsS
> erverSession.java:494)
> 	at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:248)
> 	at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
> 	at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
> 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
> 	at java.lang.Thread.run(Thread.java:595)
> 	
> The MDB is using CMT (obviously), and was using a standard @PersistenceContext. I tried changing it to inject my seam-managed PC, but the error was still the same. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list