I have the following error when deploying an application with JBoss Tools in Eclipse:
Error renaming C:\wildfly-8.1.0.Final\standalone\tmp\tmp7858611943756287857.xhtml to C:\wildfly-8.1.0.Final\standalone\deployments\.war\403.xhtml.
This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
You may adjust these settings in the server editor.
And here is a screenshot of the error:
On the documentation, I found this:
You can customize the deployment location and packaging type:
- To select the workspace deployment folder for the server, click Use workspace metadata.
- To select the deployment folder of the application server, click Use the JBoss deploy folder.
- To select a folder of your choice, click Use a custom deploy folder. With this option, complete the Deploy directories and Temporary Deploy Directory fields. The temporary folder must be on the same file system as the final deploy location otherwise publishing often fails.
- For all modules to be archived for deployment, select the Deploy projects as compressed archives check box. This avoids exploded deployments and reduces the amount of memory deployments occupy but may result in slower deployment.
What does The temporary folder must be on the same file system as the final deploy location mean? How can I solve it?
I've realized that the error doesn't occur when the check box Deploy projects as compressed archives is checked.
I solved this problem following the steps below:
- Restarted the computer
- Deleted the project files from the folder "standalone\deployments"
- Deleted all files in the folder "standalone\tmp"
- Clean project in Eclipse
- In Eclipse, removed project from Wildfly and then added again
- In Eclipse, right click on "Wildfly" and then "Clean..."
- In Eclipse, right click on the project module and then "Full publish"
I get this error right after I updated a dependency in my pom.xml and tried to republish.
The thing that worked was to uncheck the setting in the server deployment for "Deploy projects as compressed archives"
I had the same problem and the only solution after hours looking for in google, I solved closing eclipse, deleting the folder ".metadata" of the workspace restarting eclipse and creating the server of JBoss AS 6.x again and deploying again and everything worked for me correctly. I hope this help.
The hermeslm solution fixes most (if not all) problems with workspace, but it is final and robust weapon of choice. Be advised that if you have highly configured eclipse (custom code assist, formatting definitions, plugins config, UI look) you'll lose it all. You'll have to import all projects and configure it all over again.
I had the same problem but from time to time I do full workspace file-system backup and restore from it when such crap happens.
From what I have observed on backup restore so far, this particular problem may be in configuration jboss server in eclipse and files/plugins related to it. In other words if you don't have backups, try deleting and rebuilding your servers definition in eclipse before you'll delete .metadata dir.
If you go to file --> C:\Users\yourusername\wildfly-10.0.0.CR4\standalone\deployments and delete your projectname.war file, server should be able to restart.
I was getting the same error message, turns out it was because something went wrong in the deployments folder of JBoss, it wasn't even allowing me to delete my project ear folder from deployments.
My solution was, unzipped another instance of JBoss and pointed my Eclipse to this JBoss and then it worked fine.
I've had the same problem. Files of the .metadata and .recommenders workspace folders were corrupted. I took those folders from a colleague and replaced mine. It worked!
I had the same problem several times in my windows 10 machine. Since I did not have admin rights it was a hectic process to troubleshoot this issue. Simple fix would be moving JBOSS_HOME closer to root. However, you need to do a proper restart of your eclipse. I rather recommend a complete restart of your computer because after all you are going to change JBOSS_HOME in windows environmental variables.
rather old...but still takes place in NEON version of eclipse and Wildfly. and the problem is that Eclipse didn't stop normally the webserver. (Something very usual for Tomcat at least I do most of the work) Solution: I opened the "Debug" presentation. I killed the process. ( and cleaned-cleared the Server - just in case).
来源：https://stackoverflow.com/questions/26487574/jboss-tools-deploy-error-this-may-be-caused-by-your-servers-temporary-deploy-d