April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-830) Incorrect serialization of Collection and Map proxies

by Brian Stansberry (JIRA)

Incorrect serialization of Collection and Map proxies ----------------------------------------------------- Key: JBCACHE-830 URL: http://jira.jboss.com/jira/browse/JBCACHE-830 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.0.SP1, 1.4.0.GA, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0.GA, 1.2.4SP2 Reporter: Brian Stansberry Assigned To: Ben Wang The PojoCache Collection and Map proxies implement Serializable via List but don't do anything to override default serialization. They have non-transient fields with refs to things like the cache itself, so serializing one of these is a big problem -- you serialize the whole cache. Not sure what the best solution to this is. Perhaps use writeReplace()? -- 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

19 years

3
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-990) PojoCache leaks memory

by Manik Surtani (JIRA)

PojoCache leaks memory ---------------------- Key: JBCACHE-990 URL: http://jira.jboss.com/jira/browse/JBCACHE-990 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 2.0.0.ALPHA2, 2.0.0.BETA1 Reporter: Manik Surtani Assigned To: Jason T. Greene Priority: Critical Fix For: 2.0.0.BETA2 I've included the test from the forum thread into tests/perf/org/jboss/cache/manualtests/PojoCacheMemoryLeakTest.java - note that since this is in the "manualtests" package, it will not be run by cruise control. When running from within my IDE, after about 8 loops it bombs with an OOME. -- 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

19 years

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-774) PojoCache to use a RPC layer to transmit POJO events

by Ben Wang (JIRA)

PojoCache to use a RPC layer to transmit POJO events ---------------------------------------------------- Key: JBCACHE-774 URL: http://jira.jboss.com/jira/browse/JBCACHE-774 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Critical Fix For: PojoCache 2.1.0 Currently, the POJO events does not propagate to other nodes since there is no way to do that. We will need some specific RPC mechanism to that such that we can broadcast POJO attach, detach, and modification events. This will also help to remove the POJO cache interceptor on the remote node as well. -- 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

19 years

3
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-933) PojoCache to create a cache wrapper to retry when upgradeexception is encountered

by Ben Wang (JIRA)

PojoCache to create a cache wrapper to retry when upgradeexception is encountered --------------------------------------------------------------------------------- Key: JBCACHE-933 URL: http://jira.jboss.com/jira/browse/JBCACHE-933 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0.BETA1 Current 2.0 release becuase of lock contention on __JBossInternal__, it becomes much more common to have lock UpgradeException. Solutions are: 1. Fix the underlying cache lock algorithm to allow lock upgrade. This can be tricky since it affects lots of other codes. 2. Re-try the logic in a Cache wrapper when UpgradeException is encountered. I think option #2 is the best route now. -- 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

19 years

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-706) Integrate JMX bindings of JBoss Cache and PojoCache with AS5 and MC

by Manik Surtani (JIRA)

Integrate JMX bindings of JBoss Cache and PojoCache with AS5 and MC ------------------------------------------------------------------- Key: JBCACHE-706 URL: http://jira.jboss.com/jira/browse/JBCACHE-706 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 This will involve: 1. Adding new JMX MBean interface (is this necessary for the MC? What about standalone use?) 2. Providing sample XML files 3. Updating documentation -- 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

19 years

3
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1004) Genericize POJO API

by Jason T. Greene (JIRA)

Genericize POJO API ------------------- Key: JBCACHE-1004 URL: http://jira.jboss.com/jira/browse/JBCACHE-1004 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Jason T. Greene Assigned To: Jason T. Greene Fix For: 2.0.0.GA Use generics where possible and logical -- 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

19 years

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-983) State transfer test failures ( to do with concurrent eviction )

by Manik Surtani (JIRA)

State transfer test failures ( to do with concurrent eviction ) --------------------------------------------------------------- Key: JBCACHE-983 URL: http://jira.jboss.com/jira/browse/JBCACHE-983 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.BETA1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 -- 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

19 years

2
10
0 / 0

[JBoss JIRA] Created: (GPD-12) Same JBPM project shared with each person having different JBPM installation program

by Tom Baeyens (JIRA)

Same JBPM project shared with each person having different JBPM installation program ------------------------------------------------------------------------------------ Key: GPD-12 URL: http://jira.jboss.com/jira/browse/GPD-12 Project: JBoss jBPM GPD Issue Type: Bug Reporter: Tom Baeyens Assigned To: Koen Aers JBPM-794 -- 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

19 years

3
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-168) Add a plugin spi to support the ordering of deployment package/bundle processing

by Scott M Stark (JIRA)

Add a plugin spi to support the ordering of deployment package/bundle processing -------------------------------------------------------------------------------- Key: JBMICROCONT-168 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-168 Project: JBoss MicroContainer Issue Type: Feature Request Components: Deployment Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0_CR1 There are some startup issues in jboss5 due to not having an ordering notion for the DeploymentContexts that go into a MainDeployer.process scan. Probably all of these are due to improper specification of container dependencies, but in general we are going to run into startup issues due to missed dependency declaration. We should have the ability to order the DeploymentContext set via an spi contract that integrates with the structural parse phase. We should have the ability to define this globally ala the legacy directory scanner sorter, as well as per deployment level to allow for alternate deployment packaging models: Russian doll, ear, cross deployment model, etc. -- 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

19 years

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-893) JBPM_VARIABLEINSTANCE.STRINGVALUE_ is inconsistent with JBPM_LOG.OLDSTRINGVALUE_ and JBPM_LOG.NEWSTRINGVALUE_

by Romeu Figueira (JIRA)

JBPM_VARIABLEINSTANCE.STRINGVALUE_ is inconsistent with JBPM_LOG.OLDSTRINGVALUE_ and JBPM_LOG.NEWSTRINGVALUE_ ------------------------------------------------------------------------------------------------------------- Key: JBPM-893 URL: http://jira.jboss.com/jira/browse/JBPM-893 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: JBoss AS 4.0.5 GA + jBPM 3.1.4 + RHEL 4 + Oracle 10g Reporter: Romeu Figueira Assigned To: Tom Baeyens Priority: Minor Fix For: jBPM 3.1.5 The column JBPM_VARIABLEINSTANCE.STRINGVALUE_ is slated as VARCHAR2(255 char) while JBPM_LOG.OLDSTRINGVALUE_ and JBPM.NEWSTRINGVALUE_ are slated as VARCHAR2(4000). These two values should be a match between each other. -- 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

19 years

3
2
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 April 2007