Skip to content

Before doing the node-agent element migration, check if the nodes element already exists - #26170

Open
JackienStephan wants to merge 1 commit into
eclipse-ee4j:mainfrom
JackienStephan:fix-node-agent-config-upgrade
Open

Before doing the node-agent element migration, check if the nodes element already exists#26170
JackienStephan wants to merge 1 commit into
eclipse-ee4j:mainfrom
JackienStephan:fix-node-agent-config-upgrade

Conversation

@JackienStephan

Copy link
Copy Markdown
Contributor

After doing start-domain --upgrade, all the nodes are removed.
I think createDefaultNodeList() should not be done when nodes exists and node-agents not exist.

}
}, domain);
} catch (Exception e) {
Logger.getAnonymousLogger().log(Level.SEVERE,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't be better to move the log to the message of the runtime exception?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just want to follow the same style of the other try-catch of ConfigSupport.apply(..) in this soruce code.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants