September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Deleted: (JGRP-1047) FC: change semantics of min_threshold

by Bela Ban (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-1047?page=com.atlassian.jira.plug... ] Bela Ban deleted JGRP-1047: --------------------------- > FC: change semantics of min_threshold > ------------------------------------- > > Key: JGRP-1047 > URL: https://jira.jboss.org/jira/browse/JGRP-1047 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > > FC.max_credits=1000000,min_threshold=0.2: > This means that when a receiver's credits for a sender drop below 800'000 bytes, the receiver will send 200'000 bytes to the sender. This can be misleading because one might think min_threshold means the number of bytes *remaining* after which to send new credits. > We need to either change the semantics of min_threshold, or introduce a new property. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JGRP-1045) UNICAST: change semantics of min_threshold

by Bela Ban (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-1045?page=com.atlassian.jira.plug... ] Bela Ban deleted JGRP-1045: --------------------------- > UNICAST: change semantics of min_threshold > ------------------------------------------ > > Key: JGRP-1045 > URL: https://jira.jboss.org/jira/browse/JGRP-1045 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > > min_threshold currently means the following (max_credits=1000000, min_theshold=0.2): > When the remaining credits drop below 800000 bytes, a receiver sends new credits. It doesn't mean that a receiver sends new credits when only min_theshold (200000) bytes are left ! > We need to either change the name of the property, or the semantics ! -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1048) FC: change semantics of min_threshold

by Bela Ban (JIRA)

FC: change semantics of min_threshold ------------------------------------- Key: JGRP-1048 URL: https://jira.jboss.org/jira/browse/JGRP-1048 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 FC.max_credits=1000000,min_threshold=0.2: This means that when a receiver's credits for a sender drop below 800'000 bytes, the receiver will send 200'000 bytes to the sender. This can be misleading because one might think min_threshold means the number of bytes *remaining* after which to send new credits. We need to either change the semantics of min_threshold, or introduce a new property. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1047) FC: change semantics of min_threshold

by Bela Ban (JIRA)

FC: change semantics of min_threshold ------------------------------------- Key: JGRP-1047 URL: https://jira.jboss.org/jira/browse/JGRP-1047 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 FC.max_credits=1000000,min_threshold=0.2: This means that when a receiver's credits for a sender drop below 800'000 bytes, the receiver will send 200'000 bytes to the sender. This can be misleading because one might think min_threshold means the number of bytes *remaining* after which to send new credits. We need to either change the semantics of min_threshold, or introduce a new property. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1045) UNICAST: change semantics of min_threshold

by Bela Ban (JIRA)

UNICAST: change semantics of min_threshold ------------------------------------------ Key: JGRP-1045 URL: https://jira.jboss.org/jira/browse/JGRP-1045 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 min_threshold currently means the following (max_credits=1000000, min_theshold=0.2): When the remaining credits drop below 800000 bytes, a receiver sends new credits. It doesn't mean that a receiver sends new credits when only min_theshold (200000) bytes are left ! We need to either change the name of the property, or the semantics ! -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-35) Get class name from Annotation

by Jeff Zhang (JIRA)

Get class name from Annotation ------------------------------ Key: JBANN-35 URL: https://jira.jboss.org/jira/browse/JBANN-35 Project: Papaki Issue Type: Feature Request Components: Core Reporter: Jeff Zhang Assignee: Jesper Pedersen Fix For: 1.0.0.Beta2 we get annotation info from AnnotationRepository by: Collection<Annotation> values = annotationRepository.getAnnotation(ConfigProperty.class); I need a feature that getting the class name that it contains the annotation, since we need attach the annotation information to different class. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2277) CLONE- ensure refined Japanese resource bundle is merged into BRMS 5.0.1 Branch

by Trevor Kirby (JIRA)

CLONE- ensure refined Japanese resource bundle is merged into BRMS 5.0.1 Branch ------------------------------------------------------------------------------- Key: JBRULES-2277 URL: https://jira.jboss.org/jira/browse/JBRULES-2277 Project: Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-guvnor Reporter: Yusuke Yamamoto Assignee: Mark Proctor -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-145) Create metadata model from annotations

by Jeff Zhang (JIRA)

Create metadata model from annotations -------------------------------------- Key: JBJCA-145 URL: https://jira.jboss.org/jira/browse/JBJCA-145 Project: JBoss JCA Issue Type: Task Components: Standalone Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Alpha3 create a metadata model from the annotations in deployers.ra.Annotations -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-6914) useJBossWebLoader not working when set to true

by Peter Johnson (JIRA)

useJBossWebLoader not working when set to true ---------------------------------------------- Key: JBAS-6914 URL: https://jira.jboss.org/jira/browse/JBAS-6914 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.1.0.CR1, JBossAS-5.0.1.GA Environment: any Reporter: Peter Johnson Assignee: Scott M Stark The description for useJBossWebLoader in server/xxx/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml indicates that if it is set to true, then classes packaged within the WAR file should be visible to classes outside the WAR file. For AS 4.2.3, that is the case. However, for 5.0.1 and 5.1.0.CR1 it is not the case. Seems like a feature of prior versions that did not survive the move to the new vfs classloaders. As a test case, download the source code for JBoss in Action from http://code.google.com/p/jbia/downloads/list. Open the jbia-src/index.html file and follow the setup instructions. Then build target 01 in the jbia-src/ch03 directory. Try different values for useJBossWebLoader, using Scenario C to test it - you should get a clean response with no exceptions when useJBossWebLoader is set to true, and and exception when it is set to false. -- 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, 10 months

4
12
0 / 0

[JBoss JIRA] Created: (JBCL-115) Module adds invalid delegates

by Thomas Diesler (JIRA)

Module adds invalid delegates ----------------------------- Key: JBCL-115 URL: https://jira.jboss.org/jira/browse/JBCL-115 Project: JBoss ClassLoader Issue Type: Bug Reporter: Thomas Diesler Fix For: JBossCL.2.0.7.GA Consider this use case ExportImportPackageUnitTestCase.testSelfImportPackage //Bundle-Name: BundleB //Bundle-SymbolicName: org.jboss.test.osgi.classloader.bundleB //Export-Package: org.jboss.test.osgi.classloader.support.b //Import-Package: org.jboss.test.osgi.classloader.support.a //Bundle-Name: BundleA //Bundle-Version: 1.0.0 //Bundle-SymbolicName: org.jboss.test.osgi.classloader.bundleA //Export-Package: org.jboss.test.osgi.classloader.support.a, org.jboss.test.osgi.classloader.support.b //Import-Package: org.jboss.test.osgi.classloader.support.a, org.jboss.test.osgi.classloader.support.b BundleB imports PackageA from BundleA, but *not* PackageB. Classes in PackageB are expected to get loaded from the bundle that the class load is initiated from. bundleB.start(); assertEquals("Bundle ACTIVE", Bundle.ACTIVE, bundleB.getState()); // BundleA is expected to resolve when BundleB gets started assertEquals("Bundle RESOLVED", Bundle.RESOLVED, bundleA.getState()); assertLoadClass(bundleA, A.class, bundleA); assertLoadClass(bundleA, B.class, bundleA); // BundleB imports A from BundleA assertLoadClass(bundleB, A.class, bundleA); // BundleB does not import B assertLoadClass(bundleB, B.class, bundleB); --------------------- The code in Module.addDelegates(...) incorrectly adds the DelegateLoader from the dependent module irrespectively of the packages that are actually being imported. this effectively makes makes all the packages from BundleA visible to BundleB Module other = item.getModule(); DelegateLoader delegate = iDependOnModule.getDelegateLoader(other, requirement); // Check for re-export by the module if (requirement.wantReExports()) addDelegates(iDependOnModule, delegates, dynamic, visited, true); // We want a module's re-exports (i.e. part of its imports) before the module itself if (delegate != null) delegates.add(delegate); -- 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, 10 months

1
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 September 2009