Concern about 500 Error #5473
Replies: 3 comments
-
Is that the only information relevant in the logs? Is there no full stack trace? Does this happen on startup? |
Beta Was this translation helpful? Give feedback.
-
Hi, Let me share a full trace of the logs with you. The issue occurs during runtime, not just at start/restart. Additionally, the 500 error is now appearing as a 404 error for various endpoints, even for non-users. `2024-11-13 07:48:23 INFO <> [io.apicurio.common.apps.logging.audit.AuditLogService] (executor-thread-11068) apicurio.audit action="request" result="failure" src_ip="null" path="/6003d62d7f921837125fc3292f6622f5.txt" response_code="404" method="GET" user="" 2024-11-13 08:00:06 INFO <> [io.apicurio.registry.metrics.health.liveness.ResponseErrorLivenessCheck] (executor-thread-11077) After this event, the error counter is 18 (out of the maximum 5 allowed). 2024-11-13 08:00:19 INFO <> [io.apicurio.common.apps.logging.audit.AuditLogService] (executor-thread-11087) apicurio.audit action="exportData" result="success" src_ip="172.31.35.45" x_forwarded_for="52.208.21.11" principal_id="e535c061-0b8f-4675-8cd0-267d6e852365" for_browser="false" Regards |
Beta Was this translation helpful? Give feedback.
-
Are you performing some sort of penetration testing? The routes you have for the requests seem to indicate that:
If not, better check what's going one with your server, because that is for sure not normal. None of those requests are performed by the UI or any regular client application. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone!
I've deployed apicurio/apicurio-registry-sql:2.6.5.Final into an EC2 with Docker and I saw these errors (just 10 occurrences) and UI and API always working fine:
WARN <_> [io.apicurio.registry.metrics.health.liveness.ResponseErrorLivenessCheck] (executor-thread-84) Liveness problem suspected in ResponseErrorLivenessCheck because of an exception: : java.lang.IllegalStateException: UT010005: Cannot call getOutputStream(), getWriter() already called INFO <_> [io.apicurio.registry.metrics.health.liveness.ResponseErrorLivenessCheck] (executor-thread-84) After this event, the error counter is 1 (out of the maximum 5 allowed). WARN <_> [io.apicurio.registry.metrics.health.liveness.ResponseErrorLivenessCheck] (executor-thread-174) Liveness problem suspected in ResponseErrorLivenessCheck because of an exception: : java.lang.IllegalStateException: UT010005: Cannot call getOutputStream(), getWriter() already called ERROR <_> [io.apicurio.registry.services.http.RegistryExceptionMapperService] (executor-thread-174) [500 ERROR DETECTED] : UT010005: Cannot call getOutputStream(), getWriter() already called: java.lang.IllegalStateException: UT010005: Cannot call getOutputStream(), getWriter() already called
I would like to understand the reason or if I can do something.
Thank you for your help!
César.
Beta Was this translation helpful? Give feedback.
All reactions