I believe the following type of configuration should work with the current log4j version as it now supports trace natively:

<category name="org.jboss.profileservice">
<priority value="TRACE"/>
<appender-ref ref="PROFILESERVICE"/>
</category>

While messages do appear in the PROFILESERVICE appender, no trace level messages are there. Most likely the jboss Logger is getting in the way of mapping this priority and an update to the common logging spi is needed.