March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4140) Change distributtion of -Dmcast through testsuite

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-4140?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz edited comment on AS7-4140 at 3/13/12 1:46 PM: ------------------------------------------------------------------- I have confirmed with Andy Taylor that for the standalone-full-ha.xml messaging configuration, the broadcast-group and the discovery-group: - should be using the same multicast channel (i.e. same address and port) - work correctly when using the same multicast channel At present, standalone-full-ha.xml is not used for testing in the AS71 testsuite, as far as I can tell. However, in case it is used in furture, we should update the config generation so that it is properly processed. Therefore, we need to add the messaging configuration to the list of XSL transformations in changeIPAddresses.xsl so that the multicast addresses are replaced by -Dmcast, whether -Dipv6 is true or not. Because the ports used are not used by any other multicast channels, this should work for testing. Ondra, can you set this up? Once this is set up and tested, we can close this issue, I believe. was (Author: rachmato): I have confirmed with Andy Taylor that for the standalone-full-ha.xml messaging configuration, the broadcast-group and the discovery-group: - should be using the same multicast channel (i.e. same address and port) - work correctly when using the same multicast channel At present, standalone-full-ha.xml is not used for testing in the AS71 testsuite, as far as I can tell. However, in case it is used in furture, we should update the config generation so that it is properly processed. Therefore, we need to add the messaging configuration to the list of XSL transformations in changeIPAddresses.xsl so that the multicast addresses are replaced by -Dmcast, whether -Dipv6 is true or not. Because the ports used are not used by any other multicast channels, this should work for testing. Ondra, can you set this up? > Change distributtion of -Dmcast through testsuite > ------------------------------------------------- > > Key: AS7-4140 > URL: https://issues.jboss.org/browse/AS7-4140 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Richard Achmatowicz > Priority: Blocker > Fix For: 7.1.2.Final > > > Please change present behavior. > We need to define only one property -Dmcast (for ex., the name doesn't matter now) as command line parameter - this multicast address is needed to be distributed to every subsystem which manages any multicast communication. It is needed to be unique in every subsystem - JGroups, HornetQ etc. because we must avoid to interfere each other => port assignation must be unique for every a such component. > This change is needed in both - IPV4 and IPv6... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4140) Change distributtion of -Dmcast through testsuite

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-4140?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-4140: ------------------------------------------ I have confirmed with Andy Taylor that for the standalone-full-ha.xml messaging configuration, the broadcast-group and the discovery-group: - should be using the same multicast channel (i.e. same address and port) - work correctly when using the same multicast channel At present, standalone-full-ha.xml is not used for testing in the AS71 testsuite, as far as I can tell. However, in case it is used in furture, we should update the config generation so that it is properly processed. Therefore, we need to add the messaging configuration to the list of XSL transformations in changeIPAddresses.xsl so that the multicast addresses are replaced by -Dmcast, whether -Dipv6 is true or not. Because the ports used are not used by any other multicast channels, this should work for testing. Ondra, can you set this up? > Change distributtion of -Dmcast through testsuite > ------------------------------------------------- > > Key: AS7-4140 > URL: https://issues.jboss.org/browse/AS7-4140 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.1.Final > Reporter: Pavel Janousek > Assignee: Richard Achmatowicz > Priority: Blocker > Fix For: 7.1.2.Final > > > Please change present behavior. > We need to define only one property -Dmcast (for ex., the name doesn't matter now) as command line parameter - this multicast address is needed to be distributed to every subsystem which manages any multicast communication. It is needed to be unique in every subsystem - JGroups, HornetQ etc. because we must avoid to interfere each other => port assignation must be unique for every a such component. > This change is needed in both - IPV4 and IPv6... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-4123) add-user tool doesn't use system properties (configuration or base directories) to write the right property file

by Riccardo Pasquini (JIRA)

Riccardo Pasquini created AS7-4123: -------------------------------------- Summary: add-user tool doesn't use system properties (configuration or base directories) to write the right property file Key: AS7-4123 URL: https://issues.jboss.org/browse/AS7-4123 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Final Environment: rick@myPenguin:~> uname -a Linux myPenguin 3.1.9-1.4-desktop #1 SMP PREEMPT Fri Jan 27 08:55:10 UTC 2012 (efb5ff4) x86_64 x86_64 x86_64 GNU/Linux rick@myPenguin:~> java -version java version "1.6.0_31" Java(TM) SE Runtime Environment (build 1.6.0_31-b04) Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode) boss built using latest sources from github Reporter: Riccardo Pasquini Priority: Minor "Installing" jboss using different jboss base directory or jboss configuration directory makes the add user tool to fail probably due to path hardcoding -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] (JGRP-1437) Documentation problem with getView() (JGroups manual)

