October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-690) TcpCacheServer never gets out of STARTING state, and doesn't shut down socket when stop() is called.

by Manik Surtani (JIRA)

TcpCacheServer never gets out of STARTING state, and doesn't shut down socket when stop() is called. ---------------------------------------------------------------------------------------------------- Key: JBCACHE-690 URL: http://jira.jboss.com/jira/browse/JBCACHE-690 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.3.0, 1.4.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 Looks like a bug in the lifecycle methods, doesn't stop normal operations though. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3782) Wrong "Specification-Version: 1.0.0.GA" in jboss-common.jar

by Steven Deng (JIRA)

Wrong "Specification-Version: 1.0.0.GA" in jboss-common.jar ----------------------------------------------------------- Key: JBAS-3782 URL: http://jira.jboss.com/jira/browse/JBAS-3782 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Environment: JBoss AS 4.0.5.GA Reporter: Steven Deng Priority: Trivial "Specification-Version: 1.0.0.GA" in MANEFEST.MF of <jboss4.0.5 install dir>\lib\jboss-common.jar while this entry should be "Specification-Version: 4.0.5.GA". -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-342) Simplify GossipRouter, GossipClient and RouterStub

by Bela Ban (JIRA)

Simplify GossipRouter, GossipClient and RouterStub -------------------------------------------------- Key: JGRP-342 URL: http://jira.jboss.com/jira/browse/JGRP-342 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.4 - Remove unneeded threads in GossipRouter - Make GossipRouter, GossipClient and RouterStub use the same marshalling code (GossipData), based on Streamable -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-758) javax.ejb.EJBNoSuchObjectException should be javax.ejb.NoSuchEJBException

by Carlo de Wolf (JIRA)

javax.ejb.EJBNoSuchObjectException should be javax.ejb.NoSuchEJBException ------------------------------------------------------------------------- Key: EJBTHREE-758 URL: http://jira.jboss.com/jira/browse/EJBTHREE-758 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-756) use InitialContext props everywhere (TxUtil) for e-ejb3

by William DeCoste (JIRA)

use InitialContext props everywhere (TxUtil) for e-ejb3 ------------------------------------------------------- Key: EJBTHREE-756 URL: http://jira.jboss.com/jira/browse/EJBTHREE-756 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: William DeCoste Assigned To: William DeCoste -- 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, 2 months

1
1
0 / 0

Confie en una empresa 100% Chilena.

by Hostex

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAOP-233) Fix the serialization test for aop proxies

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-233?page=all ] Kabir Khan closed JBAOP-233. ---------------------------- Resolution: Done > Fix the serialization test for aop proxies > ------------------------------------------ > > Key: JBAOP-233 > URL: http://jira.jboss.com/jira/browse/JBAOP-233 > Project: JBoss AOP > Issue Type: Sub-task > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-35) Externalize the buffer queue size in LRUAlgorithm

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-35?page=all ] Manik Surtani closed JBCACHE-35. -------------------------------- Resolution: Duplicate Issue JBCACHE-684 > Externalize the buffer queue size in LRUAlgorithm > ------------------------------------------------- > > Key: JBCACHE-35 > URL: http://jira.jboss.com/jira/browse/JBCACHE-35 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Ben Wang > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Currently, the LRUAlgorithm use a hard size of 5000 on the buffer queue to process node eviction. We should make this configurable so it can adapt to different enviornment. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-759) Jacc layer should use the roles from the JBoss Security Manager

by Anil Saldhana (JIRA)

Jacc layer should use the roles from the JBoss Security Manager --------------------------------------------------------------- Key: EJBTHREE-759 URL: http://jira.jboss.com/jira/browse/EJBTHREE-759 Project: EJB 3.0 Issue Type: Feature Request Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD The Jacc Helper uses the principals stored in the subject for doing perm checks. There can be a need to perform role mapping on the roles. It is necessary to pick the roles from the JBoss Security Manager. We can use RealmMapping.getUserRoles to maintain compatibility with the 4.0.x series. In HEAD, ReamMapping calls internally the AuthorizationManager which will do role mapping (if user wishes) before providing the current roles. In 4.0.x, RealmMapping.getUserRoles anyway gets the roles from the authenticated subject. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBCACHE-664) Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-664?page=all ] Manik Surtani closed JBCACHE-664. --------------------------------- Resolution: Done > Add JBossRetro jars, baseline to Java5 and create a Java1.4 compat binary > ------------------------------------------------------------------------- > > Key: JBCACHE-664 > URL: http://jira.jboss.com/jira/browse/JBCACHE-664 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.4.0 > Reporter: Manik Surtani > Assigned To: Manik Surtani > Priority: Critical > Fix For: 2.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > * Use JBossRetro to build a compat version of JBossCache > * Baseline against Java5 for 'normal' builds > * Don't migrate concurrent.jar - still stick with concurrent.jar for concurrent utils rather than java.util.concurrent. -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006