January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-738) Add format of persistent state transfer to CacheLoader API Javadoc

by Brian Stansberry (JIRA)

Add format of persistent state transfer to CacheLoader API Javadoc ------------------------------------------------------------------ Key: JBCACHE-738 URL: http://jira.jboss.com/jira/browse/JBCACHE-738 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0 Persistent state is a serialized series of NodeData objects. All the standard CacheLoader impls use this format. The requirement to use this format should be added to the CacheLoader API Javadoc to make it part of the official API contract. This will ensure interoperability between cache loaders (e.g state generated by a user's CustomCacheLoader can be stored by JDBCCacheLoader, 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, 3 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBAS-3355) DetachedHANamingService does not register its ObjectName with Registry

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3355?page=all ] Brian Stansberry updated JBAS-3355: ----------------------------------- Fix Version/s: (was: JBossAS-4.2.0.CR1) JBossAS-5.0.0.CR1 > DetachedHANamingService does not register its ObjectName with Registry > ---------------------------------------------------------------------- > > Key: JBAS-3355 > URL: http://jira.jboss.com/jira/browse/JBAS-3355 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering, Naming > Affects Versions: JBossAS-4.0.4.GA > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > DetachedHANamingService does not register its ObjectName with Registry. Because of this, if it is used with ProxyFactoryHA and JRMPInvokerHA, calls to it will fail in JRMPInvokerHA.invoke due to a failure lookup the ObjectName in the registry. > The purpose of having DetachedHANamingService as a distinct base class from HANamingService is to allow use with the detached invokers, so not having this work kind of defeats the point. -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2315) Create an automated test for JBAS-2314

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2315?page=all ] Brian Stansberry updated JBAS-2315: ----------------------------------- Fix Version/s: (was: JBossAS-4.2.0.CR1) JBossAS-4.2.0.GA Move to the 4.2.0.GA. This is a testsuite improvement; doesn't need to be in 4.2.0.CR1. > Create an automated test for JBAS-2314 > -------------------------------------- > > Key: JBAS-2315 > URL: http://jira.jboss.com/jira/browse/JBAS-2315 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-4.2.0.GA > > > I currently test the JBAS-2314 fix manually; need to automate. Basically need to add a war to web-sso.ear that has secured resources but no authenticator configured. Test should access the normal sso test war on one server, then the other, and then on the 2nd server access the war w/o authenticator, confirming that no 403 is seen. -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2614) Add a stress test of region activation/inactivation under load

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2614?page=all ] Brian Stansberry updated JBAS-2614: ----------------------------------- Fix Version/s: (was: JBossAS-4.2.0.CR1) JBossAS-5.0.0.CR1 > Add a stress test of region activation/inactivation under load > -------------------------------------------------------------- > > Key: JBAS-2614 > URL: http://jira.jboss.com/jira/browse/JBAS-2614 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.CR1 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > There are already tests of this in the JBossCache testsuite, but a test that involves the JBossCacheManager layer as well would be good. -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-973) Cache Invalidation fails when redeploy CMP beans

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-973?page=all ] Brian Stansberry updated JBAS-973: ---------------------------------- Fix Version/s: (was: JBossAS-4.2.0.CR1) JBossAS-5.0.1.CR1 Moving out to 5.0.1, as I don't us having resources for this in the next 6 months > Cache Invalidation fails when redeploy CMP beans > ------------------------------------------------ > > Key: JBAS-973 > URL: http://jira.jboss.com/jira/browse/JBAS-973 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering, EJB2 > Affects Versions: JBossAS-3.2.6 Final > Reporter: SourceForge User > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.1.CR1 > > > SourceForge Submitter: coneheed . > Java version: 1.4.2_04,Sun Microsystems Inc. > Java VM: Java HotSpot(TM) Client VM 1.4.2_04-b05 > ,Sun Microsystems Inc. > OS-System: Windows 2000 5.0,x86 > We have in place a clustering architecture as described > in the JBoss clustering book. > It currently consists of 3 nodes. 2 "read-only" nodes > whose CMP entity beans have read-only accessor > methods and a "read-write" node where the entity beans > have "read-write" accessor methods. > We use the cache invalidation architecture (based on > JGroups) to link the read-only and read-write beans > together. Changes to the RW beans cause invalidation in > the RO beans and the data remains consistent. > This all appears to work fine until we redeploy our > application jar files. The system continues to function > but we get out of date data in our RO beans. Basically > the RO beans are not asked to ejbLoad and hence re- > read the data from the DB. > Bounce all 3 nodes and the system works fine again. > Redeplying to the RW node is OK but redeploying to the > RO node breaks the cache invalidation. > Forum article: > http://www.jboss.org/index.html?module=bb&op=viewtopic&t=50823 > Regards -- 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 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2850) Create patch for standalone Tomcat SSO valve incorporating the JBAS-2429 fix

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2850?page=all ] Brian Stansberry updated JBAS-2850: ----------------------------------- Fix Version/s: JBossAS-5.0.0.Beta2 (was: JBossAS-4.2.0.CR1) > Create patch for standalone Tomcat SSO valve incorporating the JBAS-2429 fix > ---------------------------------------------------------------------------- > > Key: JBAS-2850 > URL: http://jira.jboss.com/jira/browse/JBAS-2850 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.Beta2 > > > The fix for JBAS-2429 is applicable to the standalone valve as well, so need to create a patch and present it to the Tomcat community. -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-401) Do not disregard specified target node in partial state transfer with MUX channel

by Vladimir Blagojevic (JIRA)

Do not disregard specified target node in partial state transfer with MUX channel --------------------------------------------------------------------------------- Key: JGRP-401 URL: http://jira.jboss.com/jira/browse/JGRP-401 Project: JGroups Issue Type: Bug Affects Versions: 2.4, 2.5 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Partial state transfer method on MUX channel [1] always fetches partial state from service view coordinator[2] disregarding specified target parameter. We should correct this algorithm so that specified node target T is used as state provider if T is indeed a member of a service view, otherwise default to service view coordinator. [1] public boolean getState(Address target, String state_id, long timeout) throws ChannelNotConnectedException, ChannelClosedException [2] first node in a MUX service view -- 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 months

1
1
0 / 0

Al igual que los Cisnes de Cuello Negro, encuentre Ud. el refugio perfecto.

by Hotel Licahue

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-719) Capturing I/O Exceptions from invocation on Valve

by Clebert Suconic (JIRA)

Capturing I/O Exceptions from invocation on Valve ------------------------------------------------- Key: JBMESSAGING-719 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-719 Project: JBoss Messaging Issue Type: Sub-task Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.Beta2 We should capture exceptions from invocations and perform failover instead of throwing IOException or remoting.CannotConnectionException. -- 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 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-712) FailoverTest.testFailoverMessageOnServer2() deadlocks

by Ovidiu Feodorov (JIRA)

FailoverTest.testFailoverMessageOnServer2() deadlocks ----------------------------------------------------- Key: JBMESSAGING-712 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-712 Project: JBoss Messaging Issue Type: Sub-task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.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, 3 months

1
3
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