Undeploying application

Hi All,
I have to undeploy an application from the J2ee engine.
Can anybody guide me or provide me link for undeploying application.
Regards,
Sharib

Hi Sharib
Here are all the SDM relevant logs and traces:
../SDM/program/log/.....................
Please check whether there is any update in the files under this folder.
Also please check the SDM status from MMC or the following log files:
/usr/sap/<SID>/<instance>/work/dev_sdm
/usr/sap/<SID>/<instance>/work/std_sdm.out
/usr/sap/<SID>/<instance>/work/jvm_sdm
If there is no update at all, and SDM is still showing as Running, I would like to suggest you terminate this and restart the whole engine, afterwards you can try the undeployment again.
If it still fails, there is another option to undeploy a certain applicaion via the j2ee telnet console.
Best regards,
Thunder

Similar Messages

Error on Undeploy: Application with name "crazy" does not exist.

I am working with Jdeveloper Studio Edition Version 11.1.1.6.0 Build JDEVADF_11.1.1.6.0_GENERIC_111205.1733.6192.
I have applications that run fine, however when I click on the undeploy, I get the error below. Please keep in mind that this is a simple sample application -- no security. Just one form with reading an HR schema table. Just a sample to try and figure out why I am getting this error. Any ideas?
1. I have deleted the system folder (repeatedly)
2. I deleted out my entire C:\Users\stuart\AppData\Local\Temp directory (someone mentioned this in another post)
3. Reinstalled Jdeveloper.
Thank you,
Stuart
PS, the application is called crazy because that is what this error is making me!
I have included the start of weblogic too, just in case that sheds some light on this issue.
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode)
Starting WLS with line:
C:\Jdev1116\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Jdev1116\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Jdev1116\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Jdev1116\WLSERV~1.3 -Dwls.home=C:\Jdev1116\WLSERV~1.3\server -Dweblogic.home=C:\Jdev1116\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=C:\Jdev1116\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1 -Djrockit.optfile=C:\Jdev1116\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Jdev1116\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Jdev1116\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\Users\stuart\AppData\Roaming\JDEVEL~1\SYSTEM~1.92\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Jdev1116\patch_wls1035\profiles\default\sysext_manifest_classpath;C:\Jdev1116\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<Aug 26, 2012 10:09:26 PM EDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Aug 26, 2012 10:09:26 PM EDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 26, 2012 10:09:27 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsystems Inc.>
<Aug 26, 2012 10:09:27 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Aug 26, 2012 10:09:29 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 26, 2012 10:09:29 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Aug 26, 2012 10:09:29 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Users\stuart\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<Aug 26, 2012 10:09:39 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Aug 26, 2012 10:09:45 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Aug 26, 2012 10:09:45 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 26, 2012 10:10:38 PM EDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Aug 26, 2012 10:10:38 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Aug 26, 2012 10:10:38 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Aug 26, 2012 10:10:38 PM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.1.55:7101 for protocols iiop, t3, ldap, snmp, http.>
<Aug 26, 2012 10:10:38 PM EDT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<Aug 26, 2012 10:10:38 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Aug 26, 2012 10:10:38 PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
IntegratedWebLogicServer startup time: 76287 ms.
IntegratedWebLogicServer started.
[Running application crazy on Server Instance IntegratedWebLogicServer...]
[10:10:41 PM] ---- Deployment started. ----
[10:10:41 PM] Target platform is (Weblogic 10.3).
[10:10:42 PM] Retrieving existing application information
[10:10:42 PM] Running dependency analysis...
[10:10:43 PM] Deploying 2 profiles...
[10:10:44 PM] Wrote Web Application Module to C:\Users\stuart\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\crazy\ViewControllerWebApp.war
[10:10:47 PM] Wrote Enterprise Application Module to C:\Users\stuart\AppData\Roaming\JDeveloper\system11.1.1.6.38.61.92\o.j2ee\drs\crazy
[10:10:47 PM] Deploying Application...
<Aug 26, 2012 10:10:48 PM EDT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application crazy is not versioned.>
[10:11:15 PM] Application Deployed Successfully.
[10:11:15 PM] The following URL context root(s) were defined and can be used as a starting point to test your application:
[10:11:15 PM] http://stuart-PC:7101/crazy-ViewController-context-root
[10:11:15 PM] Elapsed time for deployment: 34 seconds
[10:11:15 PM] ---- Deployment finished. ----
Run startup time: 34164 ms.
[Application crazy deployed to Server Instance IntegratedWebLogicServer]
Target URL -- http://stuart-PC:7101/crazy-ViewController-context-root/faces/main.jspx
<Aug 26, 2012 10:11:25 PM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 192.168.1.55:52,130 during the configured idle timeout of 5 secs>
<Aug 26, 2012 10:11:25 PM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 192.168.1.55:52,131 during the configured idle timeout of 5 secs>
<Aug 26, 2012 10:11:25 PM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 192.168.1.55:52,132 during the configured idle timeout of 5 secs>
<Aug 26, 2012 10:11:25 PM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 192.168.1.55:52,129 during the configured idle timeout of 5 secs>
[Application termination requested. Undeploying application crazy.]
[10:11:54 PM] ---- Deployment started. ----
[10:11:54 PM] Target platform is (Weblogic 10.3).
[10:11:54 PM] Undeploying Application...
<AppPolicyHandler> <removePolicies> Removal of application policy failed. Reason: {0}.
oracle.security.jps.service.policystore.PolicyObjectNotFoundException: Application with name "crazy" does not exist.
     at oracle.security.jps.internal.policystore.xml.XmlPolicyStore.unsync_getApplicationPolicy(XmlPolicyStore.java:704)
     at oracle.security.jps.internal.policystore.xml.XmlPolicyStore.getApplicationPolicy(XmlPolicyStore.java:673)
     at oracle.security.jps.internal.config.deploy.DeployUtil.removeAppPolicy(DeployUtil.java:253)
     at oracle.security.jps.internal.config.deploy.AppPolicyHandler$2.run(AppPolicyHandler.java:123)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.internal.config.deploy.AppPolicyHandler.removePolicies(AppPolicyHandler.java:118)
     at oracle.security.jps.internal.config.deploy.AppPolicyHandler.handle(AppPolicyHandler.java:69)
     at oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener.callHandler(JpsApplicationLifecycleListener.java:125)
     at oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener.handle(JpsApplicationLifecycleListener.java:106)
     at oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener.postStop(JpsApplicationLifecycleListener.java:145)
     at weblogic.application.internal.flow.BaseLifecycleFlow$PostStopAction.run(BaseLifecycleFlow.java:351)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
     at weblogic.application.internal.flow.BaseLifecycleFlow.postStop(BaseLifecycleFlow.java:95)
     at weblogic.application.internal.flow.HeadLifecycleFlow.unprepare(HeadLifecycleFlow.java:290)
     at weblogic.application.internal.BaseDeployment$1.previous(BaseDeployment.java:619)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
     at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
     at weblogic.application.internal.BaseDeployment.unprepare(BaseDeployment.java:248)
     at weblogic.application.internal.EarDeployment.unprepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.unprepare(DeploymentStateChecker.java:205)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.unprepare(AppContainerInvoker.java:117)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.silentUnprepare(AbstractOperation.java:689)
     at weblogic.deploy.internal.targetserver.operations.RemoveOperation.removeDeployment(RemoveOperation.java:313)
     at weblogic.deploy.internal.targetserver.operations.RemoveOperation.doCommit(RemoveOperation.java:114)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
