[JBoss JIRA] (AS7-4701) One time password for management interfaces
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-4701:
-------------------------------------
Summary: One time password for management interfaces
Key: AS7-4701
URL: https://issues.jboss.org/browse/AS7-4701
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.2.0.Alpha1
This task is to look into one time password use for the management consoles.
This needs some further investigation as there is a trade off between ensuring a password is really one time and not valid for replays after use yet allowing a users web browser to keep establishing connections without forcing a new authentication every few minutes.
The native interface also needs similar consideration however the native interface does allow for connections to be kept open for a long time more naturally.
--
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
13 years, 2 months
[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
13 years, 2 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
13 years, 2 months