A significant increase in 500 error codes.

a year ago

In the backend API I’m using, there’s a significant increase in 500 error codes, and I see that it’s taking 49 seconds to respond with data. 90% of incoming requests are returning a 500 error code. What could be the reason for this? Urgent help needed!

Solved

9 Replies

This is unfortunately an issue with your application. Please add more logging to determine the issue.


Status changed to Awaiting User Response Railway 12 months ago


a year ago

I have shared my Project as an attachment to my question. Could you follow the logs, especially the HTTP logs?


Status changed to Awaiting Railway Response Railway 12 months ago


a year ago

Unfortunately we're unable to offer application level help.


Status changed to Awaiting User Response Railway 12 months ago


a year ago

Unfortunately we're unable to offer application level help.


a year ago

I am not asking for application-level assistance. Previously, a GET request was taking 50ms to respond, but now it takes 23,000ms. I haven't made any changes to my application, and despite upgrading my servers to the Pro plan, it still behaves this way! I am asking for the reason and want it fixed!


Status changed to Awaiting Railway Response Railway 12 months ago



a year ago

2025-03-15 20:28:27.241 WARN 1 --- [o-8080-exec-131] o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Error: 0, SQLState: null

Mar 15 23:28:27

2025-03-15 20:28:27.241 ERROR 1 --- [o-8080-exec-131] o.h.engine.jdbc.spi.SqlExceptionHelper : HikariPool-1 - Connection is not available, request timed out after 30000ms.

Mar 15 23:28:27

2025-03-15 20:28:27.243 ERROR 1 --- [o-8080-exec-131] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is org.hibernate.exception.JDBCConnectionException: Unable to acquire JDBC Connection] with root cause

The database does not respond within 30,000 ms.


a year ago

499 Error

Attachments


a year ago

These errors all come from your application. Your database vCPU usage spiked on the day you reported the error, which indicates heavy load, which is likely caused by code you pushed out.


Status changed to Awaiting User Response Railway 12 months ago


Status changed to Solved itsrems 12 months ago


Loading...