March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREFLECT-101) Replace Cached tests by duplicate run of ClassPoolTestCase with cache enabled

by Flavia Rainone (JIRA)

Replace Cached tests by duplicate run of ClassPoolTestCase with cache enabled ----------------------------------------------------------------------------- Key: JBREFLECT-101 URL: https://jira.jboss.org/jira/browse/JBREFLECT-101 Project: JBoss Reflection Issue Type: Task Components: Class Pool Affects Versions: JBossReflection.2.2.0-Alpha3 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0-Alpha4 All Cached test classes simply inherit a test class and sets the "org.jboss.classpool.policy" system property value to "org.jboss.util.TimedCachePolicy". Below is an example of such test class: public class CachedArchiveClassPoolTestCase extends ArchiveClassPoolTestCase { public CachedArchiveClassPoolTestCase(String name) { super(name); } @Override protected void setUp() throws Exception { super.setUp(); System.setProperty(CtClassCacheFactory.POLICY_CLASS, TimedCachePolicy.class.getName()); } } These classes should be replaced by a second run of the extended ClassPoolTestCases with the system property configured as described. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-102) Remove uneeded ClassPool classes

by Flavia Rainone (JIRA)

Remove uneeded ClassPool classes -------------------------------- Key: JBREFLECT-102 URL: https://jira.jboss.org/jira/browse/JBREFLECT-102 Project: JBoss Reflection Issue Type: Task Components: BeanInfo Affects Versions: JBossReflection.2.2.0-Alpha4 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0-Alpha5 Once all changes made in JBAOP-742 as merged to JBoss AOP, we will be able to determine which ClassPool classes exactly are not going to be needed. This classes should be deleted. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1480) Specify Lock datarow on Sybase create tables

by Clebert Suconic (JIRA)

Specify Lock datarow on Sybase create tables -------------------------------------------- Key: JBMESSAGING-1480 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1480 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.4.0.SP3.CP04 Reporter: Clebert Suconic Assignee: Howard Gao Priority: Minor Fix For: 1.4.0.SP3.CP05, 1.4.3.GA Some users were complaining about dead locks on sybase with JBossMessaging. That trully is a config issue on sybase, but to avoid that maybe we should specify the lock schema at create table level, as shown on this doc. http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc20021_125... -- 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, 2 months

2
18
0 / 0

[JBoss JIRA] Created: (JGRP-932) Replace header names and protocol names with IDs

by Bela Ban (JIRA)

Replace header names and protocol names with IDs ------------------------------------------------ Key: JGRP-932 URL: https://jira.jboss.org/jira/browse/JGRP-932 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 We currently use strings as header names. Since a header has to have a magic number, we can replace strings with shorts. A short is always 2 bytes and we don't need to send (potentially long) names around. A message would then have a Headers hashmap of shorts and Headers. A protocol would also have to be able to catch its own headers, e.g. by creating a method getId(). UDP.getId() might return 56, which is the value in jg-magic-map.xml for TpHeader. This will solve https://jira.jboss.org/jira/browse/JGRP-872. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7787) DataSourcePersistentManager does not overwrite creation time when "re-inserting" a record

by Brian Stansberry (JIRA)

DataSourcePersistentManager does not overwrite creation time when "re-inserting" a record ----------------------------------------------------------------------------------------- Key: JBAS-7787 URL: https://jira.jboss.org/jira/browse/JBAS-7787 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-6.0.0.M2, JBossAS-6.0.0.M1 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M3 RDBMSStoreBase.storeSessionData handles a situation where an SQL INSERT of a new session fails due to an existing DB record by trying to do an SQL UPDATE. This update is not overwriting the creation time column. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7786) DataSourcePersistentManager storeSessionData attempts to continue using a db connection after an exception

by Brian Stansberry (JIRA)

DataSourcePersistentManager storeSessionData attempts to continue using a db connection after an exception ---------------------------------------------------------------------------------------------------------- Key: JBAS-7786 URL: https://jira.jboss.org/jira/browse/JBAS-7786 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-6.0.0.M2, JBossAS-6.0.0.M1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M3 RDBMSStoreBase.storeSessionData has some logic to try to handle situations where a new session insert fails because the db already has a record[1] by instead updating that existing record. This logic is flawed because it doesn't rollback the existing db connection and get a new one before attempting this. Result is the error shown in the forum thread. Fix is to rollback the connection and get a new one. [1] This scenario can occur if an expired session is still in the db, the client browser presents the old session cookie, and JBoss Web allows a new session with the old id. I'm not certain but I believe JBW 3 actually no longer allows this??? -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-464) Security Annotations to represent the Authentication, Authorization, Mapping and Audit

by Anil Saldhana (JIRA)

Security Annotations to represent the Authentication, Authorization, Mapping and Audit -------------------------------------------------------------------------------------- Key: SECURITY-464 URL: https://jira.jboss.org/jira/browse/SECURITY-464 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta2 -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7774) Upgrade to jboss-kernel 2.2.0.Alpha7

by Kabir Khan (JIRA)

Upgrade to jboss-kernel 2.2.0.Alpha7 ------------------------------------ Key: JBAS-7774 URL: https://jira.jboss.org/jira/browse/JBAS-7774 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7773) Upgrade to jboss-mdr 2.2.0.Alpha2

by Kabir Khan (JIRA)

Upgrade to jboss-mdr 2.2.0.Alpha2 --------------------------------- Key: JBAS-7773 URL: https://jira.jboss.org/jira/browse/JBAS-7773 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2321) Upgrade to WSRP 2.0

by Fernando Ribeiro (JIRA)

Upgrade to WSRP 2.0 ------------------- Key: JBPORTAL-2321 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2321 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.1 Final Reporter: Fernando Ribeiro Assignee: Chris Laprun The recent increase in the adoption of portal servers can drive more interest in WSRP in the next couple of years. WSRP 2.0 was published more than 1 year ago and hasn't been widely implemented yet. This may be targeted at 3.0 or beyond. -- 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, 2 months

2
3
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 March 2010