Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-11854

AS7 management port not always detected correctly

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.3.0.CR1
    • 3.3.0.Beta3
    • server
    • None
    • Hide

      1. Add AS7 server with management port set to 9899 in standalone.xml
      2. Start the server - the server will be started correctly in a few seconds - this means the management port is detected correctly, perfect
      3. Stop the server, remove the server runtime and server adapter
      4. Change the management port of your AS7 server to 9799 in standalone.xml
      5. Add the server again
      6. Try to start the server - this time it will be "starting" until it reaches timeout, because it will assume the management port is again 9899 - FAIL

      Show
      1. Add AS7 server with management port set to 9899 in standalone.xml 2. Start the server - the server will be started correctly in a few seconds - this means the management port is detected correctly, perfect 3. Stop the server, remove the server runtime and server adapter 4. Change the management port of your AS7 server to 9799 in standalone.xml 5. Add the server again 6. Try to start the server - this time it will be "starting" until it reaches timeout, because it will assume the management port is again 9899 - FAIL

    Description

      Sometimes when you change the management port in standalone.xml in your AS7 server, the changes doesn't get reflected in JBT tooling. Perhaps something to do with caching?

      Important side question: Is the management port (in server editor) detected everytime you start the server? If only in the time of adding the server, then the UI should be different. But this JIRA is relevant anyway.

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users JBIDE-12153 Refresh server ports when server is added

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-11483 AS7 / EAP6 management port should be exposed via api rather than hard-coded for as71 jmx connection

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: