问题
We are using Worklight's automated ANT task to deploy a Worklight application. Unfortunately, it's currently failing with this error message:
BUILD FAILED
/deployment/jenkins/jobs/UAT-uat2-Deploy/workspace/co.uk.homebase.strategic-app/Homebase/ciBuild/buildAndDeployAnt.xml:171: The following error occurred while executing this line:
/deployment/jenkins/jobs/UAT-uat2-Deploy/workspace/co.uk.homebase.strategic-app/Homebase/ciBuild/buildAndDeployAnt.xml:186: app-deployer failed:SEVERE:Bad Request; Error 400: java.lang.RuntimeException: java.io.IOException: There is not enough space in the file system.
Unfortunately, the error message isn't precise about which filesystem is out of space. On this system, there are several filesystem which might be relevant, including /tmp, the Liberty server install filesystem (our Worklight server is running on WebSphere Liberty), and a separate filesystem for the Worklight logs.
Is there any way we can discover which filesystem is being referred to? None of them appear to be significantly low on space, although the /tmp filesystem is quite small, so that's my suspicion. If that's the case, is there a way to configure to use a different filesystem for temporary files?
回答1:
In our case, we discovered that the filesystem that was out-of-space was on the target system where we were trying to deploy a .wlapp file. Doubling the size of /tmp (this was an AIX box) fixed the issue.
来源：https://stackoverflow.com/questions/23755777/how-can-i-tell-which-filesystem-worklights-app-deployer-is-referring-to