responseReason is null [SPR-15400]

[spring-projects-issues]

Lena Lindstrot opened SPR-15400 and commented

I have a Spring- Boot-Project (1.5.2.RELEASE) with spring-web-mvc 4.3.7-RELEASE.
When I do a REST request, I get only "HTTP/1.1 200", so it missing " OK". In the calling microservie (older version) I get a nullpointer exception because responseReason is null:

java.lang.RuntimeException: com.netflix.client.ClientException
at feign.ribbon.RibbonClient.execute(RibbonClient.java:75)
at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:92)
at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:71)
at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:94)
...
Caused by: com.netflix.client.ClientException: null
at com.netflix.client.AbstractLoadBalancerAwareClient.executeWithLoadBalancer(AbstractLoadBalancerAwareClient.java:123)
at feign.ribbon.RibbonClient.execute(RibbonClient.java:69)
... 106 common frames omitted

---

Affects: 4.3.7

[spring-projects-issues]

Andrei Ivanov commented

Probably related: https://bz.apache.org/bugzilla/show_bug.cgi?id=60362

[spring-projects-issues]

Lena Lindstrot commented

A, ok, I understand now. User calling component is too old (not older as a year). So the feignclient 8.1.1 is not compatible with Spring framework 4.3.7.
The feignclient makes a not null- check and the newer one not.
You can close the issue, we update user calling component

[spring-projects-issues]

Brian Clozel commented

This has nothing to do with Spring Framework indeed; this is standard Tomcat 8.5 behavior.

You can get more background information on this in this Spring Boot issue. You should either upgrade your client or downgrade your Tomcat version.

Thanks,