August 2012 - jboss-jira - Jboss List Archives

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

by Bernd Eckenfels (JIRA)

11 years, 4 months

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

11 years, 4 months

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

11 years, 4 months

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

11 years, 4 months

2
6
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

11 years, 4 months

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

11 years, 4 months

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

11 years, 4 months

2
3
0 / 0

[JBoss JIRA] (AS7-4400) Boolean validator

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-4400: ------------------------------------ Summary: Boolean validator Key: AS7-4400 URL: https://issues.jboss.org/browse/AS7-4400 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Jesper Pedersen Assignee: Brian Stansberry If you have a BOOLEAN in the DMR, but fail to type in the correct value, say "ture", it will get evaluated as false, while the user clearly meant true. We should have a strict validation against the "true" and "false" strings. -- 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

11 years, 4 months

2
2
0 / 0

[JBoss JIRA] (AS7-4271) Boot log writer ignores -Djboss.server.base.dir

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4271: ------------------------------- Summary: Boot log writer ignores -Djboss.server.base.dir Key: AS7-4271 URL: https://issues.jboss.org/browse/AS7-4271 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Heiko Rupp Assignee: Brian Stansberry When you start a server with -Djboss.server.base.dir this directory is used for configuration and also server.log, but not to populate the boot.log, which is still written to standalone/logs/boot.log. This is bad, as it will overwrite a boot.log for a server configuration that is running in parallel without -Djboss.server.base.dir= flag. Actually the logging config also seems to point at the old place hrupp 78046 0,0 1,1 1537296 96228 s005 S+ 10:55am 0:03.70 /usr/bin/java -D[Standalone] -d32 -client -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/devel/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/devel/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -jar /devel/jboss-as-7.1.1.Final/jboss-modules.jar -mp /devel/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/devel/jboss-as-7.1.1.Final -Djboss.server.base.dir=/devel/jboss-as-7.1.1.Final/standalone2 -- 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

11 years, 4 months

2
4
0 / 0

[JBoss JIRA] (AS7-2626) Trailing forgotten --> does not generate a good error message on host.xml

by Jim Tyrrell (Created) (JIRA)

Trailing forgotten --> does not generate a good error message on host.xml ------------------------------------------------------------------------- Key: AS7-2626 URL: https://issues.jboss.org/browse/AS7-2626 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Jim Tyrrell Assignee: Brian Stansberry This snippet from the host.xml file, note the --> that was forgotten to be removed in the remote line... <domain-controller>   </domain-controller> Generates this error message: [Host Controller] 21:24:51,341 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration Several lines further down...you get this message... [Host Controller] Caused by: com.ctc.wstx.exc.WstxParsingException: Received non-all-whitespace CHARACTERS or CDATA event in nextTag(). [Host Controller] at [row,col {unknown-source}]: [44,4] It would be nice if the first error message in an XML parsing error would just show me the place it failed, along with maybe the prior line. Less nice would be the 44,4 to be in the first message and break it down as line 44, character 4. More verbosity would be nice. -- 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

11 years, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012