Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
java.sql.SQLException: ORA-12899: value too large for column BATCH_STEP_EXECUTION.EXIT_MESSAGE (actual: 2502, maximum: 2500) [BATCH-2731] #874
We throwed exception with 2 YEN SIGN in message and for too long stack trace we got:
Batch sources for JdbcStepExecutionDao.java has:
and truncateExitDescription() knows nothing about multibyte charsets:
Oleksandr Gavenko commented
It is actually separate issue but in 99.999% of practical cases it can be solved by BATCH-2091.
See me comment at #222 (comment)
Note that there is no final decision on BATCH-2091. It can be even rejected leaving this report unhandled....
We define batch job flow logic in a way when exception occurs we get to step defined by predefined "FAILED" transition which is default for ExitStatus.FAILED.
If such flow is unreliable we should catch all exception explicitly and set StepContribution.setExitStatus("FAILED"); ourselves.
We are not interested in preserving of stacktrace in any BATCH table.