Configuration Guide: About XA recovery: Vendor-Specific XA Recovery changes

Configuration Guide: 6.7. About XA Recovery: 6.7.2. Configuring Vendor-Specific XA Recovery

I would like ask for several changes in this seciton

• this section is part chapter about datasource and contain information about JMS as well. The structure should be probably changed somehow.
• title of the chapter Configuring Vendor-Specific XA Recovery should be changed as there is not only information about configuration but about issues too in this section
• part Vendor-Specific Configuration
  • add information about MariaDB as it's newly supported db from eap 7. There should be the same thing as for mysql No special configuration is required. For more information, see the MySQL documentation.
• part Known Issues
  • add information that issues followed here are based on versions of products supported with particular version of EAP
  • MySQL: add information that the bug of XA handling was fixed in MySQL 5.7.7 (but we support mysql in 5.5 as well where this bug is still valid)
  • add section about MariaDB and add the same text as for Mysql is now like MariaDB is not capable of fully handling XA transactions. If a client is disconnected from MariaDB, then all the information about such transactions is lost. See the MySQL bug http://bugs.mysql.com/bug.php?id=12161 for more information.
  • rephrase the following paragraph which is used in more places in this section from

    The JDBC driver returns XAER_RMERR when an error occurs during the call of commit method protocol. The database returns this error code and leaves the transaction in the in-doubt state on the database side. The correct return code should be XAER_RMFAIL or XAER_RETRY. This causes the transaction to be left in the Heuristic state on the JBoss EAP side and holding locks in the database which requires manual intervention. See this bug for more information. 
      

    to something like this

    The JDBC driver returns XAER_RMERR when an network failure occurs during the commit phase. This error signifies catastrophic event which is unrecoverable and transaction manager behaves based on it. But the transaction in left in-doubt state on the database side and could be easily corrected after network connection is established again. The correct return code should be XAER_RMFAIL or XAER_RETRY. Wrong error code causes the transaction to be left in the Heuristic state on the JBoss EAP side and holding locks in the database which requires manual intervention.
      

  • remove issue of ActiveMQ. This issue should be already fixed in currently supported version of ActiveMQ. There should be left a sentence that there is no known issues.