[JBoss JIRA] Created: (JBAS-7981) Use of jgroups.tcpping.initial_hosts in example JGroups configurations
by Brian Stansberry (JIRA)
Use of jgroups.tcpping.initial_hosts in example JGroups configurations
----------------------------------------------------------------------
Key: JBAS-7981
URL: https://jira.jboss.org/jira/browse/JBAS-7981
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: JBossAS-6.0.0.M4
The TCP JGroups configurations use the property jgroups.tcpping.initial_hosts for the example TCPPING configurations.
<TCPPING timeout="3000"
initial_hosts="${jgroups.tcpping.initial_hosts:localhost[7600],localhost[7601]}"
port_range="1"
num_initial_members="3"/>
This is the internal JGroups property that overrides all TCPPING.initial_hosts values.
This property should not be used here, as it encourages users to set this property, which has the unintended consequence of overriding *all* TCPPING.initial_hosts values.
Investigate jboss.partition.udpGroup as well, although JGroups shouldn't be using properties in the jboss namespace any more.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years
[JBoss JIRA] Created: (JBAS-7561) Integrate AS module-level tests into smoke tests
by Brian Stansberry (JIRA)
Integrate AS module-level tests into smoke tests
------------------------------------------------
Key: JBAS-7561
URL: https://jira.jboss.org/jira/browse/JBAS-7561
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.CR1
A number of modules in the AS testsuite include tests that are never getting executed. How these are organized varies by module; typical is src/tests/org/jboss... with a build-test.xml file used to build and execute them via ant.
These have never been part of the overall build (e.g. the way the maven 'test' goal is executed as part of 'install') nor are they run as part of the testsuite. With the mavenization of AS trunk, these tend to not even work via ant. But there are quite a number of meaningful tests that should not just be abandoned.
This JIRA is a parent task for module-specific subtasks.
The intent is to get these working via the maven 'test' goal. However, at this point we don't want to increase the already lengthy build time of trunk by executing them as part of a default install. However, we do want the hudson build to execute them and include the results with the smoke-tests target output it publishes. Perhaps we'll execute them via the smoke-tests target itself.
These tests are meant to be fast unit tests, so any lengthy ones we find should probably be moved to the testsuite module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years