January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7999) Investigate making HASingleton failover "stopOldMaster" RPC synchronous

by Brian Stansberry (JIRA)

Investigate making HASingleton failover "stopOldMaster" RPC synchronous ----------------------------------------------------------------------- Key: JBAS-7999 URL: https://jira.jboss.org/jira/browse/JBAS-7999 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry When a node becomes master, it tells any previous master to stop. That call is async, probably because long ago this was done on a JGroups up thread and making a sync call from that up thread would hang. This is no longer done on an up thread, so investigate adding a config option to allow is call to go synchronous, thus ensuring the old master is fully stopped before new one starts. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBAS-7221) Support recovery scenarios

by Jesper Pedersen (JIRA)

Support recovery scenarios -------------------------- Key: JBAS-7221 URL: https://jira.jboss.org/jira/browse/JBAS-7221 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Jesper Pedersen Assignee: Emanuel Muckenhuber Priority: Blocker Fix For: JBossAS-6.0.0.Alpha1 This is a container task for adding recovery support into the AS build. -- 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
12
0 / 0

[JBoss JIRA] Created: (SECURITY-132) Traditional Authentication

by Darran Lofthouse (JIRA)

Traditional Authentication -------------------------- Key: SECURITY-132 URL: http://jira.jboss.com/jira/browse/SECURITY-132 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Incomming call may be traditional username / password type call but consideration needs to be given for potential outbound call. -- 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

14 years, 6 months

3
11
0 / 0

[JBoss JIRA] Created: (SECURITY-141) Fallback to different authenticator if authentication fails

by Darran Lofthouse (JIRA)

Fallback to different authenticator if authentication fails ----------------------------------------------------------- Key: SECURITY-141 URL: http://jira.jboss.com/jira/browse/SECURITY-141 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Need to consider how this will work especially regarding security domains, possible to do something active directory - password-stacking and an LDAP login module that for negotiation does just role mapping and for non negotiation also does authentication. -- 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

14 years, 6 months

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-8320) Logging initialization

by Alexey Loubyansky (JIRA)

Logging initialization ---------------------- Key: JBAS-8320 URL: https://jira.jboss.org/browse/JBAS-8320 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Modules Reporter: Alexey Loubyansky Assignee: David Lloyd Fix For: 7.0.0.M1 The following exception is thrown during the start-up on windows (Sun JDK). The system property is in fact set as the error message suggests and I can successfully invoke java.util.logging.Logger logger = java.util.logging.Logger.getLogger("mylogger"); System.out.println(logger.getClass().getName() + " " + logger.getClass().getClassLoader().getClass().getName() + " " + logger.getClass().getClassLoader()); from ManagedProcess just before this.log = Logger.getLogger("org.jboss.process." + processName); (which causes the error) and output will be org.jboss.logmanager.Logger org.jboss.modules.ModuleClassLoader ClassLoader for Module "module:org.jboss.logmanager:jboss-logmanager" Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:60) at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:55) at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:46) at org.jboss.logging.Logger.getLogger(Logger.java:2222) at org.jboss.as.process.ManagedProcess.<init>(ManagedProcess.java:66) at org.jboss.as.process.ProcessManagerMaster.addProcess(ProcessManagerMaster.java:64) at org.jboss.as.process.ProcessManagerMaster.main(ProcessManagerMaster.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:105) at org.jboss.modules.Main.main(Main.java:169) -- 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
13
0 / 0

[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

14 years, 6 months

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

14 years, 6 months

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

14 years, 6 months

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

14 years, 6 months

9
10
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

14 years, 6 months

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