January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen reassigned AS7-3128: ---------------------------------- Assignee: Andrew Rubinger (was: Aslak Knutsen) > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Blocker > Labels: arq_qe_blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2203) Add Arquillian Container support for AS 7 domain controller

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran updated AS7-2203: ------------------------------------ Priority: Critical (was: Major) Increasing priority as we have been waiting on this for a while. > Add Arquillian Container support for AS 7 domain controller > ------------------------------------------------------------ > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Aslak Knutsen > Priority: Critical > Labels: arq_qe_blocker > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8337) handling of deployment failed at batch resolve time

by Alexey Loubyansky (JIRA)

handling of deployment failed at batch resolve time --------------------------------------------------- Key: JBAS-8337 URL: https://jira.jboss.org/browse/JBAS-8337 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Types of failures here include: duplicate service definition (i.e. a service was defined that already exists in the container), missing required dependency (i.e. a service was defined that depends on something that isn't there), circular dependency (i.e. two or more service definitions represent circularity in terms of their dependency links). Right now this erases the entire batch, which means that the server cannot start if any of these errors occur. The correct behavior is, in my opinion, to log each error and continue, possibly yielding a report of problem services after the batch is resolved (it is likely, however, that one failure will lead to others). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8336) handling of deployment failed the validation on the domain controller

by Alexey Loubyansky (JIRA)

handling of deployment failed the validation on the domain controller --------------------------------------------------------------------- Key: JBAS-8336 URL: https://jira.jboss.org/browse/JBAS-8336 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Fix For: 7.0.0.M1 A deployment can fail validation on the domain controller. In this event, the deployment is not added to the domain and an error is thrown from the deployer API, so this does not impact the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (AS7-1163) The license of JBoss AS itself is not evident in the distribution

by Dimitris Andreadis (JIRA)

The license of JBoss AS itself is not evident in the distribution ----------------------------------------------------------------- Key: AS7-1163 URL: https://issues.jboss.org/browse/AS7-1163 Project: Application Server 7 Issue Type: Task Components: Build System Affects Versions: 7.0.0.CR1 Reporter: Dimitris Andreadis Assignee: Paul Gier Priority: Critical Fix For: 7.0.0.Final When looking in the distribution, it's not evident what is the license of the application server itself. We have the licenses for the various subsystems in docs/licenses and the docs/licenses/licenses.xml containing entries like <dependency> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-build-config</artifactId> <version>7.0.0.CR1</version> <licenses> <license> <name>lgpl</name> <url>http://repository.jboss.org/licenses/lgpl-2.1.txt</url> </license> </licenses> </dependency> But I think we need something more explicit like we had in previous releases. Maybe a txt file LICENSE.txt either in docs/licenses, or in the top level directory. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
4
0 / 0

[JBoss JIRA] (AS7-3201) CLI: rollout-plan add command with malformed plan crashes CLI

by Dominik Pospisil (Created) (JIRA)

CLI: rollout-plan add command with malformed plan crashes CLI ------------------------------------------------------------- Key: AS7-3201 URL: https://issues.jboss.org/browse/AS7-3201 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.CR1b Reporter: Dominik Pospisil Assignee: Alexey Loubyansky The rollout-plan add command with malformed plan crashes CLI. Steps to reproduce. 1) connect to a domain 2) rollout-plan add --name=testPlan --content=test Console crashes with: java.lang.IllegalArgumentException: newValue is null at org.jboss.dmr.ModelNode.set(ModelNode.java:503) at org.jboss.as.cli.handlers.GenericTypeOperationHandler.buildOperationRequest(GenericTypeOperationHandler.java:514) at org.jboss.as.cli.handlers.GenericTypeOperationHandler.buildRequest(GenericTypeOperationHandler.java:358) at org.jboss.as.cli.handlers.BaseOperationCommand.doHandle(BaseOperationCommand.java:183) at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:84) at org.jboss.as.cli.impl.CommandContextImpl.processLine(CommandContextImpl.java:449) at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:983) at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:174) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.jboss.modules.Module.run(Module.java:248) at org.jboss.modules.Main.main(Main.java:313) -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1920) Support non-Zip based archives for deployment

by Jesper Pedersen (JIRA)

Support non-Zip based archives for deployment --------------------------------------------- Key: AS7-1920 URL: https://issues.jboss.org/browse/AS7-1920 Project: Application Server 7 Issue Type: Task Reporter: Jesper Pedersen Assignee: Jason Greene We need to support file deployments that aren't a ZIP based archive. These deployments should also be passed through the DUPs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
17
0 / 0

