January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8208) Expressing configuration property metadata in domain schema

by Brian Stansberry (JIRA)

Expressing configuration property metadata in domain schema ----------------------------------------------------------- Key: JBAS-8208 URL: https://jira.jboss.org/browse/JBAS-8208 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M1 Clients of the domain management API are going to need to see metadata about the various items they are configuring. Besides simple type stuff, information on things like whether changes require restart, etc, need to be available. This task is to determine where this information comes from and how it can be made available to the layer that provides it to the client. -- 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

14 years, 6 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-8137) Simple start and stop scripts

by Brian Stansberry (JIRA)

Simple start and stop scripts ----------------------------- Key: JBAS-8137 URL: https://jira.jboss.org/browse/JBAS-8137 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: >> I would like to see all the configurations that normally get set on the >> command line (JBoss opts and system props) moved to a config file so all >> that is ever required to start a Jboss instance is simply "run.sh >> /<configuration>/". The domain and host configuration files we'll introduce with AS 7 should encapsulate most things that are currently passed in via -D or the arguments to main(). If we start adding additional command line options that need to be processed before the domain/host configuration files are read, we should make it easy to set those in a configuration file (perhaps a simple properties file). -- 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

14 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-8744) Failure to start the JVM should trigger a management update plan to rollback

by Andrig Miller (JIRA)

Failure to start the JVM should trigger a management update plan to rollback ---------------------------------------------------------------------------- Key: JBAS-8744 URL: https://issues.jboss.org/browse/JBAS-8744 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Andrig Miller Assignee: Brian Stansberry Fix For: 7.0.0.Beta1 I have come across situations where certain JVM options, typically related to NUMA options, can cause the JVM to segfault. With our domain model, we expose the ability to set the JVM options, so I think this certainly would be a possibility. So, as we discussed on the Andiamo call today, this type of situation should cause a rollback of the management update plan, if the JVM fails to start. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8578) JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar

by Scott Marlow (JIRA)

JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar ------------------------------------------------------------------------- Key: JBAS-8578 URL: https://jira.jboss.org/browse/JBAS-8578 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMX Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 6.0.0.Final, 7.0.0.M2 For users that might of previously used jmx-remoting.sar. Add /jmxrmi alias for AS6+AS7. They could also later change their application for AS6/AS7 to use the "service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi" URL. This should be a one line change (I hope :-): registry.rebind("jmxrmi", rmiServer.toStub()); registry.rebind("jmxconnector", rmiServer.toStub()); -- 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

14 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-6332) Injection from outside modules

by Carlo de Wolf (JIRA)

Injection from outside modules ------------------------------ Key: JBAS-6332 URL: https://jira.jboss.org/jira/browse/JBAS-6332 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Carlo de Wolf When a servlet is packaged standalone (outside ear) and an EJB is packaged standalone, the EJB can't be injected into the servlet without specifying a JNDI name somewhere. It would be nice to have the ability to inject beans from outside your own enterprise application. -- 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

14 years, 6 months

7
9
0 / 0

[JBoss JIRA] Created: (SECURITY-467) Callbackhandlers to get information from various sources (DB/LDAP)

by Anil Saldhana (JIRA)

Callbackhandlers to get information from various sources (DB/LDAP) ------------------------------------------------------------------ Key: SECURITY-467 URL: https://jira.jboss.org/jira/browse/SECURITY-467 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta2 -- 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

14 years, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (JBAS-8202) Repository SPI

by Brian Stansberry (JIRA)

Repository SPI -------------- Key: JBAS-8202 URL: https://jira.jboss.org/browse/JBAS-8202 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M2 SPI to allow the DomainController (and Server???) to pull content from a location besides the local filesystem. This doesn't need to be finalized for M1, so scheduling for M2. -- 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

14 years, 6 months

3
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

14 years, 6 months

3
7
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

14 years, 6 months

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

14 years, 6 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011