The logger where this happens is used only in bootstrap code. So y'all are telling me that its too much ("nagged") to enable DEBUG logging for that class (when you see trouble bootstrapping btw!)?

IMO, when you have JPA bootstrap problems you should really be cranking up DEBUG logging on that entire JPA bootstrap package anyway. DEBUG logging and enabling assertions should always be one of the first steps (IMHO) in troubleshooting.

Sanne's 180 aside, everyone above agreed this is a non-issue which is exactly what I think as well.