covers this issue
As a temp solution you can put
rem Enable the VFS NoCopyNestedJarHandler
set JAVA_OPTS=%JAVA_OPTS% -Djboss.vfs.forceNoCopy=true
into your run.bat, if you like.
Actually that temp solution is for all those nestedjar* that remain in your temp directory after shutting the server down.
Yes, the system property is the solution. I thought the system property was added by default in Beta4. Apparently not....
Yes, for a brief moment of time, it was automatically there, but then poof, it disappeared. :)
Dimitris removed it because it was causing the cts config to fail to startup. We need to revisit restoring it.
IMO the vfs code needs a change to make forced copying on demand, rather than the converse that is being performed here (by adding the system property to not do copy by default). Probably the right approach for GA.
AS5Beta4 is increasingly creating temporary files under /tmp (5 files every 30 seconds). This issue has got something to do with the profile service, as it is for bootstrap-repo profile.
JBoss Security Team has been running AS5Beta4 on a server. So after 16 hours or so (when there was no interaction/activity), the /tmp folder reached 55GB. So the AS instance had to be brought down.
The /tmp folder has files with pattern nestedjar*:
Ok, I did not know it was increasing without bound when the profile service is enabled. I created this issue for it.
One issue is that we are too aggressively creating the entire JarHandler structure. All the profile service is doing is asking the deploy directory VirtualFile for its children. It does nother with these other than ask for the last modified time.
Either lazily initializing the JarHandler or/and tracking previously extracted jars would fix the excessive creation of tmp jars.
I've enabled jboss.vfs.forceNoCopy=true by default (if not specified) in AS trunk, so that should solve the tmp file problem now. The CTS config seems happy with the change, too.
Going forward (for GA), we may consider making the vfs NoCopy behaviour the default, and use a different flag to explicitly enable it.