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

[Bug]: hop-run exits too quickly to properly handle all finished listeners #2868

Closed
mattcasters opened this issue Apr 26, 2023 · 0 comments
Closed
Assignees
Labels
API bug P2 Default Priority
Milestone

Comments

@mattcasters
Copy link
Contributor

Apache Hop version?

2.4.0

Java version?

openjdk version "11.0.17" 2022-10-18

Operating system

Linux

What happened?

The hop-run command line tool forces a System.exit() at the end. It appears that it's possible that there are still some PipelineFinished listeners active at that point. This causes for example execution information location information (state at the end) not to be logged propertly.

Issue Priority

Priority: 2

Issue Component

Component: API

@mattcasters mattcasters self-assigned this Apr 26, 2023
@mattcasters mattcasters added this to the 2.5 milestone Apr 26, 2023
@github-actions github-actions bot added P2 Default Priority API labels Apr 26, 2023
mattcasters added a commit to mattcasters/hop that referenced this issue Apr 26, 2023
mattcasters added a commit to mattcasters/hop that referenced this issue Apr 27, 2023
bamaer added a commit that referenced this issue May 2, 2023
bamaer pushed a commit to bamaer/hop that referenced this issue May 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API bug P2 Default Priority
Projects
None yet
Development

No branches or pull requests

2 participants