August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-917) Provide the ability to :reload() through the console

by Heiko Braun (JIRA)

Provide the ability to :reload() through the console ---------------------------------------------------- Key: AS7-917 URL: https://issues.jboss.org/browse/AS7-917 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7468) Memory leak in org.jboss.security.plugins.authorization.JBossAuthorizationContext

by Ganesh Ingle (JIRA)

Memory leak in org.jboss.security.plugins.authorization.JBossAuthorizationContext --------------------------------------------------------------------------------- Key: JBAS-7468 URL: https://jira.jboss.org/jira/browse/JBAS-7468 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA Environment: JBoss Version: jboss-5.1.0.GA, OS: Linux (2.6.18-164.el5), Architecture: amd64 64bit, JVM: Java HotSpot(TM) 64-Bit Server VM (14.0-b16, mixed mode) Reporter: Ganesh Ingle Assignee: Anil Saldhana Our use case (only security related portion is mentioned here): Axis 1.4 webservice, standard J2EE declarative security through WEB-INF/web.xml, a http client sends soap request and BASIC auth information, the JBoss server performs authentication and authorization as per WEB-INF/web.xml configuration. We did a performance/stability test on above web service. After 8.5 million requests the server gone out of memory. We did heap dump analysis using VisualVM tool and found that the class org.jboss.security.plugins.authorization.JBossAuthorizationContext is consuming most of the memory. This class has a memer array named "controlFlags", this array was showing 25.7 million ControlFlag entries. When we investigated the code we found that there is one instance of JBossAuthorizationManager per security domain and this manager has one instance of JBossAuthorizationContext. For every authorization the JBossAuthorizationContext initializes authorization modules and pushes their control flags (instances of class ControlFlag) in member arrays. When the authorization is complete, a commit/abort is invoked on all modules and finally the "modules" array is cleared. However, the "controlFlags" array is not cleared. We checked the entire class, this array never gets cleared. We changed the code to clear both "modules" and "controlFlags" array in a finally block in method JBossAuthorizationContext.authorize(final Resource resource, final Subject subject, final RoleGroup callerRoles). We ran a 50million test after this fix, the test was successful which proves the fix worked. -- 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, 8 months

7
13
0 / 0

[JBoss JIRA] Created: (AS7-1631) JAX-RS client support for OSGi bundles

by Thomas Diesler (JIRA)

JAX-RS client support for OSGi bundles -------------------------------------- Key: AS7-1631 URL: https://issues.jboss.org/browse/AS7-1631 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Provide OSGi bundles the ability to use the RESTeasy client APIs -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1263) Publish deployment descriptor schemas and dtd in the dist

by Brian Stansberry (JIRA)

Publish deployment descriptor schemas and dtd in the dist --------------------------------------------------------- Key: AS7-1263 URL: https://issues.jboss.org/browse/AS7-1263 Project: Application Server 7 Issue Type: Task Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.0.1.Final AS 7.0 has the domain/host/standalone config schemas in docs/schema, but not the deployment descriptor schemas and DTDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

7
14
0 / 0

[JBoss JIRA] Created: (LOGTOOL-22) Add additional support for message validation.

by James Perkins (JIRA)

Add additional support for message validation. ---------------------------------------------- Key: LOGTOOL-22 URL: https://issues.jboss.org/browse/LOGTOOL-22 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: David Lloyd Fix For: 1.0.0.Beta8 Add validation to see if the method parameters match the parameters required for the message. For example, an integer should be passed to String.format("%d"). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-9362) Long running thread leaks SimpleRole objects

by Tim Terlegard (JIRA)

Long running thread leaks SimpleRole objects -------------------------------------------- Key: JBAS-9362 URL: https://issues.jboss.org/browse/JBAS-9362 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 6.0.0.Final Environment: Tested on Mac OS X 10.6.7 with Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode) 1.6.0_24 Reporter: Tim Terlegard Assignee: Anil Saldhana Attachments: simpleroletest.tar.gz When invoking a long-running EJB method which makes a bunch of calls to some method in another EJB, then JBoss leaks SimpleRole objects. The SimpleRole objects are not removed by a manually triggered garbage collection. The SimpleRole object leakage seems to go away if I remove the security domain in jboss.xml. When running my jboss application during the night JBoss had 4GB of SimpleRole objects. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

