Details
L3 - Default Description
Problem description:
- given:
- a shared engine
- the attached process definition is deployed on the engine
- two process applications are deployed on the application server (A and B)
- App A has a custom object serializer deployed
- when:
- I start a process instance on app A of the given process definition with an object variable
- App B performs a process instance modification where the timer event is cancled and the token moved to the gateway
- the object variable is being deserialized after the gateway
- then:
- the process instance modifcation cannot be executed because the wrong serialized is used (see attached stacktrace)
- expected:
- The right serializer ist and the instance modification works
Hint:
We should check if it is necessary that the TypedValueField loads the variable serializer by default:
https://github.com/camunda/camunda-bpm-platform/blob/master/engine/src/main/java/org/camunda/bpm/engine/impl/persistence/entity/util/TypedValueField.java#L281-L285