opname: shouldMerge cannot process request, because object doesn't exist ------------------------------------------------------------------------ Key: JBTM-1880 URL: https://issues.jboss.org/browse/JBTM-1880 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public(Everyone can see) Components: JTA Reporter: Tom Ross Assignee: Tom Jenkinson When dealing with some situations we choose to ignore certain exceptions [1] {noformat} 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; } {noformat} Unfortunately jacorb does log it and the result is a log file full warnings: {noformat} [jacorb.poa.controller] (RequestController-1) rid: 42 opname: shouldMerge cannot process request, because object doesn't exist {noformat} 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/...