The javax.net.SocketFactory is part of the javax.api module. Since the org.jboss.logmanager uses this for the syslog handler on TCP and SSL connections, a dependency on the module is needed.
I should add this is only an issue if using the syslog handler with TCP for the protocol on a custom-handler.
Same issue is in audit-log in syslog-handler. Audit log has P0 and it could be customer problem in Beta, because it couldn't be set and used by customer. For that reason it is candidate on Beta blocker. PR sent by James solves this issue.
James Perkins <jperkins> made a comment on jira WFLY-2177 Pull request merged
Verified on EAP 6.2.0.ER4