October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2040) AS7 TS: Running sets of tests from the command line

by Ondrej Zizka (Moved) (JIRA)

[ https://issues.jboss.org/browse/AS7-2040?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka moved JBQA-5424 to AS7-2040: ----------------------------------------- Project: Application Server 7 (was: JBoss QA) Key: AS7-2040 (was: JBQA-5424) Workflow: GIT Pull Request workflow (was: jira) > AS7 TS: Running sets of tests from the command line > --------------------------------------------------- > > Key: AS7-2040 > URL: https://issues.jboss.org/browse/AS7-2040 > Project: Application Server 7 > Issue Type: Task > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > Work out a way, using profiles, to run: > * unit tests and all integration tests in one shot (needed by dev) > * run the integration tests separately (needed by QA) > Running combinations of integration tests was achieved with the > $AS7/testsuite/build.{sh,bat} scripts, but I wasn't expecting the > requirement to have to be able to do this from $AS7/build.{sh,bat} > entirely. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-2040) AS7 TS: Running sets of tests from the command line

by Ondrej Zizka (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-2040?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-2040: ------------------------------ Component/s: Test Suite > AS7 TS: Running sets of tests from the command line > --------------------------------------------------- > > Key: AS7-2040 > URL: https://issues.jboss.org/browse/AS7-2040 > Project: Application Server 7 > Issue Type: Task > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > Work out a way, using profiles, to run: > * unit tests and all integration tests in one shot (needed by dev) > * run the integration tests separately (needed by QA) > Running combinations of integration tests was achieved with the > $AS7/testsuite/build.{sh,bat} scripts, but I wasn't expecting the > requirement to have to be able to do this from $AS7/build.{sh,bat} > entirely. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-2039) Prevent removal of server configuration that are still running

by Heiko Braun (Created) (JIRA)

Prevent removal of server configuration that are still running -------------------------------------------------------------- Key: AS7-2039 URL: https://issues.jboss.org/browse/AS7-2039 Project: Application Server 7 Issue Type: Enhancement Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Beta1 -- 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

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] (AS7-2038) TS: Tests grouping

by Ondrej Zizka (Created) (JIRA)

TS: Tests grouping ------------------ Key: AS7-2038 URL: https://issues.jboss.org/browse/AS7-2038 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Ondrej Zizka Assignee: Ondrej Zizka {code} @Test (groups = {"JMS", "XA"}) {code} or the new style {code} @Category( Integration.class ) {code} -- 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

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported

by Nicolas Estrada (JIRA)

Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported ----------------------------------------------------------------------------------------- Key: JGRP-1371 URL: https://issues.jboss.org/browse/JGRP-1371 Project: JGroups Issue Type: Bug Affects Versions: 2.12.1 Environment: All Reporter: Nicolas Estrada Assignee: Bela Ban Priority: Critical If a positive timeout is specified for the FLUSH protocol, if the specified waiting time timeout elapses during the notBlockedDown.await(timeout) invocation, the shouldSuspendByItself flag will be set but it will continue looping forever. The if clause below should be moved into the while block. If the timeout is 0L or negative, instead of waiting forever, it will instantaneously return from the await(timeout) method, but seeing as it can never suspend itself as mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is received. Changing the method to await() for "eternal" timeouts may be dangerous however; There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH coordinator fails. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JGRP-1366) CounterService: distributed counter

by Bela Ban (JIRA)

CounterService: distributed counter ----------------------------------- Key: JGRP-1366 URL: https://issues.jboss.org/browse/JGRP-1366 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 Provide a CounterService class (similar to LockService), which communicates with a protocol. Provide methods similar to what's in AtomicInteger, e.g. get(), compareAndSet(), incrAndGet(), decrAndGet() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
3
0 / 0

[JBoss JIRA] (AS7-2037) Broadcast port on HornetQ config gets ignored

by Andy Taylor (Created) (JIRA)

Broadcast port on HornetQ config gets ignored --------------------------------------------- Key: AS7-2037 URL: https://issues.jboss.org/browse/AS7-2037 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.Alpha1 Reporter: Andy Taylor Assignee: Andy Taylor Fix For: 7.1.0.Beta1 When configuring the broadcast-group the port configuration is ignored and 0 is always used. This is because it is created first with a 0 setting so the Binding Service can be created but never reset to the proper configuration -- 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

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-2024) JDBC Driver registry does not unregister properly

by Tristan Tarrant (Created) (JIRA)

JDBC Driver registry does not unregister properly ------------------------------------------------- Key: AS7-2024 URL: https://issues.jboss.org/browse/AS7-2024 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Alpha1 Reporter: Tristan Tarrant Assignee: Stefano Maestri Priority: Minor org.jboss.as.connector.registry.DriverRegistryImpl in as7 trunk I think line 62 is a copy/paste bug: {code:title=DriverRegistryImpl.java} @Override public void unregisterInstalledDriver(InstalledDriver driver) { if (driver == null) throw new IllegalArgumentException(MESSAGES.nullVar("driver")); DEPLOYMENT_CONNECTOR_REGISTRY_LOGGER.tracef("Removing deployment: %s", driver); synchronized (drivers) { drivers.put(driver.getDriverName(), driver); } } {code} should be {code:title=DriverRegistryImpl.java} @Override public void unregisterInstalledDriver(InstalledDriver driver) { if (driver == null) throw new IllegalArgumentException(MESSAGES.nullVar("driver")); DEPLOYMENT_CONNECTOR_REGISTRY_LOGGER.tracef("Removing deployment: %s", driver); synchronized (drivers) { drivers.remove(driver.getDriverName()); } } {code} -- 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

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-2000) resteasy async bug

by Stanislav Minar (Created) (JIRA)

resteasy async bug ------------------ Key: AS7-2000 URL: https://issues.jboss.org/browse/AS7-2000 Project: Application Server 7 Issue Type: Bug Components: REST Affects Versions: 7.0.2.Final Reporter: Stanislav Minar IllegalAccessError when submitting response to org.jboss.resteasy.spi.AsynchronousResponse. Due to this issue resteasy async is not usable at all :( java.lang.IllegalAccessError: tried to access field org.jboss.resteasy.plugins.server.servlet.HttpServletInputMessage.dispatcher from class org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$1: java.lang.IllegalAccessError: tried to access field org.jboss.resteasy.plugins.server.servlet.HttpServletInputMessage.dispatcher from class org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$1 at org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$1.setResponse(Servlet3AsyncHttpRequest.java:47) [async-http-servlet-3.0-2.2.1.GA.jar:] -- 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

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-2019) maven-jaxws-tools-plugin <target> option is undocumented

by Steve Cohen (Created) (JIRA)

maven-jaxws-tools-plugin <target> option is undocumented -------------------------------------------------------- Key: AS7-2019 URL: https://issues.jboss.org/browse/AS7-2019 Project: Application Server 7 Issue Type: Bug Components: Documentation, Web Services Reporter: Steve Cohen Assignee: Alessio Soldano Priority: Minor The wsconsume goal of the maven-jaxws-tools-plugin is documented here: http://community.jboss.org/wiki/JBossWS-Wsconsume#Maven_Plugin. This documentation does not mention the <target> configuration option which I needed. The command-line documentation on the same page, ie. http://community.jboss.org/wiki/JBossWS-Wsconsume#Command_Line_Tool does list the --target option, so I decided to give it a try in the plugin and it works. This should be documented. -- 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

12 years, 6 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011