Details
-
Bug
-
Resolution: Done
-
Minor
-
5.10.6.Final
-
None
Description
The LRA code uses patter at many places where it prints error message to log and then it returns that error description to client by throwing the WebApplicationException.
The example could be
} catch (URISyntaxException e) { LRALogger.i18NLogger.error_invalidRecoveryUrlToJoinLRAURI(recoveryUrl.toString(), lraId); String errorMsg = lraId + ": Invalid recovery URL " + recoveryUrl.toString(); throw new WebApplicationException(errorMsg, e , Response.status(INTERNAL_SERVER_ERROR).entity(errorMsg).build()); }
There is the inconsistency that the log message is not the same as the message returned in via the exception.
It would be good to make it consistent. The goal is to verify the log messages at `io.narayana.lra.proxy.logging.lraI18NLogger` and `io.narayana.lra.logging.lraI18NLogger`.