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)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web25

  • via fixunix.com by Unknown author, 10 months 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, 10 months 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)
  • via Oracle Community by 3004, 2 weeks ago
    Attempt to resume an inactive transaction: 3:80dca889de2214da
  • Stack trace

    • 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)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.