Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-15484

Upgrade to Narayana 5.11.3.Final-redhat-00001 - Fuse Spring Boot narayana-jta does not treat null value in com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass()

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • fuse-7.9-GA
    • fuse-7.8-GA
    • Narayana
    • None

    Description

      As commented on TEIID-6040,

      • Fuse Spring Boot using xa datasource shows NullPointerException on jta periodic recovery every 2 mins.
      • This NullPointerException disappear after executing any xa transaction on Fuse spring boot.

      This is because jta-5.9.8.Final-redhat-00002.jar com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass() method does not handle a null value:

      	private final void xaRecoveryFirstPass(XAResource xares)
	{
		if (jtaLogger.logger.isDebugEnabled()) {
            jtaLogger.logger.debug("xarecovery of " + xares);
        }

		
			Xid[] trans = null;

			try
			{
				trans = xares.recover(XAResource.TMSTARTRSCAN);

				if (jtaLogger.logger.isDebugEnabled()) {
                    jtaLogger.logger.debug("Found "
                            + ((trans != null) ? trans.length : 0)
                            + " xids in doubt");
                }
				if (jtaLogger.logger.isTraceEnabled()) {
					for (Xid xid : trans) {         // no null check for "trans"

      Please do the null check like the one for debug level log in the same method:

                          jtaLogger.logger.debug("Found "
                            + ((trans != null) ? trans.length : 0)
                            + " xids in doubt");

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3414 narayana-jta throws NPE during recovering when TRACE logger level is setting

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is duplicated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. ENTESB-17322 Upgrade to Narayana 5.11.3.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done

          Activity

            People

              ggrzybek Grzegorz Grzybek
              rhn-support-hfuruich Hisao Furuichi
              Federico Mariani Federico Mariani
              Stefan Veres
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: