[jboss-jira] [JBoss JIRA] (WFLY-5536) Recovery manager is not able to recover MDB and shows warnings on each run.
    Hayk Hovsepyan (JIRA) 
    issues at jboss.org
       
    Fri Oct 16 03:38:00 EDT 2015
    
    
  
     [ https://issues.jboss.org/browse/WFLY-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hayk Hovsepyan updated WFLY-5536:
---------------------------------
    Steps to Reproduce: 
When MDB Inbound connection  enlisted on 2PC, and server crashes before TX save state is called,  Recovery manager is not able to proceed the log about JMS MDB XA  resource and shows warning messages on each time it runs.
1. Enlist MDB JMS XA resource for Inbound connection.
2. Enlist TestXA resource.
3. 2PC starts prepare phase
4. Prepare MDB JMS XA resource.(txn log created on broker side)
5. Prepare TestXA resource.
6. 2PC starts commit phase
7. MDB JMS XA resource is committed.(txn log erased on broker side)
8. Crash JVM and undeploy MDB.
9. Restart the server and start recovery.
10. TestXA resource is committed
11. Recovery manager logs warning messages for MDB JMS XA resource each time it is started (txn log record about MDB JMS XA still exist in transaction log store on EAP side)
{code}
14:50:04,897 WARN  [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:718d19b:561fa0a5:25, node_name=1, branch_uid=0:ffff7f000001:718d19b:561fa0a5:26, subordinatenodename=null, eis_name=unknown eis name >, heuristic: TwoPhaseOutcome.FINISH_OK com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord at 2a6e6c5 >
14:50:04,897 WARN  [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:718d19b:561fa0a5:25, node_name=1, branch_uid=0:ffff7f000001:718d19b:561fa0a5:26, subordinatenodename=null, eis_name=unknown eis name >
{code}
Possible cause of issue is because eis_name is unknown, as shown in logs.
Full log of server is attached.
The issue can be reproduced via automated test case.
1. Clone the repo: "git clone -b JMS-MDB-LOG --single-branch git at gitlab.mw.lab.eng.bos.redhat.com:hhovsepy/tests-transactions.git"
2. Change directory: "cd tests-transactions/jbossts/"
3. Run test: "mvn clean verify -Djboss.dist=$JBOSS_HOME -Dtest=JMSMdbCrashRecoveryTestCase#commitHaltFirst"
> Recovery manager is not able to recover MDB and shows warnings on each run.
> ---------------------------------------------------------------------------
>
>                 Key: WFLY-5536
>                 URL: https://issues.jboss.org/browse/WFLY-5536
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Hayk Hovsepyan
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>         Attachments: MDB_JMS_XA.log
>
>
> Recovery manager is not able to recover MDB and shows warnings.
> This causes to see the same warning log in server each time recovery is run.
> This happens when server is crashed before transaction state is saved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
    
    
More information about the jboss-jira
mailing list