[jbosstools-issues] [JBoss JIRA] (JBIDE-12960) jboss.bind.address.management is set after unchecking Expose management port for remote server

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731648#comment-12731648 ] 

Rob Stryker commented on JBIDE-12960:
-------------------------------------

Hey Martin:

I think I might reject this issue. Details below. I recently updated the UI to show a larger box for start args (JBIDE-12991), and I suspect that's what's causing your issue (maybe).  I suspect you unchecked "detect automatically" in the UI, and that's why the values aren't being overridden. 

What I am seeing now is as follows:
1. Set up a remote as7 server (use the defaults for startup polling etc.)
2. Open the server editor (Server view -> double click the server)
3. Check "Expose your management port..." in the server editor and save it
4. Click Open launch configuration and check you have something like this in the Start Command:
-Djboss.bind.address.management=MARVIN.BRQ.REDHAT.COM - OK
5. In the server editor, uncheck the option (Expose your management port...) and save
6. Click Open launch configuration and check the Start Command - you do NOT SEE the management binding
-Djboss.bind.address.management=MARVIN.BRQ.REDHAT.COM  - THIS IS OK. 

Only when I follow the following steps, do I replicate your issue:
1. Set up a remote as7 server (use the defaults for startup polling etc.)
2. Open the server editor (Server view -> double click the server)
3. Check "Expose your management port..." in the server editor and save it
4. Click Open launch configuration and THEN UNCHECK "DETECT AUTOMATICALLY", and see:
-Djboss.bind.address.management=MARVIN.BRQ.REDHAT.COM - OK
5. In the server editor, uncheck the option (Expose your management port...) and save
6. Click Open launch configuration and check the Start Command - you WILL STILL SEE something like this:
-Djboss.bind.address.management=MARVIN.BRQ.REDHAT.COM


In the second case, the bug *is* there, but it is intentional. Once a user unchecks 'detect automatically', the current values are saved, and will no longer be affected by changes to the editor. SO for example, when you first uncheck 'detect automatically', it makes whatever is in the textbox be the final arguments. At that time, the arguments include the management port exposing. 

The reason it is like this is because a user may choose not to expose automatically, and then choose to write his own arguments in directly, such as -Djboss.bind.address.management=some.internal.ip.  If every startup (or load of the argument page) we decide to "clear out" this flag because the checkbox is not set in the server editor, users will have no way to expose management address on anything other than the default provided by the server editor. 

I suspect the changes from JBIDE-12991 will help you re-run this use case (maybe tomorrow?) and verify the situation. I suspect you needed to uncheck "detect automatically" to see whether or not the management port was exposed, and you forgot to re-check it before closing the page. 


                
> jboss.bind.address.management is set after unchecking Expose management port for remote server
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12960
>                 URL: https://issues.jboss.org/browse/JBIDE-12960
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.0.Beta1
>         Environment: JBDS 6.0.0.Beta1c B58
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.CR1
>
>
> When you create a remote AS7 server and check Expose management port in the server editor, this is added to the start command:
> -Djboss.bind.address.management=your.server.host.name
> If you uncheck the option again, it should be removed from the command. But it's not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira