Skip to content

fix: log full stack trace and sequence id in SequenceCheck.checkTableID catch#625

Merged
yamelsenih merged 1 commit into
solop-develop:developfrom
EdwinBetanc0urt:bugfix/sequencecheck-catch-log-stacktrace
Jul 8, 2026
Merged

fix: log full stack trace and sequence id in SequenceCheck.checkTableID catch#625
yamelsenih merged 1 commit into
solop-develop:developfrom
EdwinBetanc0urt:bugfix/sequencecheck-catch-log-stacktrace

Conversation

@EdwinBetanc0urt

Copy link
Copy Markdown
Member

Problem

In SequenceCheck.checkTableID(...), the per-record catch inside the parallel lambda logged only the exception's localized message:

} catch (Exception e) {
    s_log.severe(e.getLocalizedMessage());
}

This discards the stack trace and does not say which sequence failed, which is exactly what hid the original NullPointerException (getCreated() is null) — the log showed a bare message with no origin.

Fix

Log the full exception with the failing sequence id:

} catch (Exception e) {
    s_log.log(Level.SEVERE, "AD_Sequence_ID=" + sequenceId, e);
}

How to test

  1. Force an exception for one sequence during the Sequence Check process.
  2. Before: a single-line message with no stack trace and no sequence reference.
  3. After: SEVERE entry with AD_Sequence_ID=<id> and the full stack trace.

Notes

  • Diagnostics-only change; no functional behavior changes.
  • Level is already imported; touches SequenceCheck.java only.
  • Independent of the other SequenceCheck fixes (verified it auto-merges cleanly with the parallel-logging change).

🤖 Generated with Claude Code

…ID catch

Replace s_log.severe(e.getLocalizedMessage()) with
s_log.log(Level.SEVERE, "AD_Sequence_ID=" + sequenceId, e) so the failing
sequence and the exception stack trace are preserved in the server log.
@yamelsenih yamelsenih merged commit 992f396 into solop-develop:develop Jul 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants