Skip to content

Conversation

mxm
Copy link
Contributor

@mxm mxm commented Jun 27, 2016

No description provided.

@gyfora
Copy link
Contributor

gyfora commented Jun 27, 2016

I think it is often the case that the timeout is caused by some failure. For instance the savepoint restore failes due to something, then you get this timeout in the command line.

Maybe it's also good to add a note to check the JM log for any failures because increasing the timeout wont help.

Just a thought :)

@mxm
Copy link
Contributor Author

mxm commented Jun 28, 2016

Thanks for the feedback. Savepoint related errors should be forwarded to the client independently of timeouts (except maybe when the savepoint takes too long). So that should be fixed in a follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants