June 2012 - jboss-jira - Jboss List Archives

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

by Bernd Eckenfels (JIRA)

12 years, 2 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

12 years, 2 months

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

12 years, 2 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

12 years, 2 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

12 years, 2 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

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1103) Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase

by James Perkins (JIRA)

Intermittent failures in org.jboss.as.controller.CompositeOperationHandlerUnitTestCase -------------------------------------------------------------------------------------- Key: AS7-1103 URL: https://issues.jboss.org/browse/AS7-1103 Project: Application Server 7 Issue Type: Bug Reporter: James Perkins Assignee: Brian Stansberry Fix For: 7.0.0.CR1 Below is the message from the error. ------------------------------------------------------------------------------- Test set: org.jboss.as.controller.CompositeOperationHandlerUnitTestCase ------------------------------------------------------------------------------- Tests run: 24, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.625 sec <<< FAILURE! testRestartRequired(org.jboss.as.controller.CompositeOperationHandlerUnitTestCase) Time elapsed: 0.031 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[restart-requir]ed> but was:<[undefin]ed> at org.junit.Assert.assertEquals(Assert.java:123) at org.junit.Assert.assertEquals(Assert.java:145) at org.jboss.as.controller.CompositeOperationHandlerUnitTestCase.testRestartRequired(CompositeOperationHandlerUnitTestCase.java:496) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

7
12
0 / 0

[JBoss JIRA] (AS7-2625) No Spaces Allowed in Host -> Name, but ' do work, odd

by Jim Tyrrell (Created) (JIRA)

No Spaces Allowed in Host -> Name, but ' do work, odd ----------------------------------------------------- Key: AS7-2625 URL: https://issues.jboss.org/browse/AS7-2625 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Jim Tyrrell Assignee: Brian Stansberry For some reason spaces do not seem to be allowed, but an Apostrophe seems to be okay. [Host Controller] 20:56:20,250 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014601: Error booting the container: java.lang.IllegalArgumentException: JBAS014719: Invalid value specification Jim's Most_Excellent_Domain_Ever_so_here Would be nice if the error message would kick out what values are acceptable? -- 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, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-762) Provide an operation to request service status report after server has been started

by Heiko Braun (JIRA)

Provide an operation to request service status report after server has been started ------------------------------------------------------------------------------------- Key: AS7-762 URL: https://issues.jboss.org/browse/AS7-762 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry For proper healthcare it would beneficial if I could verify the server status after is has been started. I.e. to catch these, which currently only appear in the server log: [Server:server-three] 17:48:26,636 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report [Server:server-three] New missing/unsatisfied dependencies: [Server:server-three] service jboss.binding.http2 (missing) [Server:server-three] [Server:server-three] 17:48:26,636 ERROR [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 3893ms - Started 101 of 149 services (1 services failed or missing dependencies, 47 services are passive or on-demand) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2012