November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1226) State transfer doesn't clean out persistent store if size of transferred persistent state is 0

by Brian Stansberry (JIRA)

State transfer doesn't clean out persistent store if size of transferred persistent state is 0 ---------------------------------------------------------------------------------------------- Key: JBCACHE-1226 URL: http://jira.jboss.com/jira/browse/JBCACHE-1226 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.SP7 Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Minor StateTransferIntegrator_140.integratePersistentState() is a no-op if the size of the provided persistent state is 0. So, if persistent state transfer is enabled but the provider doesn't have any persistent state to transfer, any stale persistent state laying around on the recipient will not get cleaned up. A fix for this needs to properly discriminate between the above case and one where no persistent state is available because persistent state transfer is disabled. Manik, I found this when a solution to an EJB3 bug didn't work as expected. I can tweak my solution to get around it, so this isn't urgent for me. Feel free to assign to me, although I likely won't get to it for a long time. This likely affects all releases in the 1.x series. A *quick* look at how this works leads me to expect it's not an issue in 2.x. -- 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

18 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4301) Evaluate replacing FileCacheLoader with JdbmCacheLoader

by Brian Stansberry (JIRA)

Evaluate replacing FileCacheLoader with JdbmCacheLoader ------------------------------------------------------- Key: JBAS-4301 URL: http://jira.jboss.com/jira/browse/JBAS-4301 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Need to establish a relationship with the JDBM guys to see how suitable and supportable it is. -- 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

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-378) Research options for testing dependency version ranges

by Paul Gier (JIRA)

Research options for testing dependency version ranges ------------------------------------------------------ Key: JBBUILD-378 URL: http://jira.jboss.com/jira/browse/JBBUILD-378 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: MavenBuild 2007 It would be helpful to be able to automatically run a maven build with each of the valid combinations of dependency versions. For example, if a dependency includes a version range of 1.1, 1.2, and 1.3. We would want to build and test the project using each of these versions to make sure that they all work correctly. Sherriff on the maven forum has worked on something like this for continuum. When we move our automated builds to hudson, maybe we could create something similar to this. -- 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

18 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-408) Figure out a way to use alternate pom files in modules.

by Paul Gier (JIRA)

Figure out a way to use alternate pom files in modules. ------------------------------------------------------- Key: JBBUILD-408 URL: http://jira.jboss.com/jira/browse/JBBUILD-408 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Currently the jdk14 builds have to be done as separate modules, because maven is not able to use alternate files (pom-jdk14.xml) in modules. This issue has been created to address this in maven: http://jira.codehaus.org/browse/MNG-3150 Until this issue is resolved, maybe an ant script can be created to build the modules as an aggregate. -- 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

18 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-417) Change maven classpath ordering for dependencies

by Paul Gier (JIRA)

Change maven classpath ordering for dependencies ------------------------------------------------ Key: JBBUILD-417 URL: http://jira.jboss.com/jira/browse/JBBUILD-417 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 Currently maven puts transitive dependencies first in the compile and test classpaths. It would be better to have direct dependencies listed first. See this maven issue: http://jira.codehaus.org/browse/MNG-3197 -- 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

18 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-391) Create jboss.org site for maven-jdocbook-plugin

by Paul Gier (JIRA)

Create jboss.org site for maven-jdocbook-plugin ----------------------------------------------- Key: JBBUILD-391 URL: http://jira.jboss.com/jira/browse/JBBUILD-391 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - Maint 2007 Steve created the jdocbook plugin for maven. This should be the new standard docbook configuration within jboss. A site needs to be created for the plugin documentation on jboss.org. -- 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

18 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-628) Discovery: add cluster name to discovery request to be able to discard responses from different clusters

by Bela Ban (JIRA)

Discovery: add cluster name to discovery request to be able to discard responses from different clusters -------------------------------------------------------------------------------------------------------- Key: JGRP-628 URL: http://jira.jboss.com/jira/browse/JGRP-628 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.1, 2.7 When we have 2 groups ONE and TWO: ONE: 228.8.8.8:7500 and TWO: 228.1.2.3:7500 In some cases, they will receive each other's traffic (http://wiki.jboss.org/wiki/Wiki.jsp?page=PromiscuousTraffic). Assume ONE has members {A,B,C} and TWO has no members yet. When D (in cluster TWO) starts up and sends out a discovery request, it might also receive discovery responses from ONE (A,B,C). D might now identify A as coordinator and send a JOIN-REQ to A. However, A will discard that request as the group name of D's request is TWO rather than ONE ! Result: D's JOIN-REQ will hang ! Note that the transport (TP) does drop messages from different clusters, but this happens only after the new member has joined the group, so discovery requests/responses from different groups are *not* discarded. Tasks: - Verify that the transport-name matching algorithm in TP is correct - Confirm that - on initial discovery - discovery requests and responses are not matched -- 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

18 years, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1134) Move JNDI Binding Policy to its own Project

by Andrew Lee Rubinger (JIRA)

Move JNDI Binding Policy to its own Project ------------------------------------------- Key: EJBTHREE-1134 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1134 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Blocker Currently in Ext-API, move into new Project with its own lifecycle. -- 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

18 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1138) Create a set of Persistence Unit deployers

by Carlo de Wolf (JIRA)

Create a set of Persistence Unit deployers ------------------------------------------ Key: EJBTHREE-1138 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1138 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: AS 5.0.0.Beta3 -- 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

18 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1133) Resolve API Leaks in Ext-API

by Andrew Lee Rubinger (JIRA)

Resolve API Leaks in Ext-API ---------------------------- Key: EJBTHREE-1133 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1133 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger The following are internals and must be moved outside the external API: org.jboss.ejb3.remoting.RemoteProxyFactory org.jboss.ejb3.ProxyFactory -- 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

18 years, 4 months

2
4
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 November 2007