• State Not Answered
  • Replies 11 replies
  • Subscribers 7 subscribers
  • Views 7377 views
  • Users 0 members are here
Related Discussions
Home » Discussions » AI and Rules

Reoccurring error message in logs, anyone seen this?

ChristineH
Certified Lead Developer

We are sporadically seeing this issue in the logs when rules (queries to the DB) are throwing alerts. However, we can restart the nodes successfully. Has anyone seen this? Is this an Oracle issue (number of connections, concurrent connections, etc.)? or an indication of an install issue with Appian? We are on Appian 16.1. Any help appreciated!

2016-07-06 14:32:16,160 [http-/0.0.0.0:8080-15] ERROR org.hibernate.transaction.JTATransaction - JTA commit failed
javax.transaction.RollbackException: ARJUNA016102: The transaction is not active! Uid is 0:ffff0a762419:-11302709:576a9d41:1001a6
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1179)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransac...

OriginalPostID-222121

OriginalPostID-222121

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    If this is occurring frequently, try setting the following logger to get some more information:

    log4j.logger.org.hibernate.util.JDBCExceptionReporter=DEBUG

    You should then see some more information about what is causing the transaction to be aborted. If that doesn;t give enough detail, you can update

    <logger category="com.arjuna">
    <level name="ERROR"/>
    </logger>

    to

    <logger category="com.arjuna">
    <level name="DEBUG"/>
    </logger>

    in your standalone.xml
Reply
  • 0
    Appian Employee
    If this is occurring frequently, try setting the following logger to get some more information:

    log4j.logger.org.hibernate.util.JDBCExceptionReporter=DEBUG

    You should then see some more information about what is causing the transaction to be aborted. If that doesn;t give enough detail, you can update

    <logger category="com.arjuna">
    <level name="ERROR"/>
    </logger>

    to

    <logger category="com.arjuna">
    <level name="DEBUG"/>
    </logger>

    in your standalone.xml
Children
No Data

© 2024 Appian. All rights reserved.