Opened 10 years ago

Closed 9 years ago

#460 closed defect (fixed)

wrong log level for eep proxy connections

Reported by: sponge Owned by: sponge
Priority: minor Milestone: 0.8.12
Component: apps/i2ptunnel Version: 0.6.31
Keywords: Cc:
Parent Tickets: Sensitive: no


Error level is too high for connections that don't work on the eep proxy. Here is an example, from bidir's proxy. Not sure if the same level is in the eep-proxy as well.

ERROR [] unnel.I2PTunnelHTTPBidirServer: Error connecting to HTTP server / Connection refused
     at Method)
     at net.i2p.i2ptunnel.I2PTunnelHTTPServer.blockingHandle(
     at net.i2p.i2ptunnel.I2PTunnelServer$
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
     at java.util.concurrent.ThreadPoolExecutor$

Perhaps the log level should be INFO, not ERROR, as it's not a major issue, and a transient error

This has been an issue since for as long as I can remember.


Change History (3)

comment:1 Changed 10 years ago by zzz

Owner: set to sponge
Status: newassigned

This is not an outgoing client eep proxy error, it's an incoming server error. I2PTunnel can't connect the HTTP server at port 7658. Why is it transient? The local web server isn't responding.

So I don't see why it should be less than ERROR.

Assigning to you for further explanation or to close it.

comment:2 Changed 9 years ago by sponge

Status: assignedaccepted

Tunnel is open before jetty got the chance to start, that's why it happens…
And you are correct, that is on the inbound, I'll still fix this on the bidir tunnel.

comment:3 Changed 9 years ago by sponge

Resolution: fixed
Status: acceptedclosed

Changed warning level for the first 3 minutes to WARN.

Note: See TracTickets for help on using tickets.