Unpacked deployments are not copied. You can also set a jboss.deploy.localcopy=false system property to prevent the copying.
Thanks for the reply, Scott. I have modified run.conf to include "-Djboss.deploy.localcopy=false" in the JAVA_OPTS variable. However, I'm still seeing temp files created under tmp/deploy/, along with the corresponding message "Attaching Java program to <jboss install>/server/default/tmp/deploy/tmp99999xxx.jar", which indicates that this is a new jar. I have also tried passing the -D param to run.sh on the command line and (grasping at straws) added it to properties-service.xml, all to no effect. If I missed something, could you please clarify? If this is a bug, I'll be happy to enter an issue into JIRA.
Ok, it appears that the system property is getting overriden by the xmbean configuration in 4.0.x, so you need to edit the conf/xmdesc/org.jboss.deployment.MainDeployer-xmbean.xml descriptor and set the CopyFiles value to false:
<attribute access='read-write' setMethod='setCopyFiles' getMethod='getCopyFiles'> <description></description> <name>CopyFiles</name> <type>boolean</type> <descriptors> <value value="false"/> </descriptors> </attribute>
After this, there will still be some rars that are getting copied when they should not, but its a fraction of what was copied before:
[starksm@banshee9100 tmp]$ ls -R .: aopdynclasses/ deploy/ ./aopdynclasses: ./deploy: deploy/ ./deploy/deploy: jboss-local-jdbc.rar-contents/ jms/ jboss-xa-jdbc.rar-contents/ mail-ra.rar-contents/ ./deploy/deploy/jboss-local-jdbc.rar-contents: jboss-local-jdbc.jar* ./deploy/deploy/jboss-xa-jdbc.rar-contents: jboss-xa-jdbc.jar* ./deploy/deploy/jms: jms-ra.rar-contents/ ./deploy/deploy/jms/jms-ra.rar-contents: jms-ra.jar* ./deploy/deploy/mail-ra.rar-contents: mail-ra.jar*
I created a jira entry for the rar copying that is still ocurring:
Great! That cut my startup time from 2:30 (best case) to 40 seconds. Thanks!