Hello.


I encounter performance issue with ListenHTTP and StandardSSLContextService on 
Nifi 0.6.1.



My workflow is quite simple : ListenHTTP => Merge => PutFile.



I can top 3000 req/s with http, only few hundreds (about 200 without error) 
with https.



The thread dump shows a lock at getDefaultCipherSuiteList:

ListenHTTP (57965e61-52c0-4ed2-a8d8-ed9bcf1500c4) Web 
Server-1050-selector-ServerConnectorManager@e624229/3 - priority:5 - 
threadId:0x00007f12c0001000 - nativeId:0x3e47 - state:BLOCKED
stackTrace:
java.lang.Thread.State: BLOCKED (on object monitor)
at 
sun.security.ssl.SSLContextImpl.getDefaultCipherSuiteList(SSLContextImpl.java:291)
- waiting to lock <0x0000000631ce2450> (a 
sun.security.ssl.SSLContextImpl$TLSContext)
at sun.security.ssl.SSLEngineImpl.init(SSLEngineImpl.java:402)
at sun.security.ssl.SSLEngineImpl.<init>(SSLEngineImpl.java:357)
at 
sun.security.ssl.SSLContextImpl.engineCreateSSLEngine(SSLContextImpl.java:210)
at javax.net.ssl.SSLContext.createSSLEngine(SSLContext.java:361)
at 
org.eclipse.jetty.util.ssl.SslContextFactory.newSSLEngine(SslContextFactory.java:1344)





. I'm using java 1.8.0_101-b13, I found some issues with a synchronized() on 
cipher cache.



I wonder if I can do anything in Nifi configuration, if ever someone else have 
this issue.



Thanks.

Reply via email to