Bug 981743 - If the hotdeployment is disabled, we shouldn't need to have write access to the deployment folder.
If the hotdeployment is disabled, we shouldn't need to have write access to t...
Status: CLOSED NOTABUG
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: unspecified (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Anne-Louise Tangring
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-05 12:47 EDT by Chaitanya Pothineni
Modified: 2013-07-05 14:11 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-05 14:11:10 EDT
Type: Enhancement
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chaitanya Pothineni 2013-07-05 12:47:05 EDT
Description of problem:

In one of the customer sites, the deploy directory is owned by a user who only does code deployment and another team which just manages the Jboss Server. The team which manages the server doesn't have write access to the deployment folder. 
They want to just deploy the apps at server boot time. They choose to set the hd-scanner scan interval to "0" or negative value to establish this, but in 6.1 we do not allow server to startup without write access to the deployment folder. In this case hot deployment is completely turned off by setting auto-deploy-*=false.

Using CLI or management console doesn't seem to be an option.

Need a way to deploy during startup, when there is no write access to deployment folder.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.the deploy directory is owned by a user who only does code deployment and another team which just manages the Jboss Server. The team which manages the server doesn't have write access to the deployment folder. 

2.set deployment scanner with options like this :
"auto-deploy-exploded" => false,
"auto-deploy-xml" => false,
"auto-deploy-zipped" => false,
"deployment-timeout" => 600,
"path" => "deployments",
"relative-to" => "jboss.server.base.dir",
"scan-enabled" => true,
"scan-interval" => 0

3.Now try to start the server.

Actual results:

Server fails with 

ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([
    ("subsystem" => "deployment-scanner"),
    ("scanner" => "default")
]): java.lang.IllegalArgumentException: JBAS015054: [JBOSS_EAP_HOME]/standalone/deployments is not writable
	at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.<init>(FileSystemDeploymentService.java:171)
	at org.jboss.as.server.deployment.scanner.DeploymentScannerAdd.execute(DeploymentScannerAdd.java:118)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:313) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-2.jar:2.0.0.GA-redhat-2]

11:41:54,232 ERROR [org.jboss.as.controller.management-operation] JBAS014784: Failed executing subsystem deployment-scanner boot operations

Expected results:

Server starts and deploys with out any problem.
Additional info:
Comment 1 Chaitanya Pothineni 2013-07-05 14:11:10 EDT
closing this BZ as we created a product management JIRA for enhancement

https://issues.jboss.org/browse/PRODMGT-484

Note You need to log in before you can comment on or make changes to this bug.