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.
Eric View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867358#3867358 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867358 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
