October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBNAME-38) Unit tests are not running in jnpserver

by Carlo de Wolf (JIRA)

Unit tests are not running in jnpserver --------------------------------------- Key: JBNAME-38 URL: https://jira.jboss.org/jira/browse/JBNAME-38 Project: JBoss Naming Issue Type: Task Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Blocker Fix For: 5.1.0.Beta1 -- 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

16 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-6926) Run JBoss on privileged port (80) without running as root

by Brad Maxwell (JIRA)

Run JBoss on privileged port (80) without running as root --------------------------------------------------------- Key: JBAS-6926 URL: https://jira.jboss.org/jira/browse/JBAS-6926 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: System service, Web (Tomcat) service Reporter: Brad Maxwell Assignee: Dimitris Andreadis Many customers want to run JBoss Web on port 80 without running JBoss as root for security reasons. This is usually achieved by fronting JBoss with Apache & using mod_jk to proxy to JBoss or doing NAT on the machine. It would be nice if JBoss could be started as root but have configuration that would change to a non-root user after it has opened the ports such as port 80 for jboss-web, such as Apache and other app servers do. Below are some possibilities to achieve this: Changing UID is something that would have to be done via JNI (in other words, platform-specific compiled libraries - possibly more than one per platform [I'm thinking of hybrid 32/64-bit platforms]). That said I could envision a couple possible solutions for UNIX platforms (all would require development work however): Solution 1 ---------- - JBAS starts up by running Main - Main notices a special configuration option to bind certain ports upfront, stores those bound sockets for later - Main notices a special configuration option to switch UID, uses the JNI stub to do so - Commence normal bootstrap - JBossWeb (or any other network component) has a provision to re-use pre-bound sockets - On redeploy or connector undeploy, those sockets had better not be closed or else they won't be able to be re-bound Solution 2 ---------- - A separate "binder" program is written (in C) which creates a AF_UNIX socket with restricted permissions and runs as root - JBAS starts up, runs through bootstrap normally as a non-priv user - Rather than creating a ServerSocket, JBAS uses a JNI stub to connect to the AF_UNIX socket, and send a request to bind a privileged socket address - The "binder" program binds the address and sends the file descriptor back over the AF_UNIX socket, and closes its local copy of the server socket - JBAS reads that server socket back off the AF_UNIX socket (note that this is arguably slightly more elegant as a custom ServerSocketFactory could do this transparently for non-NIO usages) Solution 3 (Linux only) ----------------------- - Run JBAS with CAP_NET_BIND_SERVICE Note that these solutions all rely on platform-specific mechanisms, because it's a platform-specific problem. The best we can do is come up with a way to distribute the JNI guts in such a way that it doesn't *look* like a platform-specific solution. - DML -- 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

16 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCOMMON-97) Generify WeakClassCache

by Ales Justin (JIRA)

Generify WeakClassCache ----------------------- Key: JBCOMMON-97 URL: https://jira.jboss.org/jira/browse/JBCOMMON-97 Project: JBoss Common Issue Type: Task Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.16.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.2.17.GA Use generics in WeakClassCache. -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBANN-41) Allow for more plugable way of creating AnnotationScanner

by Ales Justin (JIRA)

Allow for more plugable way of creating AnnotationScanner --------------------------------------------------------- Key: JBANN-41 URL: https://jira.jboss.org/jira/browse/JBANN-41 Project: Papaki Issue Type: Feature Request Components: Core Affects Versions: 1.0.0.Beta2 Reporter: Ales Justin Assignee: Ales Justin Fix For: 1.0.0.Beta3 There should be some AnnotationScannerCreator which is tied to enum ScanStrategy. e.g. AnnotationScannerCreator::create(Configuration) + ScanStrategy implements AnnotationScannerCreator. This allows for usage of pre-existing Configuration. -- 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

16 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2302) Extend JMX support for Flow

by Kris Verlaenen (JIRA)

