July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-864) Support expressions in interface and socket related configs

by Brian Stansberry (JIRA)

Support expressions in interface and socket related configs ----------------------------------------------------------- Key: AS7-864 URL: https://issues.jboss.org/browse/AS7-864 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.CR1 Make it possible to fairly easily control socket bindings from the command line. So, we need expression support for: 1) Static interface criteria values (i.e. <inet-address value="${x}"/> and <loopback-address value="${x}"/> 2) The port-offset on a socket-binding-group 3) The multicast address and port on a socket-binding 4) *Perhaps* the default-interface on a socket-binding-group 5) *Perhaps* the interface on a socket-binding 6) The address and port in host.xml's <domain-controller><remote...> element 7) The port in the <management-interface> child elements 8) *Perhaps* the interface in the <management-interface> child elements -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-894) subsystem logging : boolean don't have a default or runtime value

by Heiko Rupp (JIRA)

subsystem logging : boolean don't have a default or runtime value ----------------------------------------------------------------- Key: AS7-894 URL: https://issues.jboss.org/browse/AS7-894 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Rupp [standalone@localhost:9999 subsystem=logging] ./periodic-rotating-file-handler=FILE:read-resource-description "append" => { "type" => BOOLEAN, "description" => "Specify whether to append to the target file.", "access-type" => "read-only", "storage" => "configuration" }, and [standalone@localhost:9999 subsystem=logging] ./periodic-rotating-file-handler=FILE:read-resource { "outcome" => "success", "result" => { "autoflush" => true, "encoding" => undefined, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "level" => "INFO", "file" => { "path" => "server.log", "relative-to" => "jboss.server.log.dir" }, "suffix" => ".yyyy-MM-dd" }, Probably the same for other kinds of appenders. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-7656) jboss_init_redhat.sh needs to be more robust

by Henrik Aronsen (JIRA)

jboss_init_redhat.sh needs to be more robust -------------------------------------------- Key: JBAS-7656 URL: https://jira.jboss.org/jira/browse/JBAS-7656 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Other Reporter: Henrik Aronsen Fix For: JBossAS-6.0.0.M2, JBossAS-6.0.0.M3, JBossAS-6.0.0.CR1, JBossAS-6.0.0.GA I have tried to address the shortcomings of the current JBoss init script for RHEL5: - Uses PID file - Supports chkconfig - Supports start, stop, force-stop, reload, force-reload, status - Supports custom user and password on shutdown - Supports custom jndi host/port on shutdown - Does not allow second instance to start when one is already running - Does not rely on other files such as run.sh and run.conf - Verifies successful startup - The init script does not have to be edited, use the standard location for configuration (/etc/default/jboss) instead - Runs out of the box when no configuration is provided - Should support most Linuces All feedback is welcome -- I'm sure I forgot something in the provided script The init script is currently maintained at http://code.google.com/p/jboss-rpm/source/browse/#svn/trunk/src/main/etc (This issue was copied from JBPAPP-3194 as suggested by Fernando Nasser) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-9102) Wildcard operations that span multiple processes

by Brian Stansberry (JIRA)

Wildcard operations that span multiple processes ------------------------------------------------ Key: JBAS-9102 URL: https://issues.jboss.org/browse/JBAS-9102 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.Beta2 Handle host=* and host=y,server=* type operations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (AS7-1366) HostController only pushes ops to servers whose config has auto-start=true

by Brian Stansberry (JIRA)

HostController only pushes ops to servers whose config has auto-start=true -------------------------------------------------------------------------- Key: AS7-1366 URL: https://issues.jboss.org/browse/AS7-1366 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.0.1.Final The auto-start attribute on a server-config controls whether the HC should start it at boot, not whether it is currently started. So it shouldn't be used as the driver for whether a server needs to have a change applied to its runtime. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-861) resource-description for root-logger in subsystem=looging is incomplete

by Heiko Rupp (JIRA)

resource-description for root-logger in subsystem=looging is incomplete ----------------------------------------------------------------------- Key: AS7-861 URL: https://issues.jboss.org/browse/AS7-861 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Rupp Assignee: Jason Greene [domain@localhost:9999 subsystem=logging] :read-resource-description(recursive=true) { "outcome" => "success", "result" => { "description" => "The configuration of the logging subsystem.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:logging:1.0", "operations" => undefined, "children" => { "root-logger" => {"description" => "Defines the root logger for this log context."}, and [domain@localhost:9999 subsystem=logging] :read-resource(recursive=true) { "outcome" => "success", "result" => { "root-logger" => { "level" => "INFO", "handlers" => [ "CONSOLE", "FILE" ] } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

6
7
0 / 0

[JBoss JIRA] Created: (AS7-1004) "failed to resolve interface default" if default interface inet-address value set to a local address other than 127.0.0.1

by Marek Schmidt (JIRA)

"failed to resolve interface default" if default interface inet-address value set to a local address other than 127.0.0.1 ------------------------------------------------------------------------------------------------------------------------- Key: AS7-1004 URL: https://issues.jboss.org/browse/AS7-1004 Project: Application Server 7 Issue Type: Bug Environment: Fedora 15, Sun JDK 1.6.0_24-b07, jboss-7.0.0.Beta4-SNAPSHOT-1194, standalone Reporter: Marek Schmidt Setting the "default" interface to, e.g.: {code} <interface name="default"> <inet-address value="127.0.1.1"/> </interface> {code} throws the following exception at startup, even if the 127.0.1.1 address is set up in /etc/hosts (not that it should matter) I have noticed there exists a loopback-address element which seems to work, but I fail to see why this one shouldn't. {quote} 12:06:18,660 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.default: org.jboss.msc.service.StartException in service jboss.network.default: failed to resolve interface default at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:106) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-8132) Utility to report on differences in domain configuration between domains

by Brian Stansberry (JIRA)

Utility to report on differences in domain configuration between domains ------------------------------------------------------------------------ Key: JBAS-8132 URL: https://jira.jboss.org/browse/JBAS-8132 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: One of the motivations for the domain controller was to help customers manage drift in their JBoss configurations. Because of operational concerns, specifically datacenter isolation, some customers expect to need to run multiple identical domain controllers. They would then still be faced with drift across domain controllers. A utility to detect this drift would be helpful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-851) Add some form of :whoami operation

by Darran Lofthouse (JIRA)

Add some form of :whoami operation ---------------------------------- Key: AS7-851 URL: https://issues.jboss.org/browse/AS7-851 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Jason Greene Fix For: 7.0.0.CR1 Connectivity to the server can make use of authentication automatically handled by either the web broswer or in some cases possibly a CLI using a local Kerberos ticket. This issue is to add a :whoami operation to verify who the connection is running as so the client can see they are connected as the expected user. Later this may also be expanded to make it possible to query what a client can actually do so operations a client can not perform can be potentially hidden / masked. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBEE-45) Release JACC 1.1 APIs built with JDK 1.4

by Shelly McGowan (JIRA)

Release JACC 1.1 APIs built with JDK 1.4 ---------------------------------------- Key: JBEE-45 URL: https://jira.jboss.org/jira/browse/JBEE-45 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.0.CR1 To replace this: http://repository.jboss.org/maven2/org/jboss/javaee/jboss-jacc-api_JDK4/1... which contains a servlet snapshot Needed by Hibernate -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011