Bug 1073430

Summary: Http11Nio loaded, JBWEB002081: No cipher match
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Michal Karm Babacek <mbabacek>
Component: WebAssignee: Rémy Maucherat <rmaucher>
Status: CLOSED NOTABUG QA Contact: Michal Karm Babacek <mbabacek>
Severity: urgent Docs Contact: Russell Dickenson <rdickens>
Priority: urgent    
Version: 6.3.0CC: jdoyle, mbabacek, rmaucher, rsvoboda, smumford
Target Milestone: DR3   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-10 08:46:17 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:

Description Michal Karm Babacek 2014-03-06 12:41:50 UTC
Hi guys, please, follow:

https://issues.jboss.org/browse/JBWEB-292

TL;DR: It seems that web subsystem ignores native="false" and loads natives if they are present in the modules/yada.. /lib.

Comment 1 Michal Karm Babacek 2014-03-06 13:12:37 UTC
(In reply to Michal Babacek from comment #0)
> Hi guys, please, follow:
> 
> https://issues.jboss.org/browse/JBWEB-292
> 
> TL;DR: It seems that web subsystem ignores native="false" and loads natives
> if they are present in the modules/yada.. /lib.

I amended the description, the issue has nothing to do with native libraries. It's present even if I deleted them all. Perhaps, Http11Nio does not support all these aforementioned cipher suites?

Comment 2 John Doyle 2014-03-06 21:34:19 UTC
This needs more discussion before I agree to blocker status.

Comment 3 JBoss JIRA Server 2014-03-08 10:45:09 UTC
Jean-Frederic Clere <jfclere> updated the status of jira JBWEB-292 to Closed

Comment 4 Michal Karm Babacek 2014-03-10 08:46:17 UTC
Closing, this is not a bug.
The upgrade of JBossWeb brought about new configuration requirements for the SSL part and I erroneously mistook this feature for a bug.