Extend JMX support for Flow --------------------------- Key: JBRULES-2302 URL: https://jira.jboss.org/jira/browse/JBRULES-2302 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.1.0.M2 Extend the JMX support with methods for managing process instances. -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-123) Fix problems flagged by FINDBUGS

by Adrian Brock (JIRA)

Fix problems flagged by FINDBUGS -------------------------------- Key: JBCL-123 URL: https://jira.jboss.org/jira/browse/JBCL-123 Project: JBoss ClassLoader Issue Type: Task Components: General Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.7.GA, JBossCL.2.2.0.Alpha FIx problems located by FINDBUGS -- 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

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1930) Timeouts for RMI-Calls to EJBs

by Bernd Köcke (JIRA)

Timeouts for RMI-Calls to EJBs ------------------------------ Key: EJBTHREE-1930 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1930 Project: EJB 3.0 Issue Type: Feature Request Components: ejb3 Environment: Linux, SUN-Java5-20, JBoss 4.0.2, JBoss 4.2.3.GA Reporter: Bernd Köcke Attachments: tif-1.1.zip I would like to introduce client defined timeouts for RMI-Calls to EJBs. We have EJBs which are called from webfrontends and background processes. The Frontends have strong timing demands, e.g they only want to wait 50ms to get an answer but they accept to goon without it. This can be solved by application desing, but we have running applications which should not change. By looking into the code I found that it should be enough to set the SO-Timeout on the clients socket and the goal was to do this without changes in the clients code and the EJBs. So I build a small framework that the client only needs a jar- and a property-file to set timeouts for the RMI-Calls. I build this for EJB 2.1 on JBossAS 4.0.2 and EJB 2.1 + 3 for 4.2.3.GA. I talked to Carlo and he said that the latter could be interesting. It is installed on the server side by additonal JARs and configuration, no patches to existing JBoss code is needed. The attachment is a complete Maven Eclipse project with sources, classes and artifacts. The framework is called "Timed Invoker Framework" (TIF). I added JBoss deployment descriptor fragments to the ZIP and a readme PDF. The PDF is a copy of my internal Wiki page which describes usage and installation of TIF and the source contains JavaDoc. -- 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

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBANN-46) JBoss VFS should be used to hande resources lookup

by Ales Justin (JIRA)

JBoss VFS should be used to hande resources lookup -------------------------------------------------- Key: JBANN-46 URL: https://jira.jboss.org/jira/browse/JBANN-46 Project: Papaki Issue Type: Task Components: Core Affects Versions: 1.0.0.Beta2 Reporter: Ales Justin Assignee: Jesper Pedersen Much of the JBANN-43, JBANN-45 can easily and elegantly be solved by using VFS. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-45) Indexing should apply restriction rules

by Ales Justin (JIRA)

Indexing should apply restriction rules --------------------------------------- Key: JBANN-45 URL: https://jira.jboss.org/jira/browse/JBANN-45 Project: Papaki Issue Type: Task Components: Tool - Indexer Affects Versions: 1.0.0.Beta2 Reporter: Ales Justin Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 While indexing we should take into account restrictions enforced by metadata. e.g. OSGi manifest export headers, jboss-classloading.xml capabilities, ... -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-44) Annotations should not be ignored for scanning

by Ales Justin (JIRA)

Annotations should not be ignored for scanning ---------------------------------------------- Key: JBANN-44 URL: https://jira.jboss.org/jira/browse/JBANN-44 Project: Papaki Issue Type: Task Components: Core Affects Versions: 1.0.0.Beta2 Reporter: Ales Justin Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 Why are we ignoring annotations? if (isJava5 && !ctClass.isAnnotation()) { processClass(ctClass, ari, annotationToClasses, classInfo); } if (!clz.isAnnotation()) This won't work then for meta annotated annotations. e.g. Weld uses this a lot; decorator pattern -- 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

16 years, 9 months

1
0
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 October 2009