May 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCLUSTER-26) Clustered deployments should be atomic

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/browse/JBCLUSTER-26?page=com.atlassian.jira.plugin... ] Brian Stansberry updated JBCLUSTER-26: -------------------------------------- Fix Version/s: Legacy (was: Q2Y8) Moving issues not directly related to code developed in https://svn.jboss.org/repos/jbossas/projects/cluster to "Legacy" Fix Version. > Clustered deployments should be atomic > -------------------------------------- > > Key: JBCLUSTER-26 > URL: https://jira.jboss.org/browse/JBCLUSTER-26 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assignee: Brian Stansberry > Priority: Critical > Fix For: Legacy > > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > Our current farm deployment is not automic, meaning that one cluster node failed, it won't rollback the rest within the cluster. > One soultion is make the deployer XA resource so they can participate in sort of 2 phase commit. > This can potentially be applied to MBean clustering as well. > In addition, farming service has couple bugs outstanding. It needs an overhaul as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-23) Consolidate clustering configuration frontend for state replication

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/browse/JBCLUSTER-23?page=com.atlassian.jira.plugin... ] Brian Stansberry updated JBCLUSTER-23: -------------------------------------- Fix Version/s: Legacy (was: Q2Y8) Moving issues not directly related to code developed in https://svn.jboss.org/repos/jbossas/projects/cluster to "Legacy" Fix Version. > Consolidate clustering configuration frontend for state replication > ------------------------------------------------------------------- > > Key: JBCLUSTER-23 > URL: https://jira.jboss.org/browse/JBCLUSTER-23 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assignee: Brian Stansberry > Priority: Critical > Fix For: Legacy > > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > Currently we have cluster-service.xml, tc5-cluster-serviec.xml, and other tree-cache.xml to run on tops of JGroups for various replication and clustering purpose. In ejb3, we will run into this problem of SFSB and entity bean using JBossCache. > There comes a need to consolidate all these configuration so to a end user it is consistent. > Solution may be to put in another integration layer to hide JBossCache configuration somewhat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-11) Unified clustering configuration and management

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/browse/JBCLUSTER-11?page=com.atlassian.jira.plugin... ] Brian Stansberry updated JBCLUSTER-11: -------------------------------------- Fix Version/s: Legacy (was: Q2Y8) Moving issues not directly related to code developed in https://svn.jboss.org/repos/jbossas/projects/cluster to "Legacy" Fix Version. > Unified clustering configuration and management > ----------------------------------------------- > > Key: JBCLUSTER-11 > URL: https://jira.jboss.org/browse/JBCLUSTER-11 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assignee: Brian Stansberry > Priority: Blocker > Fix For: Legacy > > Original Estimate: 12 weeks > Remaining Estimate: 12 weeks > > Will need a more unified management frontend for the new clustering: > 1. Unified JGroups MBean to configure the channel running inside the JBoss AS. > 2. Unified JBossCache configuration to select cache instance used for http session, SFSB, entity, and others. > 3. Unified clustering web console. > This issue is a duplicate of JBAS-2960. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/browse/JBCLUSTER-117?page=com.atlassian.jira.plugi... ] Brian Stansberry updated JBCLUSTER-117: --------------------------------------- Affects Version/s: Legacy Moving issues not directly related to code developed in https://svn.jboss.org/repos/jbossas/projects/cluster to "Legacy" Fix Version. > Clustered deployments using the Profile Service > ----------------------------------------------- > > Key: JBCLUSTER-117 > URL: https://jira.jboss.org/browse/JBCLUSTER-117 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: Legacy > > > 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: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/browse/JBCLUSTER-117?page=com.atlassian.jira.plugi... ] Brian Stansberry updated JBCLUSTER-117: --------------------------------------- Fix Version/s: Legacy (was: Q2Y8) Affects Version/s: (was: Legacy) > Clustered deployments using the Profile Service > ----------------------------------------------- > > Key: JBCLUSTER-117 > URL: https://jira.jboss.org/browse/JBCLUSTER-117 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: Legacy > > > 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: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7834) XMLs contained by archives are parsed aggressively by deployers, resulting in unexpected errors

by Marius Bogoevici (JIRA)

XMLs contained by archives are parsed aggressively by deployers, resulting in unexpected errors ----------------------------------------------------------------------------------------------- Key: JBAS-7834 URL: https://jira.jboss.org/jira/browse/JBAS-7834 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Reporter: Marius Bogoevici Assignee: Ales Justin Take a working application (like a very basic war) and add a file ending in -hibernate.xml (e.g. /WEB-INF/application-hibernate.xml) which references a schema which is unknown to the Hibernate Deployer (or no schema). A simple file containing this: <broken/> would do. >From this point on, the application will fail deploying consistently. Unfortunately, application-hibernate.xml is not a reserved file name under JavaEE, so a valid application may contain such files and fail to deploy. In such cases, the application server should be more lenient and ignore those files. Note 1: the problem may appear for other suffixes. Note 2: the problem has been sporadically noticed in the Spring world, but it's not necessarily a Spring-related issue (heavy usage of XML in Spring may trigger the problem more consistently). -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-233) Let's break relative order or deployer name ordering backward compatibility

by Richard Opalka (JIRA)

Let's break relative order or deployer name ordering backward compatibility --------------------------------------------------------------------------- Key: JBDEPLOY-233 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-233 Project: JBoss Deployers Issue Type: Feature Request Affects Versions: JBDEPLOY-2.0.8.SP1 Reporter: Richard Opalka Fix For: JBDEPLOY-2.0.9.GA, JBDEPLOY-2.1.0.Alpha1 There is a requirement to implement deployers comparison if they are "equivalent". This requirement is because of BC and should be removed ASAP IMHO. Here are the top two reasons why it should be removed: * it breaks topological ordering algorithm linear complexity * deployers should define their order using inputs/outputs only and shouldn't rely on relative order or deployer name ordering I suggest to remove this ordering from our algorithms and then fix particular deployers in AS trunk, that would fail because of wrong ordering. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBREFLECT-88) ValueConvertor.convertValue() always fails for the static valueOf(Object) methods

by Kabir Khan (JIRA)

ValueConvertor.convertValue() always fails for the static valueOf(Object) methods --------------------------------------------------------------------------------- Key: JBREFLECT-88 URL: https://jira.jboss.org/jira/browse/JBREFLECT-88 Project: JBoss Reflection Issue Type: Bug Affects Versions: JBossReflection.2.2.0-Alpha1 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossReflection.2.2.0-Beta The call to ReflectionUtils has the Method and Target parameters swapped around -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8004) Upgrade to JBoss Cache 3.2.5.GA

by Brian Stansberry (JIRA)

Upgrade to JBoss Cache 3.2.5.GA ------------------------------- Key: JBAS-8004 URL: https://jira.jboss.org/jira/browse/JBAS-8004 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 6.0.0.CR1 Note that this may be superseded by JBAS-7837 (move to infinispan) in which case I'll close this JIRA as out of date. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8003) Upgrade to ha-server-cache-jbc 2.2.1.Final

by Brian Stansberry (JIRA)

Upgrade to ha-server-cache-jbc 2.2.1.Final ------------------------------------------ Key: JBAS-8003 URL: https://jira.jboss.org/jira/browse/JBAS-8003 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 6.0.0.CR1 Note that this may be superseded by JBAS-7837 (move to infinispan) in which case I'll close this JIRA as out of date. -- 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, 1 month

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2010