November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3568) Increase Test Coverage of Domain Management Security Options

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3568: ------------------------------------- Summary: Increase Test Coverage of Domain Management Security Options Key: AS7-3568 URL: https://issues.jboss.org/browse/AS7-3568 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.1.Final Presently there is plenty of testing relating to the default security options but now we need coverage of the non default options especially SSL. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-5573) Track "uncleanly unregistered" hosts on the master HC; expose via management API

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5573: ------------------------------------- Summary: Track "uncleanly unregistered" hosts on the master HC; expose via management API Key: AS7-5573 URL: https://issues.jboss.org/browse/AS7-5573 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.CR1 When the master HC detects that a slave HC is no longer available but hasn't properly unregistered, the slave should still be visible in the management API but with some sort of status indicator. The slave should probably not remaining in the regular management tree, since that will encourage clients to invoke operations that will just fail, but it's existence and "unknown" status should be reflected in some manner accessible to management clients who wish to obtain a more complete view of the domain topology. -- 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

12 years, 1 month

1
2
0 / 0

[JBoss JIRA] (AS7-5008) host-controller module does parse command line args too late

by Bernd Eckenfels (JIRA)

12 years, 1 month

2
8
0 / 0

[JBoss JIRA] (AS7-4514) Metrics/operations missing in platform mbean core-service

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4514: ------------------------------- Summary: Metrics/operations missing in platform mbean core-service Key: AS7-4514 URL: https://issues.jboss.org/browse/AS7-4514 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Heiko Rupp Assignee: Brian Stansberry The platform mbean(s) exposes more metrics that what is currently available at core-service=platform-mbean -Active Thread Count -Active Thread Group Count - JVM Free memory - JVM Total memory OS metrics - Free Physical Memory - Free Swap Memory - Process CPU Time - Committed Virtual Memory - open files Threading - SuspendedThreadCount - DeadLockedThreadCount Memory - operation to trigger gc And probably more -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] (AS7-5445) deploy --name=(name with no extension) failed sometimes

by Cheng Fang (JIRA)

Cheng Fang created AS7-5445: ------------------------------- Summary: deploy --name=(name with no extension) failed sometimes Key: AS7-5445 URL: https://issues.jboss.org/browse/AS7-5445 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Cheng Fang Assignee: Brian Stansberry When deploying an app with --name option to specify a custom name, does the custom name have to include file extension to indicate its archive type? For example, is --name="nnn" valid, or does it have to be --name="nnn.war"? It seem requiring an archive type on a name is too restrictive. This is what I've observed: deploy --name="nnn" /tmp/hello.war deployed successfully, but there is no registration of web app context, so no way to run the webapp. Looks like the server haven't detected that it is a webapp from the name "nnn", and instead deployed it as a pojo module. With --name="nnn.war", everything works fine. deploy --name="nnn" /tmp/test-ejb.jar deployed successfully, and all the ejb's are registered. deploy --name="nnn" /tmp/test.ear deployed successfully, but ejb's inside the test.ear are not registered. deploy --name="nnn" /tmp/ejb-in-war.war failed, which could be the same cause as in the pure webapp deploy: {noformat} 21:47:14,391 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.deployment.unit.nnn.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.nnn.POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "nnn" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.lang.ClassNotFoundException: test.TestBean from [Module "deployment.nnn:main" from Service Module Loader] at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getEjbClass(BusinessViewAnnotationProcessor.java:216) at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:86) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 5 more Caused by: java.lang.ClassNotFoundException: test.TestBean from [Module "deployment.nnn:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.3.GA] at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getEjbClass(BusinessViewAnnotationProcessor.java:214) ... 7 more {noformat} -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] (AS7-5444) runtime-name is used when logging undeploy

by Cheng Fang (JIRA)

Cheng Fang created AS7-5444: ------------------------------- Summary: runtime-name is used when logging undeploy Key: AS7-5444 URL: https://issues.jboss.org/browse/AS7-5444 Project: Application Server 7 Issue Type: Bug Components: ConfigAdmin Affects Versions: 7.2.0.Alpha1 Reporter: Cheng Fang Assignee: David Bosschaert deploy a war and specify its runtime-name, and undeploy it: {noformat} deploy --runtime-name=nnn.war /Users/cfang/tmp/hello.war undeploy hello.war {noformat} In the server log it used the runtime-name to refer to the undeployed war, whereas I think the name (hello.war) should be used: {noformat} 17:31:08,290 INFO [org.jboss.as.server] (management-handler-thread - 55) JBAS018558: Undeployed "nnn.war" {noformat} -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] (AS7-5503) Move DC operation stream cleaning from OperationCoordinatorStepHandler and into the OSHs that actual process the input streams

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5503: ------------------------------------- Summary: Move DC operation stream cleaning from OperationCoordinatorStepHandler and into the OSHs that actual process the input streams Key: AS7-5503 URL: https://issues.jboss.org/browse/AS7-5503 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.CR1 Get rid of hackaliciousness at [1] and replace using OperationAttachments the way Stuart did for deployment overlays. [1] https://github.com/jbossas/jboss-as/blob/master/host-controller/src/main/... -- 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

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-5338) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5338: ------------------------------------- Summary: Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users Key: AS7-5338 URL: https://issues.jboss.org/browse/AS7-5338 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.CR1 Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] (AS7-4977) Api returns internal server error instead of not found for non-exiting path

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4977: ------------------------------- Summary: Api returns internal server error instead of not found for non-exiting path Key: AS7-4977 URL: https://issues.jboss.org/browse/AS7-4977 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Heiko Rupp Assignee: Brian Stansberry When I try to e.g. /subsystem=foo:read-resource the api returns a 500 internal server error. In http-land, the return code for "not found" is normally 404. -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] (AS7-4412) Slave host does not register to DC when starting with --cached-dc and DC is available

by Manel Martinez (JIRA)

Manel Martinez created AS7-4412: ----------------------------------- Summary: Slave host does not register to DC when starting with --cached-dc and DC is available Key: AS7-4412 URL: https://issues.jboss.org/browse/AS7-4412 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Manel Martinez Assignee: Brian Stansberry Priority: Critical NOTE: this is related to AS7-4281 (see https://issues.jboss.org/browse/AS7-4281?focusedCommentId=12682058&page=c... ) When a slave host is started with --cached-dc option it won't register to Domain Controller although it's available. domain.sh help says "If this host is not the Domain Controller and cannot contact the Domain Controller at boot, boot using a locally cached copy of the domain configuration (see --backup)" and this is not really happening because slave host never contact to DC with --cached-dc -- 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, 1 month

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012