[jboss-jira] [JBoss JIRA] (WFLY-5362) Wildfly 9.0.1 Final fails next day with WFLYDS0032: Failed to list files in directory

[George Leon (JIRA)]

George Leon created WFLY-5362:
---------------------------------

             Summary:  Wildfly 9.0.1 Final fails  next day  with WFLYDS0032: Failed to list files in directory
                 Key: WFLY-5362
                 URL: https://issues.jboss.org/browse/WFLY-5362
             Project: WildFly
          Issue Type: Bug
         Environment: Wildfly 9.0.1 Final
            Reporter: George Leon
            Assignee: Jason Greene


Hi  all,

First Wildlfly is the best  Bravo  from Greece .

 

 

We have  wildfly 9.0.1 Final    installed    as  root   and all folders are  owner root  

we deployed our  web app (war) via the Web UI administration   everything  works  for several hours  the next day   we come to work  and  Wildlfly  fails   with error below   any help is very welcome

 

ls          /opt/wildfly-9.0.1.Final/standalone/deployments

drwxr-xr-x. 3 root root 4096 Sep 16 14:24 configuration

drwxr-xr-x. 8 root root 4096 Sep 10 11:20 data

drwxr-xr-x. 2 root root   23 Jul 23 21:01 deployments

drwxr-xr-x. 3 root root   16 Jul 23 21:01 lib

drwxr-xr-x. 2 root root 4096 Sep 18 00:00 log

drwxr-xr-x. 7 root root   94 Sep 16 14:24 tmp

 

 

2015-09-18 10:02:41,735 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0012: Scan of /opt/wildfly-9.0.1.Final/standalone/deployments threw Exception: java.lang.RuntimeException: WFLYDS0032: Failed to list files in directory /opt/wildfly-9.0.1.Final/standalone/deployments. Check that the contents of the directory are readable.

    at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.listDirectoryChildren(FileSystemDeploymentService.java:1170)

    at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scanDirectory(FileSystemDeploymentService.java:664)

    at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:474)

    at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.scan(FileSystemDeploymentService.java:393)

    at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentScanRunnable.run(FileSystemDeploymentService.java:161)

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

    at java.lang.Thread.run(Thread.java:745)

    at org.jboss.threads.JBossThread.run(JBossThread.java:320)

 

 

Thanks 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)