I think I know how to reproduce. It occurs when the JBoss runtime is set to a directory different from the default (server). If the name of the server you select doesn't match one from the default servers, the port won't be resolved.
And I think the real reason is that the xpath of all the ports as a root directory to "server/${jboss_config}". My guess is that it is wrong and should be "D:\my_different_server_directory\${jboss_config}"
I also noticed that a tmp/jbosstoolsTemp dir is created in "server/${jboss_config}" instead of "D:\my_different_server_directory\${jboss_config}"
- is cloned by
-
JBDS-1677 Server cannot be saved for the following reasons: One or more ports have an invalid value
- Closed