Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-1880

opname: shouldMerge cannot process request, because object doesn't exist

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • None
    • JTA
    • None

    Description

      When dealing with some situations we choose to ignore certain exceptions [1]

      if (rec != null)
      			{
      				try
      				{
      					result = resHandle.shouldMerge(rec);
      				}
      				catch (OBJECT_NOT_EXIST ex)
      				{
      					// This is expected to happen whenever a resource has gone away, for example during a crash or if it has exited the 2PC process early by returning XA_RDONLY out of prepare
      				}
      				catch (Exception e) {
                          _endpointFailed = true;
      
                          jtsLogger.i18NLogger.warn_resources_errgenerr("ExtendedResourceRecord.shouldMerge", e);
                      }
      
      				rec = null;
      			}
      
      

      Unfortunately jacorb does log it and the result is a log file full warnings:

       [jacorb.poa.controller] (RequestController-1) rid: 42 opname: shouldMerge cannot process request, because object doesn't exist
      
      

      If we have decided to ignore this warning then JACORB should the same and not log it at WARN level.

      [1] https://github.com/tomjenkinson/narayana/blob/4.17/ArjunaJTS/jts/classes/com/arjuna/ats/internal/jts/resources/ExtendedResourceRecord.java#L1042

      Attachments

        Activity

          People

            thjenkin@redhat.com Tom Jenkinson
            rhn-support-toross Tom Ross
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: