Opened 6 years ago

Closed 6 years ago

#1077 closed defect (fixed)

NPE in thread run

Reported by: Eche|on Owned by: zzz
Priority: minor Milestone: 0.9.9
Component: apps/i2ptunnel Version: 0.9.8.1
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

Thread terminated unexpectedly: ServerHandler? pool /127.0.0.1:3333.hc
2013/10/16 10:12:27 | java.lang.NullPointerException?
2013/10/16 10:12:27 | at net.i2p.i2ptunnel.I2PTunnelHTTPServer$CompressedRequestor?.run(I2PTunnelHTTPServer.java:256)
2013/10/16 10:12:27 | at java.lang.Thread.run(Thread.java:724)
2013/10/16 10:12:27 | at net.i2p.util.I2PThread.run(I2PThread.java:85)

I am on 0.9.8.1-3.

thats false.i2p

Subtickets

Change History (2)

comment:1 Changed 6 years ago by zzz

Owner: set to zzz
Status: newaccepted

Hmm. I did it I think. _headers can't be null so it must be _browserin.

I2PSocketFull.getInputStream() may return null, we should be throwing an IOE. Thankfully the interface declares IOE.

Not clear if recent streaming changes triggered this but no matter.

The new logging of thread death in I2PThread is proving quite helpful.

comment:2 Changed 6 years ago by zzz

Resolution: fixed
Status: acceptedclosed

Fixed in 0.9.8.1-5. getInputStream() and getOutputStream() will no longer return null.

Note: See TracTickets for help on using tickets.