Apr 12th, 2012, 07:12 AM
BATCH_STEP_EXECUTION_CONTEXT.SHORT_CONTEXT truncation leads to invalid serialisation.
What is the expected usage for SHORT_CONTEXT in relation to SERIALIZED_CONTEXT ? We are experiencing xstream deserialisation errors when using the Spring Batch Admin SimpleJobExplorer. The JdbcStepExecutionDao
attempts to retrieve a step execution context where the data when stored has exceeded the column width - the data is truncated, so xstream fails to parse it.
What is baffling is that the SERIALIZED_CONTEXT column contains the entire set of data in a valid form. So what is the point of the SHORT_CONTEXT and it leading to failures like this.
We do understand that the execution context should only contain small things - in our case its an array of 200 strings (!) - which we will fix. But its not clear to me how the two columns relate to each other.