NIFI Warnings and Errors

[#1]

Weird NIFI 1.1 warnings

2017-01-04 19:40:34,445 WARN [NiFi Web Server-1012] org.eclipse.jetty.http.HttpParser Illegal character 0x16 in state=START for buffer HeapByteBuffer@1dd9f5b4[p=1,l=227,c=8192,r=226]={\x16<<<\x03\x01\x00\xDe\x01\x00\x00\xDa\x03\x03\x16\xF8\xBd[\x9eC\xE3...\x00\x08\xFa\xFa\x00\x1d\x00\x17\x00\x18ZZ\x00\x01\x00>>> Chrome/55.0.2883...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
2017-01-04 19:40:34,445 WARN [NiFi Web Server-1054] org.eclipse.jetty.http.HttpParser Illegal character 0x16 in state=START for buffer HeapByteBuffer@1a1c27d[p=1,l=227,c=8192,r=226]={\x16<<<\x03\x01\x00\xDe\x01\x00\x00\xDa\x03\x03\xA29\xC3\xD6\xA7{\xD8...\x00\x08::\x00\x1d\x00\x17\x00\x18\xDa\xDa\x00\x01\x00>>>5 Safari/537.36\r\n...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
2017-01-04 19:40:34,453 WARN [NiFi Web Server-1054] org.eclipse.jetty.http.HttpParser bad HTTP parsed: 400 Illegal character 0x16 for HttpChannelOverHttp@29677b4c{r=0,c=false,a=IDLE,uri=null}
2017-01-04 19:40:34,453 WARN [NiFi Web Server-1012] org.eclipse.jetty.http.HttpParser bad HTTP parsed: 400 Illegal character 0x16 for HttpChannelOverHttp@2b00525e{r=0,c=false,a=IDLE,uri=null}

2017-01-04 19:42:51,278 ERROR [Provenance Maintenance Thread-6] org.apache.nifi.NiFi An Unknown Error Occurred in Thread Thread[Provenance Maintenance Thread-6,5,main]: java.lang.OutOfMemoryError: Java heap space
2017-01-04 19:42:51,278 ERROR [Flow Service Tasks Thread-1] org.apache.nifi.NiFi An Unknown Error Occurred in Thread Thread[Flow Service Tasks Thread-1,5,main]: java.lang.OutOfMemoryError: Java heap space
2017-01-04 19:42:51,278 ERROR [FileSystemRepository Workers Thread-1] o.a.n.c.repository.FileSystemRepository Failed to handle destructable claims due to java.lang.OutOfMemoryError: Java heap space
2017-01-04 19:42:51,279 ERROR [Provenance Maintenance Thread-6] org.apache.nifi.NiFi
java.lang.OutOfMemoryError: Java heap space
2017-01-04 19:42:51,279 ERROR [Flow Service Tasks Thread-1] org.apache.nifi.NiFi
java.lang.OutOfMemoryError: Java heap space
2017-01-04 19:42:51,279 WARN [NiFi Web Server-1548] o.e.jetty.util.thread.QueuedThreadPool
java.lang.OutOfMemoryError: Java heap space
2017-01-04 19:42:51,280 WARN [NiFi Web Server-1548] o.e.jetty.util.thread.QueuedThreadPool Unexpected thread death: org.eclipse.jetty.util.thread.QueuedThreadPool$2@4c5a6f9f in NiFi Web Server{STARTED,8<=10<=200,i=1,q=0}
2017-01-04 19:42:51,283 WARN [NiFi Web Server-1550] org.eclipse.jetty.servlet.ServletHandler Error for /
java.lang.OutOfMemoryError: Java heap space

[#2 · Accepted solution]

@Timothy Spann

Once you run out of heap space, NiFi is going to start throwing all kinds of WARN and ERROR log entries. Looks like you need to increase your configured heap memory settings in the bootstrap.conf file.

[#3]

I increased it in nifi-ambari-config

Max memory allocation

[#4]

Is that NiFi secured? If so, did you attempt to access it via HTTP (vs HTTPS), or vice versa (HTTPS to an unsecured NiFi)?

Alternatively, were you running a flow at the time? If so, what were the processors involved? The version of Jetty was upgraded in NiFi 1.0.0, but I'm not sure what (if anything) is different between 1.0.0 and 1.1.0 with respect to Jetty.