6
9
0 / 0

[JBoss JIRA] Created: (JGRP-872) TP: cluster name is shipped with each message

by Bela Ban (JIRA)

TP: cluster name is shipped with each message --------------------------------------------- Key: JGRP-872 URL: https://jira.jboss.org/jira/browse/JGRP-872 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 If a cluster name (the name used in Channel.conect()) is long, because we ship it with each message (in the TP header), this blows up the size of the marshalled messages. Maybe we can canonicalize the cluster name shipped with each message, similar to what we want to do with Addresses, e.g. replace the cluster name with a short. -- 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, 8 months

4
15
0 / 0

[JBoss JIRA] Created: (JGRP-931) Logical addresses: canonicalize UUIDs with IDs (shorts)

by Bela Ban (JIRA)

Logical addresses: canonicalize UUIDs with IDs (shorts) ------------------------------------------------------- Key: JGRP-931 URL: https://jira.jboss.org/jira/browse/JGRP-931 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 Instead of using UUIDs as addresses, the cluster members should agree on shorts, e.g. 1 for A, 2 for B and so on, and use these instead of UUIDs. This happens after a certain warmup time. E.g. the coord could assign these IDs, so they're unique. IdAddress and UUID have to be able to do equals() or compareTo() with each other ! Advantage: - we send a short (2 bytes) instead of a UUID (16 bytes) - we use an IdAddress (class with a short) instead of a UUID. This is 6 bytes less per instance - IdAddress might be faster with equals() and hashCode() than UUID -- 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, 8 months

2
12
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1975) Initial OSGi JPA implementation

by Thomas Diesler (JIRA)

Initial OSGi JPA implementation ------------------------------- Key: EJBTHREE-1975 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1975 Project: EJB 3.0 Issue Type: Feature Request Reporter: Thomas Diesler Part of Enterprise OSGi there is JPA specification that we would like to have support for. This issue is the entry point for the initial implementation. Apache Aries ------------------ http://wiki.apache.org/incubator/AriesProposal Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a Java persistence project. It is related to Aries as a JPA persistence provider, including entity scanning and enhancement. The Aries project will make it easy for JPA persistence providers such as OpenJPA to be used in an OSGi environment and will provide container managed persistence for the Blueprint container. Eclipse Gemini -------------------- http://eclipse.org/proposals/gemini/ The subprojects will be created with the following initial IP components and donating companies: * Blueprint Service Implementation — SpringSource * Web Container Integration code — SpringSource * JPA Integration code for EclipseLink — Oracle * Implementation of JMX Mbeans and composite data types — Oracle * Derby JDBC Service Implementation — Oracle * JNDI Service Integration code — Oracle http://www.eclipse.org/eclipselink/ -- 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, 8 months

3
14
0 / 0

[JBoss JIRA] Created: (JBBUILD-670) Migrate existing Nexus Audit information to standard XML format

by Paul Gier (JIRA)

Migrate existing Nexus Audit information to standard XML format --------------------------------------------------------------- Key: JBBUILD-670 URL: https://issues.jboss.org/browse/JBBUILD-670 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: John Casey Fix For: Build Support 2011 We currently have audit information (username, timestamp) stored in .json files in the repository. Nexus uses an XML format to store this information, and recent versions of Nexus allow easy way to view this information in the Nexus UI. The existing audit information should be migrated to the standard Nexus XML format. These XML files are located in the directory "sonatype-work/nexus/proxy/attributes". For each file in each Maven repository hosted by Nexus, there is a file with the same name in this attributes directory. For example, "sonatype-work/nexus/proxy/attributes/jboss-releases/org/jboss/javaee/jboss-servlet-api/2.5.0.GA/jboss-servlet-api-2.5.0.GA.jar" is actually an XML file containing the attributes for the named jar file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
9
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 August 2011