MessageService.getLocalizedMessage(...) assumes that its third argument, String sqlerrmc, is tokenized.
DERBY-1178 showed that it is easy to make a change that violates this assumption. Currently this is not detected because the resulting failures are masked and handled by falling back to (incorrect) defaults.
It would be preferable if MessageService.getLocalizedMessage(...) could verify that the input is, in fact, a tokenized message, and provide an appropriate error message if isn't. Ideally it should also be more verbose, at least in debug builds, about failing to find the specified locale resources.