So I have an array of integers that’s being stored as a process variable. This has been working for a while, but suddenly the query for getting all of my tasks from the task history table fails with this error: Couldn’t deserialize object in variable ‘checkbookIdArray’ There have been updates mad…

As an update on this one: the problem seems linked to the Java version that serializes/deserializes the object structure. First, this problem only showed up after we did a server upgrade (and under the hood, that also entails upgrading the Java version). Second, I confirmed this is the root issue…

Just bumping this as we have the same issue.

[image] jeff.gehly: So the problem now is, how do I maintain the capability to deserialize after a server upgrade? I can’t just kill flowable and rebuild it every time. This is a nuclear option that works in development but is untennable for production. Is it a matter of the JARs, that i need to…

I’ll take a look at that solution and see if it works, but I hadn’t actually considered transmitting the values to the process as JSON, then unpacking the JSON when I need to read the values.

Update on this. Converting to a JSON payload does work. You have to remember to deserialize the JSON when you need to use the array as an object, but it doesn’t store the objects as a byte array anymore, which means I’m not dependent on the JVM versions anymore. I’m going to be working on upgradi…

@jeff.gehly great that it works. One small tip from me. If you are using the objects only in your processes / cases you can access it as an object myObject.field or the ArrayNode as a list. In case you want to use the variables in your Java code and you don’t want to perform the deserialization man…

I’ll keep that in mind. The reason I ran into this was that we read back the process variables to display to the UI, so I can provide the user with an update on the process status, what steps have been completed, etc. This particular array was included with the process variables because it really …

we are also facing the same issue while fetching the history by instance after upgrading flowable 6.4.1 to flowable 6.4.2. Any help here about this?

Hey @janakiram0035 , Can you please create a new post with more information about the problems you are facing? Information about the exceptions you are getting, the type of variables you are storing would make it easier for us to help you. The problem that the original poster had was due to a chang…

Hi filiphr, Can you please give an example how to use a custom Variable Type ?

Unable to serialize object in variable

Flowable Engine

joram March 4, 2019, 8:48am 4

The problem is indeed that serialization can change slightly between JDK versions. The alternative is to not rely on serializable objects, but to store the variables in a format that is not prone to these changes, for example by transforming the object to a json variable (JsonNode) and back.

Topic		Replies	Views
Flowable-Admin - problem with Variables Site Feedback	5	2291	October 2, 2019
Flowable-admin UI fails to show process/task variables Flowable Application	5	1442	October 25, 2017
Flowable transforming JSON/Serializable variables Flowable Engine	7	6154	July 12, 2024
Spring version change causes java.io.InvalidClassException: org.springframework.util.LinkedCaseInsensitiveMap Flowable Engine	3	2497	March 25, 2018
Issue when creating a Variable with a Java Object Flowable Engine	2	687	June 15, 2021

Unable to serialize object in variable

Related topics