Juergen Zimmermann WRT "location info", I forgot that log4j does not really provide what I mean OOTB. It has all the pieces but you'd have to write a custom Layout (extending PatternLayout) to get the right info. The idea is to log the full call stack when this log message happens. Log4j already has the ability to collect the stack info via its LocationInfo class. In fact that is how PatternLayout ultimately gives you access to the limited location info it provides (C,F,L,L,M conversion chars). The idea was to dump out the whole call stack so you could see who is calling this.

From your logs it certainly seems like something is using "JPA SE bootstrapping", rather than relying on the container (WildFly) to do EE bootstrapping for you. Given that, I can see how this deprecation logging could come up. SE boostrapping loops over all JPA providers discovered on the classpath and ask them each to build the EMF. The provider is supposed to check whether they are the indicated provider and if so build the EMF. The deprecated provider is logging this warning even before checking. HHH-8735 will address that