This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 155886 - Undeployment doesn't cleanup the portlet war file from glassfish's autodeploy dir.
Summary: Undeployment doesn't cleanup the portlet war file from glassfish's autodeploy...
Status: RESOLVED FIXED
Alias: None
Product: contrib
Classification: Unclassified
Component: Portalpack (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ chetansanth
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-20 15:13 UTC by Satyaranjan D
Modified: 2009-11-07 10:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Satyaranjan D 2008-12-20 15:13:28 UTC 
Steps :
- Create a portlet application (Test) in NB
- Deploy that applcation from NB
- Then undeploy the same application
- Now go to glassfish/domains/domain1/autodeploy directory
- You can still see the war file (Test.war) there.
Comment 1 Satyaranjan D 2008-12-22 11:38:17 UTC 
Assigned to Chetan.
Comment 2 _ chetansanth 2008-12-23 05:16:15 UTC 
Using appserver command to undeploy application is leaving the portlet-app war file uncleaned. In case of glassfish
removing this file from autodeploy folder will result in appserver throwing the following error:

[#|2008-12-23T10:14:26.859+0530|INFO|sun-appserver2.1|javax.enterprise.system.stream.out|_ThreadID=21;_ThreadName=httpWorkerThread-4848-4;|
SharedSecrets.getJavaNetAccess()=java.net.URLClassLoader$7@8bec23|#]

[#|2008-12-23T10:37:27.421+0530|INFO|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-64;|Autoundeploying
application :WebApplication2|#]

[#|2008-12-23T10:37:27.421+0530|WARNING|sun-appserver2.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=Timer-64;_RequestID=798d5ba3-35a5-4234-a6f3-0336d71ec2c4;|ADM1024:Undeployment
failed - Detailed Message:
com.sun.enterprise.admin.common.exception.DeploymentException: Component not registered
        at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.getRegisteredType(ApplicationsConfigMBean.java:2611)
        at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.undeploy(ApplicationsConfigMBean.java:626)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
        at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
        at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
        at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
        at $Proxy1.invoke(Unknown Source)
        at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
        at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
        at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeUndeploymentService(AutoDeployer.java:903)
        at com.sun.enterprise.deployment.autodeploy.AutoDeployer.undeployJavaEEArchive(AutoDeployer.java:399)
        at com.sun.enterprise.deployment.autodeploy.AutoDeployer.undeployApplication(AutoDeployer.java:381)
        at com.sun.enterprise.deployment.autodeploy.AutoDeployer.undeployAll(AutoDeployer.java:315)
        at
com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:375)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
|#]

[#|2008-12-23T10:37:27.421+0530|SEVERE|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-64;Component
not registered
;_RequestID=798d5ba3-35a5-4234-a6f3-0336d71ec2c4;|"DPL8011: autodeployment failure while deploying the application :
Component not registered
"|#]

[#|2008-12-23T10:37:27.421+0530|INFO|sun-appserver2.1|javax.enterprise.system.tools.deployment|_ThreadID=17;_ThreadName=Timer-64;|[AutoDeploy]
Autoundeploy failed :
E:\work\websynergy\liferay\bundles\glassfish_latest\glassfish\domains\domain1\autodeploy\WebApplication2.war.|#]
Comment 3 Satyaranjan D 2008-12-30 06:31:23 UTC 
Fix:

- Instead of using hot deploy feature of websynergy, now the hot deployment is used only for massaging of the war. The
context xml file is copied to the websynergy's autodeploy directory specifying the extracted directory for the war.
- WebSynergy then tries to massage that directory.
- After massaging, the plug-in creates the war and deploys that war on glassfish.

So that no war file is being copied to the glassfish's autodeploy directory.