[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, 5 months
[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, 5 months
[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, 5 months
[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, 5 months