Navigation Menu

Skip to content
This repository has been archived by the owner on Jun 7, 2021. It is now read-only.

SWARM-612: jboss-cli reload results in 404 / no deployment #218

Merged
merged 2 commits into from Nov 14, 2016
Merged

SWARM-612: jboss-cli reload results in 404 / no deployment #218

merged 2 commits into from Nov 14, 2016

Conversation

heiko-braun
Copy link
Contributor

  • Have you followed the guidelines in our Contributing document?
  • Have you created a JIRA and used it in the commit message?
  • Have you checked to ensure there aren't other open Pull Requests for the same issue?
  • Have you built the project locally prior to submission with mvn clean install?

Motivation

Using the management tools to :reload a live Swarm instance, caused the deployment to disappear.

Modifications

Swarm does now, like WildFly, keep a copy of the server configuration around, that it can read back when the server reloads.

Result

Start a server, :reload it using the CLI and the deployment is still registered with the node.

@heiko-braun
Motivation
c570587 
Using the management tools to :reload a live Swarm instance, caused the deplyment to disappear.

Modifications

Swarm dows now, like WildFly, keep a copy of the server configuration around, that it can read back when the server reloads.

Result

Start a server, :reload it using the CLI and the deployment is still registered with the node.
@heiko-braun
Don’t hang on to the service container outside #start()
548b073
@heiko-braun heiko-braun mentioned this pull request Nov 11, 2016
Merged
4 tasks
@heiko-braun heiko-braun reopened this Nov 14, 2016
@heiko-braun
Copy link
Contributor Author

Accidentally closed this one

@heiko-braun heiko-braun merged commit f83bd47 into thorntail:master Nov 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
1 participant
@heiko-braun