April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-45) Assimilate the Higgins Project SPI

by Anil Saldhana (JIRA)

Assimilate the Higgins Project SPI ---------------------------------- Key: SECURITY-45 URL: http://jira.jboss.com/jira/browse/SECURITY-45 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Security SPI Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 There is a need to get the SPI for Project Higgins Trust Framework into the JBoss Security SPI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
5
0 / 0

[JBoss JIRA] Created: (SECURITY-470) Callbackhandlers to get information from LDAP

by Anil Saldhana (JIRA)

Callbackhandlers to get information from LDAP --------------------------------------------- Key: SECURITY-470 URL: https://jira.jboss.org/jira/browse/SECURITY-470 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_beta4 -- 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
3
0 / 0

[JBoss JIRA] Created: (JGRP-790) FD_SOCK / shared transport: make FD_SOCK a singleton

by Bela Ban (JIRA)

FD_SOCK / shared transport: make FD_SOCK a singleton ---------------------------------------------------- Key: JGRP-790 URL: http://jira.jboss.com/jira/browse/JGRP-790 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 If we have multiple channels over the same shared transport, FD_SOCK creates multiple server sockets within the same JVM. Investigate whether we can collapse those into one server socket if we run over the same shared transport. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8787) Native libraries not found when using IBM JDK

by Mike Millson (JIRA)

Native libraries not found when using IBM JDK --------------------------------------------- Key: JBAS-8787 URL: https://issues.jboss.org/browse/JBAS-8787 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 6.0.0.Final Reporter: Mike Millson Assignee: Remy Maucherat The native components are not found on x86_64 using the IBM JDK because the startup script is looking in "lib" instead of "lib64". You get this error: 2011-01-04 16:39:37,205 INFO [org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/mmillson/jboss/eap-5.1.0/jboss-as/native/lib run.sh and run.bat set the native directory based on whether the reported version includes the string "64-bit": IS_64_BIT_JVM=`"$JAVA" $JAVA_OPTS -version 2>&1 | $GREP -i 64-bit` if [ "x$IS_64_BIT_JVM" != "x" ]; then JBOSS_NATIVE_DIR="$JBOSS_NATIVE_DIR/lib64" else JBOSS_NATIVE_DIR="$JBOSS_NATIVE_DIR/lib" fi But with the IBM JDK "java -version" does not report that string: Java(TM) SE Runtime Environment (build pxa6460sr8fp1-20100624_01(SR8 FP1)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr8ifx-20100609_59383 (JIT enabled, AOT enabled) J9VM - 20100609_059383 JIT - r9_20100401_15339ifx2 GC - 20100308_AA) JCL - 20100624_01 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

9
10
0 / 0

[JBoss JIRA] Created: (JBAS-9139) Eliminate dependency of domain-controller module on server module

by Brian Stansberry (JIRA)

Eliminate dependency of domain-controller module on server module ----------------------------------------------------------------- Key: JBAS-9139 URL: https://issues.jboss.org/browse/JBAS-9139 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta3 Get these separated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-8423) Ensure that connectors that handle end user request start late in the server start process

by Brian Stansberry (JIRA)

Ensure that connectors that handle end user request start late in the server start process ------------------------------------------------------------------------------------------ Key: JBAS-8423 URL: https://jira.jboss.org/browse/JBAS-8423 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M1 Ensure all connectors that handle user requests have appropriate behavior with respect to not starting until the overall server start is in a state where the connector can handle the expected requests. Part of this is understanding how the clients work; i.e. for some connectors clients may never send a request that the server can't correctly handle. For others, e.g. web connectors fronted by mod_jk or most hardware load balancers, once the connector is started, it may start receiving requests for apps that are not deployed. This is somewhat related to graceful shutdown, where the connector should stop handling requests at the appropriate point in a shutdown process. -- 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

6
7
0 / 0

[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

13 years

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments

by David Lloyd (JIRA)

Detect, filter, and act upon system APIs found in deployments ------------------------------------------------------------- Key: JBAS-8983 URL: https://issues.jboss.org/browse/JBAS-8983 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 Implement a fixed set of package paths which are automatically filtered out of deployments. In addition, certain paths should be interpreted as an implicit dependency request. For example if "org/slf4j" is found in a deployment, it should be filtered, and an implicit import dependency upon the org.slf4j module (which provides the org.slf4j package) should be added to the deployment. Use sub-tasks for each API to filter or detect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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

13 years

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-9176) List servers in a servergroup below /server-group/<groupname>

by Heiko Rupp (JIRA)

List servers in a servergroup below /server-group/<groupname> ------------------------------------------------------------- Key: JBAS-9176 URL: https://issues.jboss.org/browse/JBAS-9176 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp It would be nice from a consistency standpoint to list the servers of a servergroup in its api below /server-group/groupname/ - just the names would be enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011