These are chat archives for spring-cloud/spring-cloud
management.metricsis this a change that I should also PR?
@spencergibb this doesn’t ring any bells does it?
2018-05-14 14:53:41.597 TRACE 98619 --- [ctor-http-nio-6] o.s.c.g.filter.RouteToRequestUrlFilter : RouteToRequestUrlFilter start 2018-05-14 14:53:42.557 TRACE 98619 --- [ctor-http-nio-7] o.s.c.g.filter.NettyWriteResponseFilter : NettyWriteResponseFilter start 2018-05-14 14:53:42.559 ERROR 98619 --- [ctor-http-nio-6] o.s.w.s.adapter.HttpWebHandlerAdapter : Unhandled failure: Connection has been closed, response already set (status=200) 2018-05-14 14:53:42.561 ERROR 98619 --- [ctor-http-nio-6] o.s.h.s.r.ReactorHttpHandlerAdapter : Handling completed with error
Stack trace apparently never seems to leave reactor/netty land, allegedly on
Works fine via postman, fails from an http call from another jvm application
think we figured it out…kinda
the method we were posting to in the service from the gateway wasn’t returning anything. The error goes away when I return some empty json. Super hacky but it works