search

vaadin / kubernetes-kit

Other
2 stars 2 forks source link

serialization timeout even with vaadin.serialization.timeout set to 360000 #103

Closed jorgheymans closed 6 months ago

jorgheymans commented 8 months ago

Hi,

For some of our larger pages, we are incurring serialization timeouts even when the timeout is set to 6 minutes.

Regardless of how high we need to set this property to make it work, what is the devmode serialization debug doing that takes more than 6 minutes ? Is this to be expected ?

tamasmak commented 8 months ago

Hi @jorgheymans, Have you already tried to set logging.level.com.vaadin.kubernetes=trace? The serialization debug tool will provide more logs about the process. What do you see then? The serialization process steps are described in the SessionSerializer.

jorgheymans commented 7 months ago

Thank you, i will try your suggestion and report back. Apologies for the late reply.

Just curious, does the session serde mechanism support circular references? We have a large object tree in the session with lots of complex reference data and circular references between some of the classes sometimes happens because of the nature of the data.

tamasmak commented 7 months ago

Yes, the session serde mechanism uses the standard Java serialization that handles circular references. However, in some cases it may fail if there are self references on lambdas. You can read more and find suggestions about this case in the Kubernetes Kit documentation.

tamasmak commented 6 months ago

Closing this issue as there are no more questions.