[cfang]

it's probably a log4j2 configuration issue, and it looks harmless, at least on the surface.  I'm not using log4j2 in my tests, so I'm not seeing this.  One of the changes from JBeret 1.3.0.Beta2 to Beta3 is Weld and Weld-se version is upgraded from 2.3.0.Beta3 to 2.3.4.Final, which may be cause.

[richardmoore]

I was able to get rid of this message by doing the following -

1. Add system property of -Dorg.jboss.weld.se.shutdownHook=false
2. On the log4j2 xml configuration root tag, Configuration add the attribute:  shutdownHook="disable"

[cfang]

Thanks for the solution. It will help others facing the same problem.