March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCLUSTER-117) Clustered deployments using the Profile Service

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-117?page=all ] Brian Stansberry updated JBCLUSTER-117: --------------------------------------- Fix Version/s: Q2Y7 (was: Q4Y6) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) > Clustered deployments using the Profile Service > ----------------------------------------------- > > Key: JBCLUSTER-117 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-117 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Blocker > Fix For: Q2Y7 > > > Basic farmed and singleton deployments using microcontainer services (Profile Service, Virtual Deployment Framework). -- 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: (JBCLUSTER-8) Stateful session bean (SFSB) replication in EJB3

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-8?page=all ] Brian Stansberry updated JBCLUSTER-8: ------------------------------------- Fix Version/s: Q2Y7 (was: Q1Y7) > Stateful session bean (SFSB) replication in EJB3 > ------------------------------------------------ > > Key: JBCLUSTER-8 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-8 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Critical > Fix For: Q2Y7 > > > Currently Bill has implemented SFSB in ejb3 using JBossCache. Need to track further integration issue(s). -- 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: (JBCLUSTER-96) Benchmark the new SFSB impl

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-96?page=all ] Brian Stansberry updated JBCLUSTER-96: -------------------------------------- Fix Version/s: Q2Y7 (was: Q1Y7) Moving to Q2Y7; will probably be Q3. > Benchmark the new SFSB impl > --------------------------- > > Key: JBCLUSTER-96 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-96 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q2Y7 > > > Once complete more tests toward SFSB and fine-grained, we will need to do benchmark as well. Note that maybe we can use the current web benchmakr (like jbento) to load test. This has the benefit for Seam in the future as well. -- 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: (JBCLUSTER-115) Major Clustering Features in JBoss 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-115?page=all ] Brian Stansberry updated JBCLUSTER-115: --------------------------------------- Fix Version/s: Q3Y7 (was: Q4Y6) > Major Clustering Features in JBoss 5.0 > -------------------------------------- > > Key: JBCLUSTER-115 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-115 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Blocker > Fix For: Q3Y7 > > > Overall tracking issue for *major* clustering features/fixes to be included in JBoss AS 5.0.0. > There will of course be numerous minor issues; please track those with a filter on the issues in the JBAS project. -- 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] Closed: (JBCLUSTER-95) JBento benchmark results

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-95?page=all ] Brian Stansberry closed JBCLUSTER-95. ------------------------------------- Fix Version/s: Q2Y6 (was: Q3Y6) Resolution: Done I'm closing this based on the JBento presentation given at JavaOne in May 2006. Further benchmarking work should go in a separate issue. > JBento benchmark results > ------------------------ > > Key: JBCLUSTER-95 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-95 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: Q2Y6 > > > This sub-task is track the results the progress of JBento and related project work in Japan. Previously, we have done it under the bigger umbrella. -- 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: (JBAS-4165) Add configurable TTL for HA-JNDI multicast discovery

by Brian Stansberry (JIRA)

Add configurable TTL for HA-JNDI multicast discovery ---------------------------------------------------- Key: JBAS-4165 URL: http://jira.jboss.com/jira/browse/JBAS-4165 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Naming Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.1.CR1 New property jnp.discoveryTTL, used to limit the TTL of the discovery packet sent out to the cluster. Further mechanism to limit possibility of cross-cluster contamination. Particularly useful in dev and QA-type environments where jnp.partitionName, jnp.discoveryGroup and jnp.discoveryPort don't suffice. -- 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

[JBoss JIRA] Created: (JBAS-4221) Wrong start and create notification order in EARDeployer

by pgervais (JIRA)

Wrong start and create notification order in EARDeployer -------------------------------------------------------- Key: JBAS-4221 URL: http://jira.jboss.com/jira/browse/JBAS-4221 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.5.GA Environment: Java version: 1.5.0_10,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Server VM 1.5.0_10-b03,Sun Microsystems Inc. OS-System: Windows 2000 5.0,x86 Reporter: pgervais Assigned To: Dimitris Andreadis In the org.jboss.deployment.SubDeployer file the documentation on the different notification types says that all the notifications are emitted when the event has been completed, e.g: when a sub deployment has been started (not starting) In the org.jboss.deployment.EARDeployer file, the call to super.start and super.create is called at the beginning of the start and create method, the call to super should be done at the end, when the deployement has been created and when it has been started. The code is ok for the init, stop and destroy methods. I also verified the calling order in the EJBDeployer, EJB3Deployer and AbstractWebContainer and they are as specified in the SubDeployer. -- 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: (JBAOP-375) AOPClassLoaderContainer is not using the correct class loader for JAXB Deployer

by Weston Price (JIRA)

AOPClassLoaderContainer is not using the correct class loader for JAXB Deployer ------------------------------------------------------------------------------- Key: JBAOP-375 URL: http://jira.jboss.com/jira/browse/JBAOP-375 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha3 Reporter: Weston Price Attachments: jaxb-trace JBoss MC 2.0.0Beta3 provides a JAXB Deployer. In attempting to extend this deployer, I am getting stack trace attached to this case. It appear that the wrong classloader is being used. Note, the forum reference contains the information but you don't have to read the whole thing, just the last portion particular to JAXB. -- 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

[JBoss JIRA] Created: (JBSER-94) Revalidate performance

by Clebert Suconic (JIRA)

Revalidate performance ---------------------- Key: JBSER-94 URL: http://jira.jboss.com/jira/browse/JBSER-94 Project: JBoss Serialization Issue Type: Task Affects Versions: 1.0.3 GA Reporter: Clebert Suconic Assigned To: Clebert Suconic http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jboss/JBossCache/tests/functio... -- 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: (JBCACHE-407) Write locks not acquired on newly created empty nodes

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-407?page=all ] Manik Surtani updated JBCACHE-407: ---------------------------------- Workaround Description: Set "LockParentForChildInsertRemove" to true (available in 1.4.1.SPx onwards) Fix Version/s: 2.1.0.GA (was: 2.0.0.GA) Affects Version/s: 1.4.1.GA 1.4.0.GA 1.3.0.GA 2.0.0.GA Complexity: Medium Workaround: [Workaround Exists] Moving to 2.1.0 since we have a workaround > Write locks not acquired on newly created empty nodes > ----------------------------------------------------- > > Key: JBCACHE-407 > URL: http://jira.jboss.com/jira/browse/JBCACHE-407 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.4.1.GA, 1.4.0.GA, 1.3.0.GA, 2.0.0.GA > Reporter: Brian Stansberry > Assigned To: Manik Surtani > Fix For: 2.1.0.GA > > > When an empty node is created during a put (e.g node "/a" created as a result of a cache.put("/a/1", "key", "value"); call), only a read lock is acquired on the empty node. If the node is created as part of a transaction, the following failure can occur: > 2 threads, empty cache, READ_COMMITTED > 1) T1 starts a tx > 2) T1 invokes cache.put("/a/1", "key", "value1"); > 3) T2 invokes cache.put("/a/2", "key", "value2"); > 4) T1's transaction rolls back > 5) T2 invokes cache.get("/a/2", "key"); Should get "value2", will get null because the tx rollback will remove node /a and thus /a/2 as well. > This IMO breaks READ_COMMITTED semantics, as T2 is able to "read" /a (in the sense of seeing it exists and thus can have children appended to it) before the tx that created /a is committed. > New unit test IsolationLevelReadCommittedTest.testNodeCreationRollback() demonstrates the issue. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007