[
https://issues.jboss.org/browse/AS7-1036?page=com.atlassian.jira.plugin.s...
]
Karel Piwko updated AS7-1036:
-----------------------------
Description:
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.
was:
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, 8180.
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.
Forum Reference:
http://community.jboss.org/thread/168140 (was:
http://community.jboss.org/thread/168140)
Arquillian Managed Container does not honor configured ports
------------------------------------------------------------
Key: AS7-1036
URL:
https://issues.jboss.org/browse/AS7-1036
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Reporter: Karel Piwko
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira