October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2357) OperationStepHandlers do not properly check if runtime steps should be added

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2357?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2357: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1021633|https://bugzilla.redhat.com/show_bug.cgi?id=1021633] from MODIFIED to ON_QA > OperationStepHandlers do not properly check if runtime steps should be added > ---------------------------------------------------------------------------- > > Key: WFLY-2357 > URL: https://issues.jboss.org/browse/WFLY-2357 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 8.0.0.CR1 > > > Currently only checks if the process type is a server which would add runtime steps if booted in admin only mode. This should use the {{OperationContext.isNormalServer()}} instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-369) Domain mode: kill an unresponsive JVM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-369?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-369: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 901232|https://bugzilla.redhat.com/show_bug.cgi?id=901232] from MODIFIED to ON_QA > Domain mode: kill an unresponsive JVM > ------------------------------------- > > Key: WFLY-369 > URL: https://issues.jboss.org/browse/WFLY-369 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Dennis Reed > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > If an AS instance gets into a state where it cannot be controlled normally by the host controller, local OS commands must be used to kill it. > It would be helpful to be able to kill an unresponsive JVM through the management interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-158) Constant fields that are not final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-158?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-158: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 926050|https://bugzilla.redhat.com/show_bug.cgi?id=926050] from MODIFIED to ON_QA > Constant fields that are not final > ---------------------------------- > > Key: WFLY-158 > URL: https://issues.jboss.org/browse/WFLY-158 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > Attachments: non-final-fields.txt > > > Analysis by Stephan Mueller shows that the AS codebase includes a significant number of public constant fields that are missing the "final" keyword, which could allow incorrect or nefarious code to change them. This task is to fix these. > As part of the work for a few cases I'll reduce the field visibility. > I'll attach file listing the cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2371) SizeRotatingHandlerTestCase.rotationTest fails with "the file is bigger than allowed size"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2371?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2371: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1020339|https://bugzilla.redhat.com/show_bug.cgi?id=1020339] from MODIFIED to ON_QA > SizeRotatingHandlerTestCase.rotationTest fails with "the file is bigger than allowed size" > ------------------------------------------------------------------------------------------ > > Key: WFLY-2371 > URL: https://issues.jboss.org/browse/WFLY-2371 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Petr Kremensky > Assignee: Petr Kremensky > > The test org.jboss.as.test.integration.logging.operations.SizeRotatingHandlerTestCase.rotationTest consistently fails with: > java.lang.AssertionError: This file is bigger than allowed rotate-size: size-rotating-reload-rotationTest.log.1 > Link to job: > https://jenkins.mw.lab.eng.bos.redhat.com/job/eap-6x-manu-acceptance-as-t... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2336) Decreasing max-threads on a unbounded queueless executor generates IllegalArgumentException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2336?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2336: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1021077|https://bugzilla.redhat.com/show_bug.cgi?id=1021077] from MODIFIED to ON_QA > Decreasing max-threads on a unbounded queueless executor generates IllegalArgumentException > ------------------------------------------------------------------------------------------- > > Key: WFLY-2336 > URL: https://issues.jboss.org/browse/WFLY-2336 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Beta1 > Reporter: Aaron Ogburn > Priority: Minor > Fix For: 8.0.0.CR1 > > > Create an unbounded queueless executor > <unbounded-queue-thread-pool name="uq-thread-pool"> > <max-threads count="350"/> > <keepalive-time time="5" unit="minutes"/> > </unbounded-queue-thread-pool> > Modifying max-threads fails: > /subsystem=threads/unbounded-queue-thread-pool=uq-thread-pool:write-attribute(name=max-threads,value=300) > { > "outcome" => "failed", > "failure-description" => "JBAS014749: Operation handler failed: null", > "rolled-back" => true > } > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("write-attribute") failed - address: ([ > ("subsystem" => "threads"), > ("unbounded-queue-thread-pool" => "uq-thread-pool") > ]): java.lang.IllegalArgumentException > at java.util.concurrent.ThreadPoolExecutor.setMaximumPoolSize(ThreadPoolExecutor.java:1620) [rt.jar:1.7.0] > at org.jboss.threads.JBossThreadPoolExecutor.setMaxThreads(JBossThreadPoolExecutor.java:95) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > at org.jboss.as.threads.ManagedJBossThreadPoolExecutorService.setMaxThreads(ManagedJBossThreadPoolExecutorService.java:86) > at org.jboss.as.threads.UnboundedQueueThreadPoolService.setMaxThreads(UnboundedQueueThreadPoolService.java:91) > The core pool size needs to be adjusted in line with the max pool size and in the right order to avoid that since max threads can't be less than core threads. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2206) Manualmode test suite copes the modules directory multiple times

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2206?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2206: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1014742|https://bugzilla.redhat.com/show_bug.cgi?id=1014742] from MODIFIED to ON_QA > Manualmode test suite copes the modules directory multiple times > ---------------------------------------------------------------- > > Key: WFLY-2206 > URL: https://issues.jboss.org/browse/WFLY-2206 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Beta1 > > > This uses lots of disk space for no good reason -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2320) EJB should not be remotely accessible until all of its dependencies have been started

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2320?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2320: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1019894|https://bugzilla.redhat.com/show_bug.cgi?id=1019894] from MODIFIED to ON_QA > EJB should not be remotely accessible until all of its dependencies have been started > ------------------------------------------------------------------------------------- > > Key: WFLY-2320 > URL: https://issues.jboss.org/browse/WFLY-2320 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Beta1 > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > > If an EJB injects or depends on a resource such as an @Singleton which has not been started, the EJB's remote interface java:jboss/exported/* is already bound and this allows remote EJB clients to try to invoke it. This causes the EJB clients to hang because the EJB will not be started until its dependencies have been started. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2418) Incorrect PIDFILE location (typo in wildfly name)

by John Smith (JIRA)

John Smith created WFLY-2418: -------------------------------- Summary: Incorrect PIDFILE location (typo in wildfly name) Key: WFLY-2418 URL: https://issues.jboss.org/browse/WFLY-2418 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Scripts Affects Versions: 8.0.0.Beta1 Environment: redhat Reporter: John Smith Assignee: Brian Stansberry Typo in: https://github.com/wildfly/wildfly/blob/master/build/src/main/resources/b... wildfly directory name is spelt incorrectly is wilfly. Line: JBOSS_PIDFILE=/var/run/wilfly/wildfly.pid Should be: JBOSS_PIDFILE=/var/run/wildfly/wildfly.pid -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1948) JMXPropertyEditorsTestCase fails on Solaris SPARC

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-1948?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-1948: --------------------------------------- Same cause. Environment variable USER is mandatory currently on non windows systems. > JMXPropertyEditorsTestCase fails on Solaris SPARC > ------------------------------------------------- > > Key: WFLY-1948 > URL: https://issues.jboss.org/browse/WFLY-1948 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10 6/06, Oracle JDK 1.7.0_25 > Reporter: Frank Langelage > Assignee: Ondrej Zizka > > Test org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase fails on Solaris, because environment variable USER is not set. > From the source: > USER_SYS_PROP = System.getProperty("os.name","linux").contains("indows")?"USERNAME":"USER"; > So there is already a differentiation between Windows and others. > For Solaris LOGNAME is the variable to use. And os.name is SunOS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2398) org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase fails

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2398?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2398: --------------------------------------- I was running smoke test with "-DnoWebProfile". If I omit this option, problem disappears. So test seems to be not compatible with full profile. > org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase fails > ------------------------------------------------------------------------ > > Key: WFLY-2398 > URL: https://issues.jboss.org/browse/WFLY-2398 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA, Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10, Oracle Java 1.7.0_45 > Reporter: Frank Langelage > Assignee: Stefano Maestri > Attachments: org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase-output.txt, org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase.txt > > > Running a build of current sources with complete testsuite this test is failing with > testRegistryConfiguration(org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase): expected:<1> but was:<2> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013