[JBoss JIRA] (AS7-2269) HornetQ Restful inteface does not work when queues are configured in AS7 config files

by Mitchell Ackerman (Created) (JIRA)

HornetQ Restful inteface does not work when queues are configured in AS7 config files ------------------------------------------------------------------------------------- Key: AS7-2269 URL: https://issues.jboss.org/browse/AS7-2269 Project: Application Server 7 Issue Type: Bug Components: JMS, REST Affects Versions: 7.0.2.Final Environment: Windows 7, Java 1.6.0_26, JBoss AS 7.0.2.Final, HornetQ 2.2.7, HornetQRest 2.2.6 Reporter: Mitchell Ackerman Assignee: Clebert Suconic When HornetQ queues are configured in AS7 config files (i.e., standalone.xml), The HornetQ Restful inteface does not work. Upon examining the AS7 modules, the rest interface libraries are not even included, so it is not surprising that it does not work. If the libraries are bundled with a webapp, REST still does not work. The workaround I have is to remove HornetQ from the AS7 configuration, configure HornetQ using the standard HornetQ configuration files (hornetq-configuration.xml, hornetq-jms, ...), and bundle the HornetQ libraries with the webapp. When doing that, however, the HornetQ queues/topics are not shown in the AS7 console JNDI. As an example, you can use HornetQRestExamples/jms-to-rest, and change configuration of the queues to AS7, in which case REST will not work. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3358) CLONE - NullPointerException when HQ backup server is shutting down after clean shutdown

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3358?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-3358: ------------------------------------- Assignee: Andy Taylor (was: Clebert Suconic) > CLONE - NullPointerException when HQ backup server is shutting down after clean shutdown > ---------------------------------------------------------------------------------------- > > Key: AS7-3358 > URL: https://issues.jboss.org/browse/AS7-3358 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.1.0.CR1 > Reporter: Pavel Slavicek > Assignee: Andy Taylor > Priority: Minor > Fix For: 7.1.0.Final > > > This issue is also in AS7. > Cloned from JBPAPP-6137: > Hi Clebert, > I hit NullPointerException when dedicated backup server was shutting down after clean shutdown command. Live server was stopped (clean shutdown too) several seconds before backup server. It seems that backup tried to take its role. NullPointerException is ugly and it should not occur. > I am putting it on minor priority. > Thank you. > 10:42:42,071 INFO [ClusterManagerImpl] announcing backup > 10:42:42,072 INFO [HornetQServerImpl] HornetQ Backup Server version 2.2.1.GA (Zmmmmmmmm, 121) [e9d8059a-5140-11e0-8830-005056c00008] started, waiting live to fail before it gets active > 10:42:49,387 INFO [ClusterManagerImpl] backup announced > ^C10:51:03,362 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true > 10:51:03,423 WARN [RemotingConnectionImpl] Connection failure has been detected: The connection was disconnected because of server shutdown [code=4] > 10:51:03,628 WARN [ClientSessionFactoryImpl] Failed to connect to server. > 10:51:03,634 SEVERE [HornetQServerImpl] Failure in initialisation > java.lang.NullPointerException > at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1436) > at org.hornetq.core.server.impl.HornetQServerImpl.access$100(HornetQServerImpl.java:130) > at org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreBackupActivation.run(HornetQServerImpl.java:398) > at java.lang.Thread.run(Thread.java:636) > 10:51:04,634 INFO [HornetQServerImpl] HornetQ Server version 2.2.1.GA (Zmmmmmmmm, 121) [e9d8059a-5140-11e0-8830-005056c00008] stopped -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBLOGGING-71) The JMX Bean associated with a LogContext must be made available

by Leonid Kosmylev (JIRA)

The JMX Bean associated with a LogContext must be made available ---------------------------------------------------------------- Key: JBLOGGING-71 URL: https://issues.jboss.org/browse/JBLOGGING-71 Project: JBoss Logging Issue Type: Enhancement Security Level: Public (Everyone can see) Environment: JBoss AS 6.0.0 Reporter: Leonid Kosmylev Assignee: David Lloyd Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If per-application logging is enabled a new instances of LogContext and LoggingMXBeanImpl are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not possible to change log levels dynamically. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
5
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 January 2012