by Jean-Philippe Gariepy (JIRA)

Jean-Philippe Gariepy created JGRP-1437: ------------------------------------------- Summary: Documentation problem with getView() (JGroups manual) Key: JGRP-1437 URL: https://issues.jboss.org/browse/JGRP-1437 Project: JGroups Issue Type: Bug Affects Versions: 3.0 Reporter: Jean-Philippe Gariepy Assignee: Bela Ban Priority: Minor There is a contradiction regarding whether or not getView() returns the current view. >From the JGroups 3 manual: {quote} 3.8.7. Getting the current view The following method can be used to get the current view of a channel: public View getView(); This method does not returns the current view of the channel. The current view is updated every time a new view is installed (viewAccepted() callback). Calling this method on an unconnected or closed channel is implementation defined. A channel may return null, or it may return the last view it knew of. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] (JBBUILD-704) Add GPG signature configuration to jboss parent pom

by Paul Gier (Created) (JIRA)

Add GPG signature configuration to jboss parent pom --------------------------------------------------- Key: JBBUILD-704 URL: https://issues.jboss.org/browse/JBBUILD-704 Project: JBoss Build System Issue Type: Enhancement Components: JBoss Parent POM Reporter: Paul Gier Assignee: Paul Gier Fix For: JBoss Parent POM - 8 The JBoss parent pom should include gpg signature configuration in a profile which can be used during release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] (JASSIST-159) StackMapTable is not properly updated (for Java7)

by Paul Lorenz (JIRA)

Paul Lorenz created JASSIST-159: ----------------------------------- Summary: StackMapTable is not properly updated (for Java7) Key: JASSIST-159 URL: https://issues.jboss.org/browse/JASSIST-159 Project: Javassist Issue Type: Bug Affects Versions: 3.15.0-GA Reporter: Paul Lorenz Assignee: Shigeru Chiba Fix For: 3.16.0-GA If a Java7 application on top of Javassist only uses the high-level API (only javassist.* classes), Javassist must be responsible for properly updating stack map tables. However, Javassist does not update a stack map table in some situation. For an application directly using a lower-level API (javassist.bytecode.* classes), updating a stack map table is the responsibility of the application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
7
0 / 0

[JBoss JIRA] (JBBUILD-714) JBoss Parent POM: Upgrade Surefire from 2.10 to 2.12

by Ondrej Zizka (JIRA)

Ondrej Zizka created JBBUILD-714: ------------------------------------ Summary: JBoss Parent POM: Upgrade Surefire from 2.10 to 2.12 Key: JBBUILD-714 URL: https://issues.jboss.org/browse/JBBUILD-714 Project: JBoss Build System Issue Type: Enhancement Reporter: Ondrej Zizka Assignee: Paul Gier Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-4128) allow non-Hibernate persistence providers to be packaged with the application

by Scott Marlow (JIRA)

Scott Marlow created AS7-4128: --------------------------------- Summary: allow non-Hibernate persistence providers to be packaged with the application Key: AS7-4128 URL: https://issues.jboss.org/browse/AS7-4128 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Affects Versions: 7.1.0.Final Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.2.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
6
0 / 0

[JBoss JIRA] (AS7-3696) TS: Fetch and IP adresses dynamically (remove hardcoded strings). [TRACKING]

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3696: --------------------------------- Summary: TS: Fetch and IP adresses dynamically (remove hardcoded strings). [TRACKING] Key: AS7-3696 URL: https://issues.jboss.org/browse/AS7-3696 Project: Application Server 7 Issue Type: Quality Risk Components: Test Suite Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: Ondrej Zizka Priority: Critical The testsuite contains hardcoded URLs, IP adresses and such, on many places. These need to be fetched dynamically from injected Arquillian resources, to allow testing with different IP configurations (e.g. IPv6). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (JBRULES-681) Multi-threaded local search solving

by Geoffrey De Smet (JIRA)

Multi-threaded local search solving ----------------------------------- Key: JBRULES-681 URL: http://jira.jboss.com/jira/browse/JBRULES-681 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Use Future's to spread all possible moves in each step over a number of threads. This number of threads is equal to the number of cpu's by default, as no IO is done during solving. Problems: - each thread will needs it own WorkingMemory and during a step, each working memory will need to be updated - a bunch of classes will need to be thread safe, or at least visibility save, such as bestsolutionrecaller. - Barriers will be needed to collect the result of each step - decks might be a great way to spread out the load -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2012