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
{{ message }}
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.
It does seem to be a bug indeed. But in the current implementation run() actually launches the business app, but instead of updating in parallel it blocks and completes the update on shutdown.
I am new to Update4J and maybe I am totally wrong, but I tried to use the DefaultBoostrap with "--launchFirst" and it did not update at all.
java -cp update4j-1.4.5.jar org.update4j.Bootstrap --local update-config.xml --remote http://<server:port>/application/config.xml --syncLocal --launchFirst --singleInstance
Without "--launchFirst" it works fine.
I think I identified the issue with a blocking call to the application (see pull request).
This should have never worked in the first place. Did I miss something?
The text was updated successfully, but these errors were encountered: