Funnily we see every minute this trace in the logs, after a restart:
<BEA-110486><Transaction BEA1-0707A967026BC04A2B95 cannot complete commit processing because resource [weblogic.jdbc.jta.DataSource] is unavailable. The transaction will be abandoned after 76,586 seconds unless all resources acknowledge the commit decision.>
in server/monitoring/Recovery Services I see that we have a "Initial Recovered Transaction Total Count" = 1
and in the Monitoring/JTA/Transactions tab I see
So my guess is that it's trying to recover a 2 phase transaction stored into a TLOG when we did an emergency shutdown. Probbaly this TX will timeout after 86400 seconds (this is the "Abandon Timeout Seconds" (see domain/JTA configuration)
<BEA-110486><Transaction BEA1-0707A967026BC04A2B95 cannot complete commit processing because resource [weblogic.jdbc.jta.DataSource] is unavailable. The transaction will be abandoned after 76,586 seconds unless all resources acknowledge the commit decision.>
in server/monitoring/Recovery Services I see that we have a "Initial Recovered Transaction Total Count" = 1
and in the Monitoring/JTA/Transactions tab I see
Transaction ID Status Seconds Active XA Resources Servers
BEA1-0707A967026BC04A2B95 Committing 15966 {weblogic.jdbc.jta.DataSource=new, WLStore_osbpr2do_AcmeCommonFileStore4=committed} {osbpr2do+osbpr2ms4=committed}
So my guess is that it's trying to recover a 2 phase transaction stored into a TLOG when we did an emergency shutdown. Probbaly this TX will timeout after 86400 seconds (this is the "Abandon Timeout Seconds" (see domain/JTA configuration)