[jboss-jira] [JBoss JIRA] (WFLY-679) Arquillian Managed Container does not honor configured ports

[Tomaz Cerar (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar resolved WFLY-679.
------------------------------

    Fix Version/s: 8.0.0.Final
                       (was: Awaiting Volunteers)
       Resolution: Done


This was fixed some time ago.
                
> Arquillian Managed Container does not honor configured ports
> ------------------------------------------------------------
>
>                 Key: WFLY-679
>                 URL: https://issues.jboss.org/browse/WFLY-679
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Karel Piwko
>             Fix For: 8.0.0.Final
>
>
> When starting a managed container, following configuration is not used by Arquillian:
> {code}
> <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>       
> {code}
> 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.

--
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