Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via fixunix.com by Unknown author, 1 year ago
Attempt to resume an inactive transaction: 3:80dca889de2214da at weblogic.transaction.internal.TransactionManagerImpl.resume(TransactionManagerImpl.java:357) at weblogic.transaction.internal.ServerTransactionManagerImpl.resume(ServerTransactionManagerImpl.java:304) at weblogic.jms.frontend.FESession.transactedInfect(FESession.java:1684)
via objectmix.com by Unknown author, 1 year ago
Attempt to resume an inactiv= e transaction: 3:80dca889de2214da at weblogic.transaction.internal.TransactionManagerImpl.resume(TransactionMana= gerImpl.java:357) at weblogic.transaction.internal.ServerTransactionManagerImpl.resume(ServerTra= nsactionManagerImpl.java:304) at weblogic.jms.frontend.FESession.transactedInfect(FESession.java:1684)
javax.transaction.InvalidTransactionException: Attempt to resume an inactive
transaction: 3:80dca889de2214da
at
weblogic.transaction.internal.TransactionManagerImpl.resume(TransactionManagerImpl.java:357)
 
at
weblogic.transaction.internal.ServerTransactionManagerImpl.resume(ServerTransactionManagerImpl.java:304)
 
at
weblogic.jms.frontend.FESession.transactedInfect(FESession.java:1684)	at weblogic.jms.frontend.FEProducer.send(FEProducer.java:429)	at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:534)