Skip to content

Fixed NPE when check 'behind-proxy' is enabled or not on an ssh node. - #26167

Open
JackienStephan wants to merge 2 commits into
eclipse-ee4j:mainfrom
JackienStephan:fix-admin-auth-check-proxy
Open

Fixed NPE when check 'behind-proxy' is enabled or not on an ssh node.#26167
JackienStephan wants to merge 2 commits into
eclipse-ee4j:mainfrom
JackienStephan:fix-admin-auth-check-proxy

Conversation

@JackienStephan

Copy link
Copy Markdown
Contributor

When isBehindProxyEnabled() method is executed on a remote node instance,
for example, execute the start-instance command on das, and the target is an instance on an ssh node,
a server element named "server" cannot be found in the instance's domain.xml.

So domain.getServerNamed("server") here returns null, resulting in NPE when call getConfig().
It would be better to find the server element of the current instance.

With this issue, start-instance command targeting on ssh instances would succeed, but list-instance cannot get the correct running status of target instances. It would always be "stopped".
Then stop-instance command on the target instances always timeout.
The only temporary workaround I found for now, is to ssh to the remote instance server and execute stop-local-instance.

When isBehindProxyEnabled() method is executed on a remote node instance,
for example, execute the start-instance command on das, and the target is an instance on an ssh node,
a <server> element named "server" cannot be found in the instance's domain.xml.
would result in NPE when call "getConfig()" method.
it would be better to find the <server> element of the current instance.
@dmatej
dmatej requested a review from arjantijms August 7, 2026 19:18
@dmatej dmatej added this to the 8.0.5 milestone Aug 7, 2026
@dmatej dmatej added the bug Something isn't working label Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants