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

24th
Feb 2019
Muhmud Ahmad
@muhmud
Feb 24 11:03
Hi guys, I'm having a weird issue with Spring Cloud Gateway in AWS. I have an AWS ELB pointing to my gateway, which then routes traffic to another service. Everything works, but I randomly get a 504 Gateway Time-out. So, I run a curl request successfully once, then immediately run the same thing again and it times out. Then I try again and it works. It maybe work successfully a few times before the timeout. I've tried running it directly on my EC2 host, and if I hit the destination service directly, it works everytime, however, going through the gateway on the host, gives me the same timeout behaviour, so I don't think it's the load balancer and so must be the gateway. I am using docker containers to run the services and free memory on the EC2 host is about 1 GB. I can't find any similar issues online; anyone have any ideas?
Muhmud Ahmad
@muhmud
Feb 24 11:08
The only exception I can see from the logs is: javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify
Muhmud Ahmad
@muhmud
Feb 24 11:37
Though, I'm not sure this is the problem. When it times out, it gets stuck on: 11:36:21.850 [reactor-http-epoll-1] DEBUG r.n.channel.ChannelOperationsHandler - [id: 0xdd643584, L:/127.0.0.1:34576 - R:localhost/127.0.0.1:8080] Writing object MonoJust
But when it works, it goes right past this
Muhmud Ahmad
@muhmud
Feb 24 19:54
Found a solution: using reactor-netty 0.8.5 fixed it