File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JBoss/WildFly and the fly likes jboss 7 how to cleanup standalone.xml.tmp.* Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "jboss 7 how to cleanup standalone.xml.tmp.*" Watch "jboss 7 how to cleanup standalone.xml.tmp.*" New topic

jboss 7 how to cleanup standalone.xml.tmp.*

Andy Iyerr

Joined: Sep 03, 2013
Posts: 2
We just upgraded rom jboss 4 to jboss 7. Everything seems fine other than standalone.xml.tmp.* (standalone.xml.tmp.KZ8YyItCh, standalone.xml.tmp.qftC6Feuk etc) being generated in the /opt/jboss/<appname>/deployments/ folder. What are these files, and can they be deleted or is there a setting to disable them from being generated.

Francesco Marchioni
Ranch Hand

Joined: Sep 22, 2003
Posts: 194
Hi Andy,
it's quite odd that you have .tmp configuration files in your deployments folder. Which release of JBoss are you using ? by default the configuration is only stored in the "configuration" folder and the application server does not keep tmp files of it but rather an history of older configurations and your self-made snapshots. These are persisted in standalone_xml_history and the application server cares about rolling them on a time basis. You should not be concerned about this files, as they won't be used at all by the application server, yet if you provide some more details we can guess why you have those files in the deployments folder.

Enterprise Integration Tutorials - JBoss-WildFly Tutorials
I agree. Here's the link:
subject: jboss 7 how to cleanup standalone.xml.tmp.*
It's not a secret anymore!