[10:11:56 PM] Application Undeployed Successfully.
[10:11:56 PM] Elapsed time for deployment: 2 seconds
[10:11:56 PM] ---- Deployment finished. ----
[Application crazy stopped and undeployed from Server Instance IntegratedWebLogicServer]
Edited by: Stuart Fleming on Aug 26, 2012 7:12 PM

Frank,
Thank you for your answer. I had not checked (will do so tonight).
I had considered it adequate to wipe out the entire system directory (thereby wiping out the integrated weblogic server), but perhaps it was not adequate? I did not specify that this is on the integrated server, but that is the case....
Stuart

NotEditorException when undeploying applications

Very often when undeploying applications, we get the NotEditorException.
It seems that the application is (correctly) undeployed.
This only occurs when undeploying, at other actions we never get this problem..
What can be a reason for this?
thx

what is the version of weblogic

Undeploying Application Errors

<Nov 15, 2002 9:05:18 AM PST> <Error> <J2EE> <Error undeploying application asd:
null>
<Nov 15, 2002 9:05:18 AM PST> <Error> <Management> <InvocationTargetException
setting attribute Deployed on MBean mydomain:Location=myserver,Name=asd,Type=ApplicationConfig
to value false. Method: public void weblogic.management.mbeans.custom.Application.setDeployed(boolean)
throws weblogic.manageme
nt.DeploymentException,weblogic.management.UndeploymentException
java.lang.NullPointerException
at javax.servlet.GenericServlet.getServletContext(GenericServlet.java:205)
at javax.servlet.GenericServlet.log(GenericServlet.java:300)
at javax.servlet.GenericServlet.destroy(GenericServlet.java:122)
at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:451)
at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:434)
at weblogic.servlet.internal.WebAppServletContext.destroyServlets(WebAppServletContext.java:3805)
at weblogic.servlet.internal.WebAppServletContext.shutdown(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:153)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:519)
at weblogic.j2ee.WebAppComponent.undeploy(WebAppComponent.java:90)
at weblogic.j2ee.Application.undeploy(Application.java:285)
at weblogic.j2ee.J2EEService.undeployApplication(J2EEService.java:232)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:370)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:300)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1401)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:894)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:296)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:393)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:299)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy18.setDeployed(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:846)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:748)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:1098)
--------------- nested within: ------------------
weblogic.management.UndeploymentException: - with nested exception:
[java.lang.NullPointerException]
at weblogic.j2ee.J2EEService.undeployApplication(J2EEService.java:248)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:370)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:300)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1401)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:894)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:296)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:393)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:299)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy18.setDeployed(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:846)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:748)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:1098)
>

Problem solved, deploy the custom server, through Oracle Enterprise Manger, the third deploy page is there to configure MDS. selecting an MDS, specified when I created the domain, and given a name for a partition (any name) fixed this error.
Jerry

How to retain portlet preferences when undeploying application

Hi,
we have a requirement where we configure portlet preferences for each portlet instance in a page through admin console.
we use these preference values to retrieve content from VCR and display in portlet jsp.
The problem here is when we undeploy application and install it again all the preferences configured in the admin console will vanish.
Is there any way to retain these values even when we undeploy application.
Thanks

Hello,
There are two ways you could do this: put the preference values in your .portlet files or use the propagation tool to move the customized portlet instances to your new deployment.
Putting the preference values in your .portlet file can't be done from the administration tools-- it must be done from the IDE or manually editing the files-- so I'm guessing it would not solve your problem.
For more information on using the propagation tool, see:
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/propTool.html
Kevin

Coherence objects not released when undeploying application?

Hi
Part of our continuous integration build is deploying our application to a Weblogic server and running some selenium test cases against it. We have usually about 15 builds running each day.
Our problem is that we seem to be experiencing a memory leak in that process; each new build takes more and more memory until weblogic starts throwing out-of-memory errors (as a workaround we'r restarting weblogic every night).
After spending some time using a profiler (we'r using YourKit Java Profiler) it appears that the calls to Coherence libraries cause references to our objects not being properly released and GC is not able to get rid of them properly. If the calls to the Coherence libraries are removed teh GC correctly releases all our application objects.
To confirm this I have created this simle test scenario:
1. Created an empty web application (war) that has only one class in it:
package com.test;
import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
import com.tangosol.net.CacheFactory;
public class TestServletContextListener implements ServletContextListener {
     public void contextDestroyed(ServletContextEvent arg0) {
          CacheFactory.shutdown();
     public void contextInitialized(ServletContextEvent arg0) {}
2. Modified the web.xml to register the ContextListener:
<listener>
<listener-class>com.test.TestServletContextListener</listener-class>
</listener>
3. Created empty EAR that has only two libraries in it: coherence.jar & tangosol.jar (version 3.3.1)
5. included the test web application in the EAR (no other classes, projects or libraries are included; no other configuration settings are adjusted from defaults)
6. While using the profiler I was performing deployemnt and undeployment of teh EAR against the Weblogic server. With each new deployment a new set of com.tangosol* classes is created. Those classes are not released even when GC is forced from the profiler.
I'm not able to attach a screenshot from the profiler to this post, but with each redeployment I can see the following objects created (ordered with number of objects created in a descending order):
com.tangosol.util.Base$ComonMonitor: 1024 new objects
com.tangosol.run.xml.XmlToken: 16 new Objects
com.tangosol.util.ListMap: 11 new Objects
com.tangosol.util.RecyclingLingedList$Node: 5 new Objects
etc.
Am I doing something wrong or is there really a problem with the object references not properly released in Coherence?
thank you
s.

Hello Robert
I have double checked that the two coherence libs don’t exist anywhere on the server class path. I have also tried calling shutdown from preStop instead of postStop but it made no difference.
(Please note that I'm not really looking for the right place to shutdown Coherence; instead I'm trying to demonstrate that calls to Coherence libraries causes object references not to be released properly. I have chosen to use the shutdown method only because it's nicely visible when it's being invoked and also it is something that our application is calling during shutdowns).
To make sure that I'm not overlooking something with the Weblogic setup I have tried it with Tomcat:
1. Downloaded and installed Tomcat 6.0.14
2. Create new WAR project and put coherence.jar & tangosol.jar in WEB-INF/lib
3. Created one class:
package com.test;
import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
import com.tangosol.net.CacheFactory;
public class TestServletContextListener implements ServletContextListener {
     public void contextDestroyed(ServletContextEvent arg0) {
          CacheFactory.shutdown();
     public void contextInitialized(ServletContextEvent arg0) {}
4. modified web.xml:
<listener>
     <listener-class>com.test.TestServletContextListener</listener-class>
</listener>
5. deployed the WAR to the tomcat server with profiler connected to it
After that I have used Tomcat Web Application Manager (http://localhost:8088/manager/html/list) to Stop & Start the application repeatedly.
The behavior is the same as on weblogic. Each stop of the application creates another set of tangosol objects that do not get released by GC.
Am I correct when I say that there is some problem with the Coherence libraries causing memory leaks by not allowing GC to release old objects?
Thank you
s.

Error while undeploying application

When I try to undeploy an application from Oracle AppServer 9.0.4 on Windows I receive the following message:
No ApplicationInfo is associated with application named [somename].
What is ApplicationInfo and why normally deployed application cannot be normally deleted?

Hello,
Please review the following post:
Pointers to "clean" up a deployment when "Undeployment" fails in between
Also as a word of advice, please always search the forums before making a post, your answer maybe a search click away :).
Hope this helps.
Deepak

Error while undeploying Application in 9iAS R2

An error occured while undeploying the application. Root Cause: oracle.ias.sysmgmt.persistence.OperationResult. oracle.ias.sysmgmt.persistence.OperationResult.
The abov error is occuring while undeploying the application. also when i am trying to start dcmctl shell
Please help me out in resolving this issue.

Hello,
Please review the following post:
Pointers to "clean" up a deployment when "Undeployment" fails in between
Also as a word of advice, please always search the forums before making a post, your answer maybe a search click away :).
Hope this helps.
Deepak

Undeploying Applications

Just wondering how to use JDev to undeploy an application?
Thanks

While the server is running, open View/Application Server Navigator
Expand the server until you see all the deployed composites. Right-click and select Undeploy on the one you want to undeploy.
Deployment/Undeployment is a little flaky so you may need to restart the server before you see it really go away.
Heidi.

How to undeploy application on the PI 7.1 Java Engine

Hi everyone,
I have a very simple and stupid question: how can I undeploy the JEE Application on a PI 7.1 server?
I mean, I've installed a JEE Application on the PI 7.1 server through JSPM. I don't use this application any longer and want to just remove it from the server. But I didn't find out how can I do this.
Thanks a lot in advance
with best regards
Xiang
Edited by: Xiang Zhang on Nov 10, 2008 10:36 AM

Hi Prateek,
thanks a lot for your reply. It almost solved the problem. Do you know how can use other tools to undeploy an application. I mean some tools, which have been delivered by SAP with PI 7.1, like NWA, or something else.
with regards
Xiang

EJBs still bound even after undeploying application

Hi,
I am using WebLogic 10.0 MP2 notice that if I undeploy an ear containing Stateless Session EJBs there are still entries for these EJBs in the JNDI server tree. The entries look like <name of Bean>#<full package name of Bean>.
I am undeploying using the WebLogic Console (Deployments->Delete) and see in the log that the deployment goes from STATE_PREPARED to STATE_NEW.
I can fix the issue by deleting the EJBCompilerCache directory but would like to know why they don't get removed as part of the undeploy.
Thanks for any help
Mandy

Hi,
Not I'm not using the autodeploy directory, I am uploading from my local machine to the uploads/ directory.
I don't seem to get any problems when I redeploy the application in a single server but on a cluster I get this issue..
<01-Dec-2010 23:04:35 o'clock GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '129124****2336' for task '19'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(sampleejbs-ejb-0.0.1-SNAPSHOT.jar)
Unable to deploy EJB: JmsAPIConnPoolSonicJmsStatelessSessionBean from sampleejbs-ejb-0.0.1-SNAPSHOT.jar:
[EJB:011008]Unable to bind EJB Home Interface to the JNDI name: sampleejbs-ear-0sampleejbs-ejb-0_0_1-SNAPSHOT_jarJmsAPIConnPoolSonicJmsStatelessSessionBean_HOME.
javax.naming.NameAlreadyBoundException: sampleejbs-ear-0sampleejbs-ejb-0_0_1-SNAPSHOT_jarJmsAPIConnPoolSonicJmsStatelessSessionBean_HOME is already bound; remaining name ''and this:
<01-Dec-2010 23:04:35 o'clock GMT> <Error> <Cluster> <BEA-000123> <Conflict start: You tried to bind an object under the name WLPooledWLJmsStatelessSessionBean#com.xx.xxx.test.samples.JmsMessageSender in the JNDI tree. The object from -769998****8669S:xxx05bb01-wl01:[7021,7021,-1,-1,-1,-1,-1]:jcrxxbus1:xxx05bb01-bus1 is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.>Any ideas much appreciated!
Many thanks
Mandy

Re: jsp:destroy called on undeploying application

You may want to try precompiling the jsps. Try adding the lines below in weblogic.xml:
<jsp-param>
<param-name>precompile</param-name>
<param-value>true</param-value>
</jsp-param>
"Jose K" <[email protected]> wrote:
>
Hi all,
Each time I undeploy an application on Weblogic Portal 4 (running on
WLS 6.1)
, it calls the jsp:destroy which gets rid of all compiled JSP classes.
The result
being that after restart, it takes a very long time to get the web pages
up after
recompiling all the JSP's which havent changed at all. Is this a property
that
can be set? How can I change it?
Thanx Jose

Hi,
With precompile option it takes a long time (almost 2 hours) to restart server as it compiles each jsp again. Is there any option by which I can avoid deletion of compiled jsp classes?
Thanks in advance,
Yogesh.

Jsp:destroy called on undeploying application

Hi all,
Each time I undeploy an application on Weblogic Portal 4 (running on WLS 6.1)
, it calls the jsp:destroy which gets rid of all compiled JSP classes. The result
being that after restart, it takes a very long time to get the web pages up after
recompiling all the JSP's which havent changed at all. Is this a property that
can be set? How can I change it?
Thanx Jose

Hi Yogesh,
          You can set a workingDir in your weblogic.xml to point to a directory
          outside the webapp docroot. Something like:
          <jsp-descriptor>
          <jsp-param>
          <param-name>workingDir</param-name>
          <param-value>c:\jspworkingdir\webapp\</param-value>
          </jsp-param>
          </jsp-descriptor>
          This way you can prevent the jsps from being deleted in your server temp
          dir.
          -- Nagesh
          "Yogesh Kumar" <[email protected]> wrote in message
          news:[email protected]..
          > Hi,
          > Each time I undeploy an application on Weblogic Portal 4 (running on WLS
          6.1), it calls the jsp:destroy which gets rid of all compiled JSP classes.
          The result being that after restart, it takes a very long time to get the
          web pages up after recompiling all the JSP's which havent changed at all.
          >
          > With precompile option it takes a long time (almost 2 hours) to restart
          server as it compiles each jsp again. Is there any option by which I can
          avoid deletion of compiled jsp classes?
          >
          > Thanks in advance,
          > Yogesh

How to use script undeploy applications

Is anyone familiar with OAS script? I want to undeploy some applications using script rather than EM. Any suggestion or help is appreciated.

In 10.1.2, you can write your own shell script and use dcmctl undeployApplication command:
http://download.oracle.com/docs/cd/B14099_19/core.1012/b13997/cmds.htm#BEIGDEFI
In 10.1.3, you can use Ant or admin_client.jar to write your own script:
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28951/dplyapps.htm#i1038931
Hope this helps.
Thanks
Shail

Can't figure out why I can't undeploy an application using WLST

Hi,
I have WebLogic 9.2.2 installed locally on my WinXP machine. I am running a WLST script (through Ant 1.6) to attempt to undeploy my application. This line
undeploy("RoutingEngine (v1.0)")
is causing this error,
[wlst] Undeploying application RoutingEngine (v1.0) ...
[wlst] <Mar 4, 2009 1:04:40 PM MST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating undeploy operation for application, RoutingEngine (v1.0) [archive: null], to AdminServer .>
[wlst] Failed to undeploy the application with status failed
[wlst] Current Status of your Deployment:
[wlst] Deployment command type: undeploy
[wlst] Deployment State : failed
[wlst] Deployment Message : weblogic.management.ManagementException: [Deployer:149001]No application named 'RoutingEngine (v1.0)' exists for operation undeploy
If I log in to my WebLogic admin console under "Deployments", there is an application named "RoutingEngine (v1.0)" listed. Should I be naming this something else or referencing it under another name?
Thanks, - Dave

Hi, something similar has happened in an oracle weblogic 10.3.5, when i tried to delete an application deployed as library, the adminserver responded with error “[Deployer:149001]No application named ‘my-web-9(9.2.1)’ exists for operation undeploy”.
I solved this problem, using weblogic.Deployer but specifying the appversion like this:
java weblogic.Deployer -verbose -noexit -name my-web-9 -appversion 9.2.1 -adminurl t3://192.168.40.66:7000 -user weblogic -undeploy

Undeploying application

Similar Messages

Maybe you are looking for