[FINERACT-1168] Integration Tests failure due to internal server errors should show server side failure stack trace

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.7.0
• Assignee: Aleksandar Vidakovic
• Reporter: Michael Vorburger
• Created: 30/Sep/20 19:32
• Updated: 06/May/22 07:59
• Resolved: 06/May/22 07:59

Description

IT failures like FINERACT-1167, already raised in FINERACT-927, are a PITA (impossible) to debug.

This is an IT failure due to a #500 means "something internal went wrong on the server" - but we don't know what...

To know what the problem was, the server should return the exception in the HTTP body of the 500 response. The IT should then capture that, and include it in the JUnit test failure.

But in production, 500 errors should NOT show the stack trace - that is typically considered a security problem. So we need some env var / sys prop to enable it, just for debugging. Spring Boot probably actually already has some... knob, for this?

Petri Tuomola thought this may interest you.

Issue Links

• blocks: FINERACT-1167 SchedulerJobsTest: Expected status code <202> but was <500>
• blocks: FINERACT-1256 Bulk Import Template generation should not fail for (office) names containing hyphens and other characters invalid as Sheet Range Names
• blocks: FINERACT-1590 Release Apache Fineract 1.7.0
• is blocked by: FINERACT-1199 Jersey (JAX RS implementation) & Tomcat logging needs to be configured to use slf4j instead of JUL
• is blocked by: FINERACT-1200 OpenJPA logging to slf4j
• is blocked by: FINERACT-764 Run Integration Tests using Spring Boot IT support instead of on Tomcat started separately by gradle-tomcat-plugin
• is blocked by: FINERACT-982 Completely ditch use of Drizzle JDBC Driver after all
• is blocked by: FINERACT-890 Custom slf4j integrated logger for the (optional!) MySQL JDBC driver support in Fineract
• links to: GitHub Pull Request #1495