January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-135) Extract the common use clustering code from the JBoss AS codebase

by Brian Stansberry (JIRA)

Extract the common use clustering code from the JBoss AS codebase ----------------------------------------------------------------- Key: JBCLUSTER-135 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-135 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Critical Fix For: Q3Y6 Remoting, Messaging, JBoss Cache and JBoss AS all have clustering aspects to their functionality. There is potential for code reuse between these projects that can't be realized if the clustering code resides in the cluster module of the AS codebase. 1) Extract general purpose clustering code from the AS cluster module into a separate project and produce binaries that other projects can use without creating a dependence on the AS project. 2) Provide APIs that both support standalone functionality of non-AS projects and facilitate ease of integration into the AS. This task is meant to be an umbrella task, with specific detailed subtasks. This task is primarily focused on meeting the short requirements of JBMESSAGING-516, but we also need to give due consideration to potential use in other projects. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-143) Create initial release schedule

by Brian Stansberry (JIRA)

Create initial release schedule ------------------------------- Key: JBCLUSTER-143 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-143 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Analyze when things need to be done so they can be integrated into dependent projects. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-142) Determine binaries

by Brian Stansberry (JIRA)

Determine binaries ------------------ Key: JBCLUSTER-142 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-142 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Need to determine what binaries should be built. Projects like Remoting want a lightweight binary, so we may need to create more than one. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3410) VDF Deployer migration tasks

by Scott M Stark (JIRA)

VDF Deployer migration tasks ---------------------------- Key: JBAS-3410 URL: http://jira.jboss.com/jira/browse/JBAS-3410 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services Reporter: Scott M Stark Assigned To: Dimitris Andreadis Priority: Blocker Fix For: JBossAS-5.0.0.Beta The deployers need to be migrated to the new VDF framework: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework The subtasks map to the deployers needing to be migrated. -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-754) RPC return values to use a marshaller as well

by Manik Surtani (JIRA)

RPC return values to use a marshaller as well --------------------------------------------- Key: JBCACHE-754 URL: http://jira.jboss.com/jira/browse/JBCACHE-754 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 Currently, all RPC calls go through the VersionAwareMarshaller which is responsible for efficiently marshalling JBC internal objects as well as user objects using JBoss Serialization. Return values and exceptions, on the other hand, are marshalled/unmarshalled using JGroups' Util.{to|from}ByteBuffer() which uses standard object serialization. The problems here are twofold: 1) Relatively inefficient (in speed as well as byte array size) marshalling/unmarshalling for return values 2) Potential class loader problems Most RPC calls in JBoss Cache do not have return values so this is not a problem that comes up often, but certain features (clustered cache loader, data gravitation in buddy replication) rely on return values. The solution to this problem is to be able to register a marshaller with the JGroups RPCDispatcher for return values (and exceptions) as well as for the RPC calls themselves. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-718) PojoCache TxLockInterceptor needs to release the lock node as well

by Ben Wang (JIRA)

PojoCache TxLockInterceptor needs to release the lock node as well ------------------------------------------------------------------ Key: JBCACHE-718 URL: http://jira.jboss.com/jira/browse/JBCACHE-718 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: 2.0.0 Currently, in TxLockInterceptor, I achieve the node lock by applying explicitly a cache.put(). It has two drawbacks: 1) It explicit going to insert a value to that node 2) Needs to do a remove when it is done. Not much can be done re: 1 now, but we should do 2, alhtough it will degrade the performance further. -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-788) Optimistic locking should not REQUIRE transactions!

by Manik Surtani (JIRA)

Optimistic locking should not REQUIRE transactions! --------------------------------------------------- Key: JBCACHE-788 URL: http://jira.jboss.com/jira/browse/JBCACHE-788 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0, 1.3.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 Makes things simpler. TXs are only used so transaction workspaces can be stored in a transaction entry. This workspace can just as easily be stored in ThreadLocal for non-tx calls (that just have the lifespan of a single invocation). This will: 1) Make things a LOT quicker since we don't need 2PC for all calls. 2) Make the TxInterceptor a lot simpler 3) Allow the use of Opt Locking without a TM -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-932) Implicit lock ownership check in UnversionedNode

by Manik Surtani (JIRA)

Implicit lock ownership check in UnversionedNode ------------------------------------------------ Key: JBCACHE-932 URL: http://jira.jboss.com/jira/browse/JBCACHE-932 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 This will involve read and write DIRECT methods on UnversionedNode to check whether the calling thread has acquired the necessary locks, else throw a lock exception. This will ensure proper concurrent access to the Node, even when not going through the interceptor stack. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-324) Build.xml in testsuite directory doesn't support multiple JVM argument

by Sunny Chan (JIRA)

Build.xml in testsuite directory doesn't support multiple JVM argument ---------------------------------------------------------------------- Key: JBBUILD-324 URL: http://jira.jboss.com/jira/browse/JBBUILD-324 Project: JBoss Build System Issue Type: Feature Request Components: Targets and Tasks Affects Versions: Repository Build head, Repsository Build Branch_4_0 Environment: Any Reporter: Sunny Chan Priority: Minor We are using the JBoss unit test as part of our JVM verification testsuite. We wanted to be able to invoke tests with multiple JVM options, but it didn't work. If you set parameters via build.sh -Djunit.vm.options with multiple paramters (e.g. -Djunit.vm.options="-d64 -verbose:gc"), it will fail with unrecongized option error. The problem is that in testsuite/build.xml, the junit.vm.options is passed onto junit ant task via <jvmarg value> tag rather then <jvmarg line> tag. The jvmarg line allows multiple JVM options exist in one line. Once I replace all instance of <jvmarg value="${junit.jvm.options}"/> with <jvmarg line="${junit.jvm.options}"/> then the problem goes away. I can provide a patch for this if you want - but I don't know the rules on patches (whether I need to be cleared for contribution) so let me know if you want that. -- 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, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-840) OutOfMemoryError: Java heap space

by Carlo de Wolf (JIRA)

OutOfMemoryError: Java heap space --------------------------------- Key: EJBTHREE-840 URL: http://jira.jboss.com/jira/browse/EJBTHREE-840 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: AS 4.2 (20070122) Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD OutOfMemoryError when running microbench -- 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

3
15
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 January 2007