September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCL-114) org.jboss.classloader.spi.base.BaseClassLoader.loadClass is inefficient on loading recurring classes

by Carlo de Wolf (JIRA)

org.jboss.classloader.spi.base.BaseClassLoader.loadClass is inefficient on loading recurring classes ---------------------------------------------------------------------------------------------------- Key: JBCL-114 URL: https://jira.jboss.org/jira/browse/JBCL-114 Project: JBoss ClassLoader Issue Type: Bug Affects Versions: JBossCL.2.0.6.GA Reporter: Carlo de Wolf Priority: Blocker Fix For: JBossCL.2.0.7.GA Whenever something asks for a class to be loaded we run into lock contention problems on org.jboss.classloader.spi.base.BaseClassLoader. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7234) Reduce failed classloading logs from ERROR to WARN

by Dennis Reed (JIRA)

Reduce failed classloading logs from ERROR to WARN -------------------------------------------------- Key: JBAS-7234 URL: https://jira.jboss.org/jira/browse/JBAS-7234 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.1.0.GA Reporter: Dennis Reed Assignee: Dennis Reed LoadMgr3 logs a failure to load a class as ERROR, but this is not always an error. For example, Seam attempts to load clustering classes, and catches the exception to disable its PojoCache. This should not be logged as an ERROR. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-1041) Provide more DEBUG level information on Channel resources used when running tests in parallel

by Richard Achmatowicz (JIRA)

Provide more DEBUG level information on Channel resources used when running tests in parallel --------------------------------------------------------------------------------------------- Key: JGRP-1041 URL: https://jira.jboss.org/jira/browse/JGRP-1041 Project: JGroups Issue Type: Feature Request Affects Versions: 2.8 Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz Priority: Minor Fix For: 2.8 When running tests in parallel under testng, the JGroups testsuite provides mechanisms to allocate channel resources (udp.mcast_addr, udp..mcast_port, bind_port, port_range) in such a way that JGroups channels in different tests do not interfere with each other. This is done by allocating non-overlapping ranges of addresses and ports. However, there is a rather complex trail to follow when trying to find which addresses will be picked up by tests: * build.xml + build.properties, which feed to * runtest parameters, which feed to * testng parameters, which feed to * ChannelTestBase parameters, which feed to * test case paramaters At present, it is not easy to discover which values a test is using for the channel resources mentioned above. It would be nice to be able to see this information in the DEBUG logs, to aid in resolving problesm with the wrong addresses being used. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7235) Enable EAR isolation by default

by Jason T. Greene (JIRA)

Enable EAR isolation by default ------------------------------- Key: JBAS-7235 URL: https://jira.jboss.org/jira/browse/JBAS-7235 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: ClassLoading Reporter: Jason T. Greene Assignee: Scott M Stark Fix For: JBossAS-5.2.0.Beta1 The EE spec and modern deployments (seam, web beans, etc) require isolation. Previously EAR isolation has been set to default for legacy compatibility, however, the legacy cases are becoming less common. 5.2 is a good release to make this change. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-186) Ensure loadClass on classloader happens during initialization and not during request handling

by Anil Saldhana (JIRA)

Ensure loadClass on classloader happens during initialization and not during request handling --------------------------------------------------------------------------------------------- Key: JBID-186 URL: https://jira.jboss.org/jira/browse/JBID-186 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.beta1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.CR2 loadClass is a synchronized operation. Hence needs to be performed during initialization. The request handling process can then do clazz.newInstance. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-169) JBoss Security SPI 2.1.0.20090318

by Jesper Pedersen (JIRA)

JBoss Security SPI 2.1.0.20090318 --------------------------------- Key: JBJCA-169 URL: https://jira.jboss.org/jira/browse/JBJCA-169 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha4 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-34) Papaki 1.0.0.Beta1

by Jesper Pedersen (JIRA)

Papaki 1.0.0.Beta1 ------------------ Key: JBANN-34 URL: https://jira.jboss.org/jira/browse/JBANN-34 Project: Papaki Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (GPD-355) offer conversion support for files from jBPM 3 to jBPM 4

by Koen Aers (JIRA)

offer conversion support for files from jBPM 3 to jBPM 4 -------------------------------------------------------- Key: GPD-355 URL: https://jira.jboss.org/jira/browse/GPD-355 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assignee: Koen Aers Priority: Minor Fix For: jBPM jPDL Designer 4.0.0.GA -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBANN-33) Add maven release script

by Jesper Pedersen (JIRA)

Add maven release script ------------------------ Key: JBANN-33 URL: https://jira.jboss.org/jira/browse/JBANN-33 Project: Papaki Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.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, 8 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBJCA-167) Generic Connection Manager Implementation

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBJCA-167?page=com.atlassian.jira.plug... ] Jesper Pedersen updated JBJCA-167: ---------------------------------- Component/s: Core > Generic Connection Manager Implementation > ----------------------------------------- > > Key: JBJCA-167 > URL: https://jira.jboss.org/jira/browse/JBJCA-167 > Project: JBoss JCA > Issue Type: Task > Components: Core > Reporter: Gurkan Erdogdu > Assignee: Gurkan Erdogdu > Fix For: 1.0.0.Alpha4 > > > Implementation of the ConnectionManager, Non Tx Connection Manager and Tx Connection Manager. Using JBoss 5.X branch. -- 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, 8 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 September 2009