July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5745) ServerMBean.InShutdown flag won't turn on when the shutdown hook is called directly

by Takayoshi Kimura (JIRA)

ServerMBean.InShutdown flag won't turn on when the shutdown hook is called directly ----------------------------------------------------------------------------------- Key: JBAS-5745 URL: http://jira.jboss.com/jira/browse/JBAS-5745 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-5.0.0.CR1, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Takayoshi Kimura Assigned To: Dimitris Andreadis The ServerMBean.InShutdown flag is only turned on when the shutdown() operation is called. There is another shutdown path, a shutdown hook called by signals including Ctrl+c. This flag is needed to update in the shutdownHook.shutdown() method to reflect the sever status. -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6588) Move to HASingletonProfileActivator

by Brian Stansberry (JIRA)

Move to HASingletonProfileActivator ----------------------------------- Key: JBAS-6588 URL: https://jira.jboss.org/jira/browse/JBAS-6588 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 When the profile service moves to XML-based configuration, switch deploy-hasingleton to a subprofile that gets created at bootstrap but not activated. Differs from 5.1 impl which creates the subprofile when HASingletonProfileManager is deployed. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6355) ServiceBindingManager docs

by Brian Stansberry (JIRA)

ServiceBindingManager docs -------------------------- Key: JBAS-6355 URL: https://jira.jboss.org/jira/browse/JBAS-6355 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 -- 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

15 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-5554) Cross-cluster dependencies

by Brian Stansberry (JIRA)

Cross-cluster dependencies -------------------------- Key: JBAS-5554 URL: http://jira.jboss.com/jira/browse/JBAS-5554 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Deployers Reporter: Brian Stansberry Assigned To: Brian Stansberry Service B on node 2 depends on Service A on node 1. Per Scott, "Dependencies on components that are marked as @Clustered needs a cluster aware dependency implementation. Custom dependencies are supported by the mc, but the component deployers generating the component metadata have to generate the correct dependency implementation." This also ties in with the coordinated deployment issue in JBAS-5553, as we wouldn't want Service B deployment to fail on node 2 just because it happened to deploy before Service A on node 1. -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5550) Clustered deployments using the ProfileService

by Brian Stansberry (JIRA)

Clustered deployments using the ProfileService ---------------------------------------------- Key: JBAS-5550 URL: http://jira.jboss.com/jira/browse/JBAS-5550 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, ProfileService Reporter: Brian Stansberry Assigned To: Brian Stansberry Container task for work on bringing clustered deployments to the full ProfileService. Some of the subtasks will be for AS 5.0.0; others for later. See the forum reference as well as an earlier discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=63437 -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5553) Coordinated cluster-wide deployment into the runtime

by Brian Stansberry (JIRA)

Coordinated cluster-wide deployment into the runtime ---------------------------------------------------- Key: JBAS-5553 URL: http://jira.jboss.com/jira/browse/JBAS-5553 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, ProfileService Reporter: Brian Stansberry Assigned To: Brian Stansberry Once deployment repository content is synchronized across a cluster, need to add the ability to do staged deployments of updated content into the runtime. -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5555) Rationalize clustering metadata

by Brian Stansberry (JIRA)

Rationalize clustering metadata ------------------------------- Key: JBAS-5555 URL: http://jira.jboss.com/jira/browse/JBAS-5555 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Deployers Reporter: Brian Stansberry Assigned To: Brian Stansberry Clustering metadata is scattered in different metadata objects. Need to rationalize, particularly to support adding clustering aspects to non-JEE beans. -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5551) Provide cluster topology info to the DeploymentManager impl

by Brian Stansberry (JIRA)

Provide cluster topology info to the DeploymentManager impl ----------------------------------------------------------- Key: JBAS-5551 URL: http://jira.jboss.com/jira/browse/JBAS-5551 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, ProfileService Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 DeploymentManager operations create a list of DeploymentTargets. Currently this list only includes the local node. Need to integrate cluster topology information so it can include one DeploymentTarget per node in the cluster (at least if the relevant DeploymentPhase is APPLICATION_CLUSTERED.) -- 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

15 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-6933) Review HA design to inlcude Mobicents more easily

by jean deruelle (JIRA)

Review HA design to inlcude Mobicents more easily ------------------------------------------------- Key: JBAS-6933 URL: https://jira.jboss.org/jira/browse/JBAS-6933 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.CR1 Reporter: jean deruelle Assignee: Brian Stansberry Priority: Minor Change the clustering design to allow for extensibility without so much protected methods as per the JBoss Fourm thread http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231472#4231472 -- 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

15 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1728) Create a JTA profile for use in unit tests

by Carlo de Wolf (JIRA)

Create a JTA profile for use in unit tests ------------------------------------------ Key: EJBTHREE-1728 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1728 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

15 years, 8 months

1
1
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 July 2009