Skip to main content

Did someone see those 504 errors before? We get time outs when trying to reach 2 endpoints and would like to know how to fix this. 

 

We have 2 endpoints are unreachable (the other endpoints are working well). Those are the sales order lines and stock mutation. Those endpoints are standard Thinkwise. 


We do not see any strange errors on the application side also the infrastructure developer says everything is working correctly: 

‘I have verified that the load balancer associated with the application is operational, and the target group receiving the domain traffic is in a healthy state. I also logged into instance and i can see that ec2 instance is running and healthy.
I also  reviewed the associated security groups and firewall configurations. I can confirm that everything appears to be correctly configured and functioning as expected on the AWS side.’

 

 

Maybe a silly question from my side, and you already may have tried this, but can you run a query on stock_mutation with another tool like pgAdmin or so, one that is closer to the DB and does not care about how long things take? This might give you an indication on how heavy the query or the query result is. I remember that I could make indicium cry when I did a select from a gigantic table without any where clause, but I could also blow up a SQL Server query when making things too complex, both ended up with similar results as yours: A timeout...

Thanks for the help: The issue was that this call was fetching too many records. We’ll be making a call to fetch with less records now (added a filter). 

Reply


Terms & ConditionsCookie settings