[GLASSFISH-19162] Loader_<xxx> directories in generated/jsp application folders are not deleted after server shutdown Created: 16/Oct/12  Updated: 20/Dec/16  Resolved: 16/Oct/12

Status: Resolved
Project: glassfish
Component/s: deployment
Affects Version/s: 3.1.2
Fix Version/s: 4.0_dev

Type: Bug Priority: Major
Reporter: kksineric_hotmail Assignee: Hong Zhang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Issue Links:
is related to GLASSFISH-11483 Admin GUI "Disk Space Memory Leak" (G... Resolved


This is basically the same issue that was reported in http://java.net/jira/browse/GLASSFISH-11483. It can be duplicated using the test.war file attached in that issue. Though it was flagged as resolved but I'm seeing the same bug occurring again in the latest stable release (

Comment by Hong Zhang [ 16/Oct/12 ]

Yes, I was able to reproduce this issue in This seems to be a regression in 3.1.* code base. The classloader (and related directories) was cleaned up at a later stage of the lifecycle, but that stage was not invoked as part of the server shutdown.

This issue was already fixed in GlassFish 4.0 (the classloader cleanup is now happening as part of the server shutdown).

Comment by Hong Zhang [ 16/Oct/12 ]

(Accidentally removed the affected version, put it back)

Comment by kksineric_hotmail [ 17/Oct/12 ]

Thanks for verifying the issue. Do you have an estimate on when a stable release for Glassfish 4 will be out?

Comment by Hong Zhang [ 17/Oct/12 ]

The official GlassFish 4.0 release is targeted for Q2 of 2013:

But you can get the weekly promoted builds here:

Comment by luisjotapepe [ 13/Mar/13 ]

Hello guys. I am currently using GlassFish Server Open Source Edition (build 5). My problem is that this is already in Prod environment and we just noticed this. It is happening for domain and clusters across all nodes ie: /usr/local/glassfish3/glassfish/nodes/localhost-domain1/<clustername>/generated/jsp/

What is safe to delete from here? and what not?

Kindly appreciate your help

Comment by kksineric_hotmail [ 14/Mar/13 ]

As a workaround, we added the code below to the "asadmin" batch file, right before 'exec "$JAVA" -jar "$AS_INSTALL_LIB/admin-cli.jar" "$@"'. This will remove the generated folder upon startup.

if [ "$1" = "start-domain" ]; then
echo "Removing generated folder..."
rm -rf ../domains/domain1/generated
sleep 2

Generated at Mon Feb 27 15:56:04 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.