Hi again.
I’ve encountered a few problems with the session timeout mechanism of Bonita and wondered whether anyone had any solutions…
First: If you open a form, fill it out and wait for longer than the configured session timeout before clicking “Submit” the system diverts you to the login screen but silently throws the form contents away (ie: the task is not executed), leaving the user unaware that he/she has failed to perform the task. Is there a way to detect this as an error in the form and present the user with an error message?
Second: When “GET” requests are triggered within a form after the timeout, the data that comes back is the HTML content of the login page not (as one would hope) a JSON page indicating a problem.
Third: Setting session-time to more than an hour in the web.xml file causes Bonita to return an error 500 if pages are called for after an hour but before the configured timeout. This seems to be resolvable by setting bonita.tenant.session.duration (default value: 1 hour) to a value higher than the session-timeout, but that begs the question: why are there these two mechanisms in place? And suggests there is a bug with the handling of the duration value.
Chris