Bug 1013169

Summary: org.jboss.logmanager module needs dependency on javax.api for the SocketFactory
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Perkins <jperkins>
Component: LoggingAssignee: James Perkins <jperkins>
Status: CLOSED CURRENTRELEASE QA Contact: Nikoleta Hlavickova <nziakova>
Severity: urgent Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: dosoudil, myarboro, olukas, pkremens
Target Milestone: ER4   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:55:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1010473    

Description James Perkins 2013-09-27 23:46:00 UTC
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.

Comment 2 James Perkins 2013-09-27 23:50:25 UTC
I should add this is only an issue if using the syslog handler with TCP for the protocol on a custom-handler.

Comment 3 Ondrej Lukas 2013-09-30 11:46:48 UTC
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.

Comment 4 JBoss JIRA Server 2013-09-30 17:19:55 UTC
James Perkins <jperkins> made a comment on jira WFLY-2177

Pull request merged

Comment 6 Petr Kremensky 2013-10-04 12:30:36 UTC
Verified on EAP 6.2.0.ER4