Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-679

Arquillian Managed Container does not honor configured ports

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.Final
    • None
    • None
    • None
    • Workaround Exists
    • Hide

      Modify standalone.xml in ${jboss.home}/standalone/configuration/standalone.xml by hand before starting Arquillian tests.

      Show
      Modify standalone.xml in ${jboss.home}/standalone/configuration/standalone.xml by hand before starting Arquillian tests.

    Description

      When starting a managed container, following configuration is not used by Arquillian:

      <container qualifier="container" default="true">
            <configuration>
                <property name="jbossHome">target/jbossas-2</property>
                <property name="managementPort">19999</property>
                <property name="jmxPort">1190</property>
                <property name="httpPort">8180</property>
                <property name="startupTimeoutInSeconds">180</property>
            </configuration>
            <!-- 
                [ARQ-425] config parser code not in sync with schema
                Make executionType configurable
             -->
            <protocol type="jmx-as7">
                <configuration>
                    <property name="executionType">REMOTE</property>
                </configuration>
            </protocol>
        </container>

      The standalone container is always started on default ports, e.g. 9999, 1099, 8080.
      The ports are defined in standalone.xml and it seems difficult to change them without touching the file. See
      http://community.jboss.org/thread/168140 for related question.

      This makes customization of the test runs with managed containers difficult and for clusters even more difficult.

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. WFLY-749 JBoss AS lifecycle controlling tests

          • 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.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              kpiwko Karel Piwko
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: