These are chat archives for spring-cloud/spring-cloud

6th
Jan 2017
bitsofinfo
@bitsofinfo
Jan 06 2017 03:06
Any ideas why all my spring cloud containers constantly spew this message, despite everything appearing to otherwise be operating normally? 2017-01-06T03:02:57.926556955Z 2017-01-06 03:02:57,926 25da18881ecd 1 my-app [t=,s=,se=] DEBUG [io] UT005013: An IOException occurred 2017-01-06T03:02:57.926569555Z java.io.IOException: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? 2017-01-06T03:02:57.926574055Z at io.undertow.protocols.ssl.SslConduit.notifyReadClosed(SslConduit.java:612) 2017-01-06T03:02:57.926577955Z at io.undertow.protocols.ssl.SslConduit.doUnwrap(SslConduit.java:708) 2017-01-06T03:02:57.926583655Z at io.undertow.protocols.ssl.SslConduit.read(SslConduit.java:565) 2017-01-06T03:02:57.926587555Z at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127) 2017-01-06T03:02:57.926591555Z at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:153) 2017-01-06T03:02:57.926595355Z at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:131) 2017-01-06T03:02:57.926598955Z at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:57) 2017-01-06T03:02:57.926602555Z at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) 2017-01-06T03:02:57.926606555Z at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) 2017-01-06T03:02:57.926610255Z at io.undertow.protocols.ssl.SslConduit$SslReadReadyHandler.readReady(SslConduit.java:1122) 2017-01-06T03:02:57.926614055Z at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) 2017-01-06T03:02:57.926618155Z at org.xnio.nio.WorkerThread.run(WorkerThread.java:559)
Dave Syer
@dsyer
Jan 06 2017 04:53
No idea. It's the container by the looks of it (undertow).
Maybe you have a health check pinger that isn't behaving well?
bitsofinfo
@bitsofinfo
Jan 06 2017 15:23
Yeah, it outputs on every HTTPS request by anything.
The requests work, but this dumps, annoying
Dave Syer
@dsyer
Jan 06 2017 15:24
It's a DEBUG log
I'd ignore it
bitsofinfo
@bitsofinfo
Jan 06 2017 15:25
yes, just going to filter it out
Ryan Baxter
@ryanjbaxter
Jan 06 2017 17:20
are you expecting the IP address to be changed to localhost?
Ali Akbar Azizkhani
@removed~azizkhani
Jan 06 2017 18:42
@ryanjbaxter yes this will change like zuul routes
@ryanjbaxter why zuul dont do it ? i will write filter ? :worried:
Ryan Baxter
@ryanjbaxter
Jan 06 2017 19:32
because it may not be the case that you want it to go back through the proxy