Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable zeeq client timeout #293

Open
HMubaireek opened this issue Feb 29, 2024 · 1 comment
Open

Configurable zeeq client timeout #293

HMubaireek opened this issue Feb 29, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@HMubaireek
Copy link

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

@HMubaireek HMubaireek added the enhancement New feature or request label Feb 29, 2024
@saig0
Copy link
Collaborator

saig0 commented Feb 29, 2024

@HMubaireek thank you for raising this. 👍

How many processes did you deploy?

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants