September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7252) Upgrade JBoss LogManager to 1.1.0.GA

by David Lloyd (JIRA)

Upgrade JBoss LogManager to 1.1.0.GA ------------------------------------ Key: JBAS-7252 URL: https://jira.jboss.org/jira/browse/JBAS-7252 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd -- 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

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-168) Papaki 1.0.0.Beta1

by Jesper Pedersen (JIRA)

Papaki 1.0.0.Beta1 ------------------ Key: JBJCA-168 URL: https://jira.jboss.org/jira/browse/JBJCA-168 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha4 -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBANN-37) Papaki 1.0.0.Beta2

by Jesper Pedersen (JIRA)

Papaki 1.0.0.Beta2 ------------------ Key: JBANN-37 URL: https://jira.jboss.org/jira/browse/JBANN-37 Project: Papaki Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.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

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBANN-36) Support scanning directories

by Jesper Pedersen (JIRA)

Support scanning directories ---------------------------- Key: JBANN-36 URL: https://jira.jboss.org/jira/browse/JBANN-36 Project: Papaki Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta2 Support scanning directories for .class files -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7240) DataVersioningException when using EJB3 entities with OPTIMISTIC caching

by Dennis Reed (JIRA)

DataVersioningException when using EJB3 entities with OPTIMISTIC caching ------------------------------------------------------------------------ Key: JBAS-7240 URL: https://jira.jboss.org/jira/browse/JBAS-7240 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.3.GA Reporter: Dennis Reed Assignee: Dennis Reed Fix For: JBossAS-Branch_4_2 org.jboss.ejb3.entity.OptimisticJBCCache.DataVersionAdapter.newerThan incorrectly returns true for A.newerThan ( A ). This causes JBoss Cache to throw a DataVersioningException when trying to remove the entry from the cache. -- 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

14 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1154) Client.connect() should throw an exception when Lease creation fails

by Ron Sigal (JIRA)

Client.connect() should throw an exception when Lease creation fails -------------------------------------------------------------------- Key: JBREM-1154 URL: https://jira.jboss.org/jira/browse/JBREM-1154 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 When any of the versions of org.jboss.remoting.Client.connect() is called, it will try, if leasing is enabled, to register the Client with an org.jboss.remoting.Lease on the server side. Client.connect() calls org.jboss.remoting.MicroRemoteClientInvoker.establishLease(), which calls org.jboss.remoting.LeasePinger.addClient(), which calls LeasePinger.sendClientPing(), which sends to the server the Clients it represents. If LeasePinger.sendClientPing() fails, it just logs a message and swallows the exception. That behavior is appropriate when sendClientPing() is just sending an ordinary PING, but if the attempt to register a new Client fails, the call to Client.connect() should fail. -- 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

14 years, 8 months

1
3
0 / 0

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

by Bela Ban (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-1048?page=com.atlassian.jira.plug... ] Bela Ban deleted JGRP-1048: --------------------------- > 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 > > 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

14 years, 8 months

1
0
0 / 0

[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

14 years, 8 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

14 years, 8 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

14 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2009