[JBoss JIRA] (AS7-2943) Make managed servers (domain mode) store deployments in their own content repository
5:12 p.m.
Make managed servers (domain mode) store deployments in their own content repository
-------------------------------------------------------------------------------------
Key: AS7-2943
URL: https://issues.jboss.org/browse/AS7-2943
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Brian Stansberry
Priority: Blocker
Fix For: 7.1.0.Final
AS7-341 implements the removal of the deployed content in the domain
DeploymentRemoveHandler. However, since the managed servers use their HC's content
repository, if one of the servers failed removing the deployment from their model, the
content is wrongly removed from the HC repository since the error is not reported back.
Having each server maintain their own repo avoids this problem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 p.m.
[
https://issues.jboss.org/browse/AS7-2943?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-2943:
---------------------------------------
It also removes the need for the server process to have access to the HC's working
area. This opens up the possibility of configuring the server processes to run in a
separate filesystem area with different permissions from the HC process' area. If the
config then offered a mechanism for the HC to launch the servers under a different user
name, an avenue would be closed via which an attacker who compromised a server process
could affect the HC.
Make managed servers (domain mode) store deployments in their own
content repository
-------------------------------------------------------------------------------------
Key: AS7-2943
URL: https://issues.jboss.org/browse/AS7-2943
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Brian Stansberry
Priority: Blocker
Fix For: 7.1.0.Final
AS7-341 implements the removal of the deployed content in the domain
DeploymentRemoveHandler. However, since the managed servers use their HC's content
repository, if one of the servers failed removing the deployment from their model, the
content is wrongly removed from the HC repository since the error is not reported back.
Having each server maintain their own repo avoids this problem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:54 p.m.
[
https://issues.jboss.org/browse/AS7-2943?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-2943:
-------------------------------------
Assignee: Kabir Khan (was: Brian Stansberry)
Potentially this could be configurable via the host.xml <server> element; i.e.
people who want to avoid multiple copies could choose to use a shared repo. That
introduces the issue of how to GC the deployment repo though.
Make managed servers (domain mode) store deployments in their own
content repository
-------------------------------------------------------------------------------------
Key: AS7-2943
URL: https://issues.jboss.org/browse/AS7-2943
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Kabir Khan
Priority: Blocker
Fix For: 7.1.0.Final
AS7-341 implements the removal of the deployed content in the domain
DeploymentRemoveHandler. However, since the managed servers use their HC's content
repository, if one of the servers failed removing the deployment from their model, the
content is wrongly removed from the HC repository since the error is not reported back.
Having each server maintain their own repo avoids this problem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 p.m.
[
https://issues.jboss.org/browse/AS7-2943?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-2943:
---------------------------------------
Note this is only a blocker because we need to make sure the repo cleanup from AS7-341
doesn't remove content still relied upon by a server. The "separate filesystem
area" feature contemplated in my last 2 comments is not a blocker for 7.1.0.Final.
Make managed servers (domain mode) store deployments in their own
content repository
-------------------------------------------------------------------------------------
Key: AS7-2943
URL: https://issues.jboss.org/browse/AS7-2943
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Kabir Khan
Priority: Blocker
Fix For: 7.1.0.Final
AS7-341 implements the removal of the deployed content in the domain
DeploymentRemoveHandler. However, since the managed servers use their HC's content
repository, if one of the servers failed removing the deployment from their model, the
content is wrongly removed from the HC repository since the error is not reported back.
Having each server maintain their own repo avoids this problem
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4556
days inactive
4585
days old
3 comments
3 participants
participants (3)
-
Brian Stansberry (Assigned) (JIRA) -
Brian Stansberry (Commented) (JIRA)
-
Kabir Khan (Created) (JIRA)