dev@glassfish.java.net

[gf-dev] Some questions according to the deployment

From: Lv, Songping <lvsongping_at_cn.fujitsu.com>
Date: Tue, 23 Sep 2014 09:55:51 +0000

Hi, Hong:
Cc: glassfish team:

     I have some questions according to the issue GLASSFISH-19162 and GLASSFISH-11483 in JIRA.
     I hope if any of you can answer the questions I have list in line:
<1>. I have found the issue of GLASSFISH-19162 and GLASSFISH-11483 has been resolved since the version of 4.0_b56_ms5 and I found a tag called https://svn.java.net/svn/glassfish~svn/tags/3.1.2.2-no-delete-fix-11483-19162 , is this tag used to fix the same issue in version3.1.2.2?


<2>. If we applied the tag called https://svn.java.net/svn/glassfish~svn/tags/3.1.2.2-no-delete-fix-11483-19162, there will cause a regression in redeployment scenario. Which means it will be failed in redeployment the application as follows:
・ an ear file which contains war file
・ there's a jar file under the directory of WEB-INF/lib in war file
・ the operation target is on the cluster.
By the way, I have attached a similar ear file here so that you can reproduce this phenomenon in version 3.1.2.2 which apply the tag https://svn.java.net/svn/glassfish~svn/tags/3.1.2.2-no-delete-fix-11483-19162

So I think the tag of https://svn.java.net/svn/glassfish~svn/tags/3.1.2.2-no-delete-fix-11483-19162 may be invalid here because the solution will cause a regression here.


<3>.However, the version4.0 can't reproduce the similar problem I have list above because the issue of GLASSFISH-19898 has been resolved by jwells. But the jwell's solution will cause a Full GC here and it will cause the classloader can be recycled even if the classloader is not stopped. So I don't the this solution is a kind solution to fix the issue of GLASSFISH-19898. Maybe we can find another solution to fix the issue of GLASSFISH-19898.

<4>.I have better solution to fix the GLASSFISH-19162, GLASSFISH-11483 and GLASSFISH-19898, why not move the ApplicationInfo.clean both to the ApplicationLifecycle.unload and ApplicationLifecycle.undeploy. I think it will be a nice solution to fix all of this issues.

Thanks

Regards
Jeremy Lv
--------------------------------------------------
Lv Songping
Software Division II
    Development Department I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
        Nanjing, 210012, China
TEL  : +86+25-86630566-9327
COINS: 7998-9327
FAX  : +86+25-83317685
MAIL : lvsongping_at_cn.fujitsu.com
BLOG : https://www.java.net//author/jeremy-lv