Re: [I] [Bug]: Multiple Hop Server Object IDs for a single HOP Pipeline on the HOP Server (hop)
hansva closed issue #4086: [Bug]: Multiple Hop Server Object IDs for a single HOP Pipeline on the HOP Server URL: https://github.com/apache/hop/issues/4086 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] [Bug]: Multiple Hop Server Object IDs for a single HOP Pipeline on the HOP Server (hop)
hansva commented on issue #4086: URL: https://github.com/apache/hop/issues/4086#issuecomment-5002771135 This issue was actually solved in 2.10, but I am hardening the code a bit -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] [Bug]: Multiple Hop Server Object IDs for a single HOP Pipeline on the HOP Server (hop)
hansva commented on issue #4086: URL: https://github.com/apache/hop/issues/4086#issuecomment-5002680866 .take-issue -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
Re: [I] [Bug]: Multiple Hop Server Object IDs for a single HOP Pipeline on the HOP Server (hop)
Raul-rp commented on issue #4086: URL: https://github.com/apache/hop/issues/4086#issuecomment-4271426674 **BUG: Multiple Object IDs ( Object ID Becomes Orphaned in Hop Server 2.17)** This issue typically appears when: The same pipeline/workflow is executed or deployed multiple times Hop Server keeps metadata in memory and concurrent executions The object remains in memory as a running execution without any relationship to the UI; therefore, it cannot be stopped or cleaned up except by restarting the long‑lived container. The issue is very difficult to reproduce. @hansva -> **Would it be possible to implement a mechanism to prevent this and automatically clean up any workflow/pipeline Object IDs that become orphaned and no longer appear in the UI menu?** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
