You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Processes list show empty results although there are processes. It turns out that the timeout value is hardcoded to 5000 ms, while the actual query took 18 seconds in my environment.
Describe the solution you'd like
Make the timeout value configurable somehow. I have hazelcast, zeebe, postgresql and zeeq all installed independently. I managed to configure zeebe-play to connect to them (except zeeq there's no option for remote configuration). However, it seems the default limit of 5000 ms is not enough for this setup, it would work with everything embedded, and with short list of processes.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
If the query takes 18 seconds then it's a lot. Even if you could configure the timeout, you would need to wait 18 seconds until the processes are loaded. It doesn't sound like a great UX.
How do you use Play?
Can you clear your state after a while?
Is your feature request related to a problem? Please describe.
Processes list show empty results although there are processes. It turns out that the timeout value is hardcoded to 5000 ms, while the actual query took 18 seconds in my environment.
Describe the solution you'd like
Make the timeout value configurable somehow. I have hazelcast, zeebe, postgresql and zeeq all installed independently. I managed to configure zeebe-play to connect to them (except zeeq there's no option for remote configuration). However, it seems the default limit of 5000 ms is not enough for this setup, it would work with everything embedded, and with short list of processes.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: