Destroy() on redeploy (WLS6.1)

Hi,
          I already read in this newsgroup than WLS6.0 had a problem with calling
          a servlet's destroy() method on a graceful shutdown - so I am glad this
          is now working in WLS6.1.
          However there is a strange effect when I redeploy an enterprise archive
          which contains a web app.
          After the first re-deployment (the enterprise archive is already
          deployed when the server is started), nothing happens.
          After each sequential redeployment, first destroy and then init is
          called, how you would expect it. does anyone else have the same problem?
          The exact event-log looks like this
          server starts
          servlet.init() (Servlet does load-on-startup)
          redeploy
          servlet.destroy()
          servlet.init()
          redeploy
          servlet.destroy()
          servlet.init()
          shutdown request with admin console
          servlet.destroy()
          Strange ...
          Andreas Ebbert

That looks correct to me. When redeploy occurs, the old servlet is destroyed
          and the new is initialized.
          Peace,
          Cameron Purdy
          Tangosol Inc.
          << Tangosol Server: How Weblogic applications are customized >>
          << Download now from http://www.tangosol.com/download.jsp >>
          "Andreas Ebbert" <[email protected]> wrote in message
          news:[email protected]...
          > Hi,
          >
          > I already read in this newsgroup than WLS6.0 had a problem with calling
          > a servlet's destroy() method on a graceful shutdown - so I am glad this
          > is now working in WLS6.1.
          >
          > However there is a strange effect when I redeploy an enterprise archive
          > which contains a web app.
          >
          > After the first re-deployment (the enterprise archive is already
          > deployed when the server is started), nothing happens.
          >
          > After each sequential redeployment, first destroy and then init is
          > called, how you would expect it. does anyone else have the same problem?
          > The exact event-log looks like this
          >
          > server starts
          > servlet.init() (Servlet does load-on-startup)
          > redeploy
          > servlet.destroy()
          > servlet.init()
          > redeploy
          > servlet.destroy()
          > servlet.init()
          > ...
          > shutdown request with admin console
          > servlet.destroy()
          >
          > Strange ...
          > Andreas Ebbert
          >

Similar Messages

Redeploying .ear in WLS6.0SP1 fails?

When we redeploy an .ear file (uncheck the deployed box, copy the .ear
file, check the deployed box - autoredeploy = off in this case ) in
WLS6.0SP1 th EJB's are successfully redeployed, but the web-app always
fails. It complains that the webapp xxx is already in use. (That
figures, because we redeploy.).
Another - related? - issue is when automatic redeploy is enabled under
WinNT and you have a learge .ear file, it starts unjarring the file
before it's completely copies thus throwing a zipfile in use error.

When we redeploy an .ear file (uncheck the deployed box, copy the .ear
file, check the deployed box - autoredeploy = off in this case ) in
WLS6.0SP1 th EJB's are successfully redeployed, but the web-app always
fails. It complains that the webapp xxx is already in use. (That
figures, because we redeploy.).
Another - related? - issue is when automatic redeploy is enabled under
WinNT and you have a learge .ear file, it starts unjarring the file
before it's completely copies thus throwing a zipfile in use error.

Struts redeploy problem: failed while destroying filter

I've deployed a webapp with struts2 on weblogic 8.1/java 1.4.1_02 from a war file. It works fine, but when I make a redeploy it throws an exception with the following two stack traces. The NoClassDefFoundError seems strange to me, because the two jars struts2-core.jar and backpost-util-concurrent.jar (for retrotranslation of struts2) contain the classes correctly.
Thanks for any help.
<Failed while destroying filter: struts2.java.lang.NoClassDefFoundError: org/apache/struts2/util/ObjectFactoryDestroyable
at org.apache.struts2.dispatcher.Dispatcher.cleanup(Dispatcher.java:260)
at org.apache.struts2.dispatcher.FilterDispatcher.destroy(FilterDispatcher.java:221)
at weblogic.servlet.internal.WebAppServletContext$FilterDestroyAction.run(WebAppServletContext.java:6394)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.destroyFilters(WebAppServletContext.java:5786)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:5682)
at weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:188)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:740)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:767)
at weblogic.servlet.internal.WebAppModule.rollback(WebAppModule.java:745)
at weblogic.j2ee.J2EEApplicationContainer.rollbackModule(J2EEApplicationContainer.java:3057)
at weblogic.j2ee.J2EEApplicationContainer.rectifyClassLoaders(J2EEApplicationContainer.java:1429)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1176)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Failed while destroying filter: struts2.java.lang.NoClassDefFoundError: edu/emory/mathcs/backport/java/util/Arrays
at edu.emory.mathcs.backport.java.util.concurrent.CopyOnWriteArrayList.toArray(CopyOnWriteArrayList.java:99)
at edu.emory.mathcs.backport.java.util.concurrent.CopyOnWriteArrayList.<init>(CopyOnWriteArrayList.java:35)
at com.opensymphony.xwork2.config.ConfigurationManager.setConfigurationProviders(ConfigurationManager.java:100)
at com.opensymphony.xwork2.config.ConfigurationManager.destroyConfiguration(ConfigurationManager.java:141)
at org.apache.struts2.dispatcher.Dispatcher.cleanup(Dispatcher.java:283)
at org.apache.struts2.dispatcher.FilterDispatcher.destroy(FilterDispatcher.java:221)
at weblogic.servlet.internal.WebAppServletContext$FilterDestroyAction.run(WebAppServletContext.java:6394)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.destroyFilters(WebAppServletContext.java:5786)
at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:5682)
at weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:188)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:740)
at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:767)
at weblogic.servlet.internal.WebAppModule.rollback(WebAppModule.java:745)
at weblogic.j2ee.J2EEApplicationContainer.rollbackModule(J2EEApplicationContainer.java:3057)
at weblogic.j2ee.J2EEApplicationContainer.rectifyClassLoaders(J2EEApplicationContainer.java:1429)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1176)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

I had similar problem a while ago. The remedy I had at that time is placing the jar files containing the classes in the "global" classpath to BEA servers, not just put them in the directories that only available for one particular web application. It's a working solution. I am sure there's other way to fix it. My guess is that the security manager for individual applications is setup more strictly. However, I haven't really been able to verify that.

Redeploying application errors out.

We have a clustered application servers (2), and have deployed the application using OEM Application Server Control.
Sometimes, when we redeploy an application (EAR) we get the following error and the ASC removes the application from the OC4J container.
[date][time][servername.oc4jcontainername] application: XYZ is in failed state
[date][time][servername.oc4jcontainername] Operation failed with error: ClassLoader "application.root" (from in filepath): A loader with this name and version already exists, from in filepath.
We have a workaround for this: undeploy application, opmnctl stopall and opmnctl startall and deploy application. This restores the application.
What would cause this error and removal of the application?

Is this an ADF application?
Check you log files. More than likely you will see a java.lang.UnsupportedOperationException.
A bug causes this to happen.
>
Bug 9077465: ERROR JAVA.LANG.UNSUPPORTEDOPERATIONEXCEPTION UPON SESSION TIMEOUT
Problem Description
After upgrading a ADF-application from JDeveloper 10.1.3.3.0 to 10.1.3.5.0 following error occurs when running the page:
java.lang.UnsupportedOperationExceptionat oracle.adf.share.DefaultContext.loadEnvironment(ADFContext.java:574)
at oracle.adf.share.ADFContext.getEnvironment(ADFContext.java:365)
at oracle.adf.share.http.HttpSessionScopeAdapter.getSession(HttpSessionScopeAdapter.java:318)
at oracle.adf.share.http.HttpSessionScopeAdapter.invalidate(HttpSessionScopeAdapter.java:524)
at oracle.adf.share.http.HttpSessionScopeAdapter.valueUnbound(HttpSessionScopeAdapter.java:584)
at com.evermind.server.http.EvermindHttpSession.destroy(EvermindHttpSession.java:472)
at com.evermind.server.http.HttpApplication.invalidateSession(HttpApplication.java:1007)
at com.evermind.server.http.HttpApplication.invalidateSession(HttpApplication.java:978)
at com.evermind.server.http.EvermindHttpSession.invalidate(EvermindHttpSession.java:411)
at com.evermind.server.http.EvermindHttpSession.invalidate(EvermindHttpSession.java:378)
at com.evermind.server.http.SessionAsyncInvalidateHandler.invalidateSession(SessionAsyncInvalidateHandler.java:159)
at com.evermind.server.http.SessionAsyncInvalidateHandler.run(SessionAsyncInvalidateHandler.java:119)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)
This error occurs when the timeout specified in the "web.xml" expires. Once this error occurs the OC4J instance is unusable. No more deployments can be done and so on. The only solution is to restart the application server.
EXPECTED BEHAVIOR
No error to be reported.
Available Workarounds
None
Related Bugs
Bug 7643044 - JAVA.LANG.UNSUPPORTEDOPERATIONEXCEPTION IN DEFAULTCONTEXT. LOADENVIRONMENT
Bug 6365500 - SESSION.INVALIDATE() @ LOGOUT GIVES NULLPOINTEREXCEPTION W/ MULTIPLE ROOT AMS
Bug 6803187 - ADF EXCEPTION CAUGHT: JAVA.LANG.UNSUPPORTEDOPERATIONEXCEPTION, MSG=NULL
Generic/Port-specific findings
Reproduces JDeveloper 10.1.3.5.0
Works fine in JDeveloper 10.1.3.3.0 and 10.1.3.4.0
>
According to Oracle Support, this was fixed in version 11.1.2.0.0. There is a back for version 11.1.1.3.0 that is available by request, but there appears to be no fix for 10g.

[svn] 3779: Continue fix for BLZ-262: null pointer exception on redeploy of web app/servlet.

Revision: 3779
Author: [email protected]
Date: 2008-10-21 10:23:55 -0700 (Tue, 21 Oct 2008)
Log Message:
Continue fix for BLZ-262: null pointer exception on redeploy of web app/servlet.
Remove finally block in servlet init() as the call to destroy() in the catch block will clear ThreadLocals
if there is an error. Move it to the end of try block instead since the init() thread doesn't need any
thread locals set.
Log the startup error before calling destroy() in init() catch clause.
QA: Yes
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-262
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageBrokerServlet.java

Hello!
I had a similar problem under WebLogic 6.1 SP4 after deploying a war-file with
a bug.
After deploying the corrected file, it seemed that the old version was deployed
again.
Perhaps this behaviour will help you to load the new application/ejb:
- undeploy
- remove from targets
- move to targets
- deploy
Claudia
"Marco" <[email protected]> wrote:
>
hi all,
i have found a werid problem in deploying applications in Solaris 8
for weblogic
7.0.
i have deployed one EJB, and the first time i access it (thru teh web
app embedded
in the .ear) it gave me a null pointer exception because i was failing
to lookup
one environment variable.
so, i fix the code, rebuild the ear and redeployed, and the same error
happened
again.
i am sure i did not do any mistakees because i have put some system.err
statements
in the bean code to show the workflow, and when i have deployed it on
Window 2k
the statemens appeared.
but in solaris they didnot appear, and i got the same exception that
i had before..
it looks like wls is caching teh ejb, because whenever i redeploy it
(adding more
and more system.err statements) it always execute the faulty code of
when deployed
the very first time.
anyone can help?
regards
marco

Help! App Server resources cleaned up before Servlet::destroy()

I have a startup servlet that starts a number of threads in it's init() method, and cleans them up in it's destroy() method. These threads listen on JMS connections obtained from a wrapped (pooled) connection factory that was looked up via resource-ref.
          The application starts up fine, but on redeploy or stop, it seems that the application server attempts to shutdown the underlying connection pool before calling the servlet's destroy() method, resultin in the following warning:
          <1-Feb-2005 12:09:46 o'clock PM EST> <Warning> <J2EE> <BEA-160063> <There was an error while closing a JMS session pool or a pooled JMS connection: weblogic.common.ResourceException: Pool bim.comm.qcf_mqusrv8 still in use, 5 resource instances still reserved by application! The pool or object was forcibly closed.>
          There are still 5 resource instances in use because my app hasn't yet been notified to shutdown via the destroy() method.
          I'm running Weblogic 8.1 SP2, and this problem is supposed to have been resolved:
          CR110367 (http://e-docs.bea.com/wls/docs81/notes/resolved_sp02.html)
          Any insight into this problem would be appreciated.

Hi,
Seems you are having socket time out exception. I use to get the same while deploying on XP with (640MB RAM) but able to re-run after freeing some memory. Creator needs optimally atleast 1GB RAM. You have not mentioned your machine RAM...
It might just help..
dr.am mohan rao

Redeploying war files WL 7.0

When a war file is updated and uploaded this error occurs when redeploying
weblogic.management.ApplicationException: Prepare failed. Task Id = 10
Start server side stack trace:
weblogic.management.ApplicationException: Prepare failed. Task Id = 10
Module Name: emi.war, Error: weblogic.j2ee.DeploymentException: Cannot deploy
ServletContext(id=87601,name=emi.war,context-path=/emi) from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war
on prod-ms-a-1 because there is already a webapp named ServletContext(id=3674494,name=emi.war,context-path=/emi)
loaded from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war,
which is using the context path /emi.
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:697)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:576)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1064)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End server side stack trace
Module Name: emi.war, Error: weblogic.j2ee.DeploymentException: Cannot deploy
ServletContext(id=87601,name=emi.war,context-path=/emi) from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war
on prod-ms-a-1 because there is already a webapp named ServletContext(id=3674494,name=emi.war,context-path=/emi)
loaded from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war,
which is using the context path /emi.
Despite destroying the old war file to deploy this new one .Only when the server
is restarted does the deployment work .
please help
Sandra

When a war file is updated and uploaded this error occurs when redeploying
weblogic.management.ApplicationException: Prepare failed. Task Id = 10
Start server side stack trace:
weblogic.management.ApplicationException: Prepare failed. Task Id = 10
Module Name: emi.war, Error: weblogic.j2ee.DeploymentException: Cannot deploy
ServletContext(id=87601,name=emi.war,context-path=/emi) from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war
on prod-ms-a-1 because there is already a webapp named ServletContext(id=3674494,name=emi.war,context-path=/emi)
loaded from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war,
which is using the context path /emi.
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:697)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:576)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1064)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
End server side stack trace
Module Name: emi.war, Error: weblogic.j2ee.DeploymentException: Cannot deploy
ServletContext(id=87601,name=emi.war,context-path=/emi) from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war
on prod-ms-a-1 because there is already a webapp named ServletContext(id=3674494,name=emi.war,context-path=/emi)
loaded from /ec/prod/server/weblogic/projects/prod/prod-ms-a-1/stage/emi-all-1.9p5/emi.war,
which is using the context path /emi.
Despite destroying the old war file to deploy this new one .Only when the server
is restarted does the deployment work .
please help
Sandra

Invalid use of destroyed classloader

Using Apache AXIS, we get the following error after our application has been hot redeployed . There is no problem on the front-end, even as far as functionality, however an error is generated in the log. It seems that the class gets destroyed and does not seem to be rebuilt properly. I am not sure what I really need to do to resolve the problem. If I restart the JBoss server then everything works fine (once again initially until I redeploy then the error occurs again), however I do not want to restart every time I need to redeploy my application.
The following is the error, once again it only appears after we redeploy the application:
10:59:54,415 ERROR [STDERR] java.io.IOException: Invalid use of destroyed classloader, UCL destroyed at:
10:59:54,415 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.findResources(RepositoryClassLoader.java:585)
10:59:54,415 ERROR [STDERR] at java.lang.ClassLoader.getResources(ClassLoader.java:1015)
10:59:54,415 ERROR [STDERR] at org.apache.commons.discovery.jdk.JDK12Hooks.getResources(JDK12Hooks.java:150)
10:59:54,415 ERROR [STDERR] at org.apache.commons.discovery.resource.DiscoverResources$1.getNextResources(DiscoverResources.java:153)
10:59:54,415 ERROR [STDERR] at org.apache.commons.discovery.resource.DiscoverResources$1.getNextResource(DiscoverResources.java:129)
10:59:54,415 ERROR [STDERR] at org.apache.commons.discovery.resource.DiscoverResources$1.hasNext(DiscoverResources.java:116)
10:59:54,415 ERROR [STDERR] at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassNames(DiscoverNamesInFile.java:186)
10:59:54,415 ERROR [STDERR] at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.getNextClassName(DiscoverNamesInFile.java:170)
10:59:54,415 ERROR [STDERR] at org.apache.commons.discovery.resource.names.DiscoverNamesInFile$1.hasNext(DiscoverNamesInFile.java:157)
10:59:54,431 ERROR [STDERR] at org.apache.commons.discovery.resource.names.NameDiscoverers$1.getNextIterator(NameDiscoverers.java:143)
10:59:54,431 ERROR [STDERR] at org.apache.commons.discovery.resource.names.NameDiscoverers$1.hasNext(NameDiscoverers.java:126)
10:59:54,431 ERROR [STDERR] at org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.getNextResource(ResourceClassDiscoverImpl.java:159)
10:59:54,431 ERROR [STDERR] at org.apache.commons.discovery.resource.classes.ResourceClassDiscoverImpl$1.hasNext(ResourceClassDiscoverImpl.java:147)
10:59:54,431 ERROR [STDERR] at org.apache.axis.configuration.EngineConfigurationFactoryFinder$1.run(EngineConfigurationFactoryFinder.java:120)
10:59:54,431 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method)
10:59:54,431 ERROR [STDERR] at org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(EngineConfigurationFactoryFinder.java:113)
10:59:54,431 ERROR [STDERR] at org.apache.axis.configuration.EngineConfigurationFactoryFinder.newFactory(EngineConfigurationFactoryFinder.java:160)
10:59:54,431 ERROR [STDERR] at org.apache.axis.client.Service.getEngineConfiguration(Service.java:812)
10:59:54,431 ERROR [STDERR] at org.apache.axis.client.Service.getAxisClient(Service.java:103)
10:59:54,431 ERROR [STDERR] at org.apache.axis.client.Service.<init>(Service.java:112)

I found the solution: The Apache Discovery file was causing the error. I updated to the most recent commons-discovery-0.4.jar and everything works fine.

How to view the change immediately after a java file is modified without restarting server or redeploy?

          Hi All,
          How to view the change immediately after a java file that is used in jsp is modified
          without restarting server or redeploy?
          Moreover, it is better to keep the original session.
          Any suggestion is appreciated.
          Kammau


          Hi,
          In order to have a new version of a java class, the current classloader must be
          deleted and a new one created. This is what redeployment does. I believe that
          this is more of an issue with Sun's implementation of classloaders. You could
          ask BEA support (719.232.7878) and see if they have any plans to periodically
          check jar files to see if java class file timestamps and destroy and re-create
          classloaders on the fly.
          1) You will still have to accept the performance hit of destroying classloaders
          and creating new ones. There isn't any way around that.
          2) I would think you would want to have more explicit control in production and
          integration anyway.
          You can redeploy applications from the command line (script) file not just the
          console.
          Hope this helps,
          pat
          "Kammau" <[email protected]> wrote:
          >
          >Hi All,
          >How to view the change immediately after a java file that is used in
          >jsp is modified
          >without restarting server or redeploy?
          >Moreover, it is better to keep the original session.
          >Any suggestion is appreciated.
          >
          >Kammau

Redeploying a war file in tomcat 6.0.16 Options

Hi All,
Tomcat is undeployed the application and trying to deploy the new war file.
But tomcat did not able to redeploy the war file and no errors in to log file also.
I am using tomcat 6.0.16. Msg in the log file is as follows
INFO: Undeploying context [evpn]
Nov 17, 2008 3:21:21 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive evpn.war
Nov 17, 2008 3:22:59 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Nov 17, 2008 3:23:00 PM org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[examples] has not been started
Nov 17, 2008 3:23:00 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
your help values more to me.
Thanq very much..............

Hi all,
I don't want to restart the tomcat to redeploy this war file.
Plz help me out ......

WLS7 Deploy on startup works, redeploy gets ClassNotFoundExceptions

Hello
We are using WLS7 SP2 on our local pcs. We package our app as an EAR that contains
several libraries, a war, and several EJB jars. When we put it in the applications
folder and start the server, it deploys fine, works fine. In WLS6.1SP3, when
we used hot deploy to redeploy the app, it would load (although we saw the memory
leak happen). But now in WLS7, we frequently (but not consistently) get error
messages that there are classes that cannot be found.
I have tried fiddling with the deployment order in application.xml, and that didn't
seem to help consistently. I also modified the ant script to call weblogic.Deployer
to -remove the application prior to copying the ear to the applications directory,
and still no real difference.
The thing that's frustrating is that it deploys at startup with no trouble at
all. Is it possible that on redeply there's some lingering references to the
old ear that don't get cleared when it's undeployed? Is the server maybe caching
something?
Has anyone else out there experienced the same problem with hot-deploy in WL7SP2?
Did you resolve the problem? If so, how? Arrrrgghh!!!!!!!

Matt:
Sorry for your frustrations! This is (and I know you don't want to hear
this probably) something that we worked very hard on for the 8.1 release,
ironed out all the bugs in hot deploy. Cleaned up memory leaks and made it
so you don't have to restart the server. We found additionally that the
applications directory is a bit of a hack useful for toy demo's but not real
development. (i.e. you are constantly either archiving and copying or copy
files from your pcs to the directory). So we introduced an approach that
allows you to check your application's src files (jsp, descriptors, .java
files, thirdparty libs) into pcs in exploded ear format and then introduced
a set of ant tasks to help you build and deploy.
So if you can upgrade...... check out:
http://google.bea.com/search?q=split+directory&ie=&site=bea&output=xml_no_dtd&client=bea&lr=&proxystylesheet=http%3A%2F%2Fdev2dev.bea.com%2Fimages%2Fdev2dev.xsl&oe=
Otherwise we go down the road of having a reproducible test case and
oppening a ticket with support.
Cheers
mbg
"Matt Harrah" <[email protected]> wrote in message
news:[email protected]...
>
Hello
We are using WLS7 SP2 on our local pcs. We package our app as an EAR thatcontains
several libraries, a war, and several EJB jars. When we put it in theapplications
folder and start the server, it deploys fine, works fine. In WLS6.1SP3,when
we used hot deploy to redeploy the app, it would load (although we saw thememory
leak happen). But now in WLS7, we frequently (but not consistently) geterror
messages that there are classes that cannot be found.
I have tried fiddling with the deployment order in application.xml, andthat didn't
seem to help consistently. I also modified the ant script to callweblogic.Deployer
to -remove the application prior to copying the ear to the applicationsdirectory,
and still no real difference.
The thing that's frustrating is that it deploys at startup with no troubleat
all. Is it possible that on redeply there's some lingering references tothe
old ear that don't get cleared when it's undeployed? Is the server maybecaching
something?
Has anyone else out there experienced the same problem with hot-deploy inWL7SP2?
Did you resolve the problem? If so, how? Arrrrgghh!!!!!!!

Redeployment errors

hi all,
we were trying to redeploy the app while the wls is running..
there were some application classes which were put into the server's classpath..so
we ran a build script to clean up the app from /applications directory and then
ran another build to deploy the app back into /applications directory
and the following errors are reported
pls help me get an insight into this
thanks
sai
<Nov 7, 2001 11:33:52 AM EST> <Error> <HTTP Session> <Could not deserialize session
data
java.io.NotSerializableException: weblogic.servlet.internal.ServletRequestImpl
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:70)
at weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.java:288)
at weblogic.servlet.internal.session.SessionData.removeValue(SessionData.java:156)
at weblogic.servlet.internal.session.SessionData.remove(SessionData.java:324)
at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(MemorySessionContext.java:93)
at weblogic.servlet.internal.session.MemorySessionContext.shutdown(MemorySessionContext.java:103)
at weblogic.servlet.internal.WebAppServletContext.destroyServlets(WebAppServletContext.java:2424)
at weblogic.servlet.internal.WebAppServletContext.shutdown(WebAppServletContext.java:2410)
at weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:157)
at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:479)
at weblogic.j2ee.WebAppComponent.undeploy(WebAppComponent.java:86)
at weblogic.j2ee.Application.undeploy(Application.java:200)
at weblogic.j2ee.J2EEService.undeployApplication(J2EEService.java:215)
at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:221)
at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:187)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1149)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:773)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:750)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:256)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:318)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:259)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:293)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:175)
at $Proxy13.setDeployed(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:386)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:152)
at weblogic.management.mbeans.custom.ApplicationManager$ApplicationPoller.run(ApplicationManager.java:643)
>
<Nov 7, 2001 11:33:52 AM EST> <Info> <HTTP> <[WebAppServletContext(6864758,ppp)]
action: Finalizing this controller servlet>
<Nov 7, 2001 11:33:52 AM EST> <Info> <HTTP> <[WebAppServletContext(6864758,ppp)]
globalProps: destroy>
<Nov 7, 2001 11:33:52 AM EST> <Info> <HTTP> <[WebAppServletContext(6864758,ppp)]
*.jsp: destroy>
<Nov 7, 2001 11:33:52 AM EST> <Info> <HTTP> <[WebAppServletContext(6864758,ppp)]
*.html: destroy>
Undeploying EJB Component platform-ejb
<Nov 7, 2001 11:33:53 AM EST> <Info> <Adapter> <Exception thrown by rmi server(class
weblogic.jndi.internal.RootNamingNode) [-4557802104
javax.naming.NameNotFoundException: Unable to resolve com.bea.wlpi.EventProcessor.
Resolved: 'com.bea.wlpi' Unresolved:'EventProcessor'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)

Hi Anuj,
Thanks for the reply....there is no ojdbcX.jar in $JAVA_HOME/jre/lib/ext folder....
this composite has dbadapter(mysql) named OP1 as reference component...
while deploying from jdeveloper,it is showing authorization request dialogue asking username and password..I gave weblogic username and password but deployment was unsuccessful.....
Following are jdeveloper deployment log
[09:09:12 AM] Deploying sca_LoadMinMax3_rev1.0.jar to partition "custom" on server WLS_SOA1 [http://XXXX:8001]
[09:09:12 AM] Processing sar=/C:/JDeveloper/11.1.1.5/mywork/LoadMinMax3/LoadMinMax3/deploy/sca_LoadMinMax3_rev1.0.jar
[09:09:12 AM] Adding sar file - C:\JDeveloper\11.1.1.5\mywork\LoadMinMax3\LoadMinMax3\deploy\sca_LoadMinMax3_rev1.0.jar
[09:09:12 AM] Preparing to send HTTP request for deployment
[09:09:12 AM] Creating HTTP connection to host:XXXX, port:8001
[09:09:12 AM] Sending internal deployment descriptor
[09:09:12 AM] Sending archive - sca_LoadMinMax3_rev1.0.jar
[09:12:12 AM] Received HTTP response from the server, response code=401
[09:12:12 AM] Problem in sending HTTP request to the server. Please make sure the server is up and/or check standard HTTP response code for 401
[09:12:12 AM] Error deploying archive sca_LoadMinMax3_rev1.0.jar to partition "custom" on server WLS_SOA1 [http://XXXX:8001]
[09:12:12 AM] HTTP error code returned [401]
[09:12:12 AM] No error message is returned from the server.
[09:12:12 AM] Error deploying archive sca_LoadMinMax3_rev1.0.jar to partition "custom" on server WLS_SOA1 [http://XXXX:8001]
[09:12:12 AM] #### Deployment incomplete. ####
[09:12:12 AM] Error deploying archive file:/C:/JDeveloper/11.1.1.5/mywork/LoadMinMax3/LoadMinMax3/deploy/sca_LoadMinMax3_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
Regards,
jdev

Assertion Error during hot deployment in WLS6.1

Hi,
I am using WLS6.1SP2. The hot deployment feature is enabled. But when I try to
redeploy the bean, it gives the following
assertion error. Somehow the hot deployment doesn't seem to work.
Following is the stack trace:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
at com.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
at com.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize be
fore invoke ]]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
at com.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
throwable exception in BaseServlet weblogic.rmi.extensions.RemoteRuntimeExcepti
on - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must initialize be
fore invoke ]]
throwable exception message null

Are you deployed in an EAR? If so, this is probably a hot redeploy bug.
Report to [email protected].
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Atul Sapkal" <[email protected]> wrote in message
news:[email protected]...
>
Hi,
I am using WLS6.1SP2. The hot deployment feature is enabled. But when Itry to
redeploy the bean, it gives the following
assertion error. Somehow the hot deployment doesn't seem to work.
Following is the stack trace:
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ mustinitialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
atcom.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
atcom.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ mustinitialize bef
ore invoke ]
at weblogic.utils.Debug.assert(Debug.java:84)
atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:218)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
atcom.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
atcom.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must
initialize be> fore invoke ]
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
at $Proxy100.isMyDHLOnlyUser(Unknown Source)
atcom.dhl.network.wsi.login.web.LoginServlet.doPost(LoginServlet.java:3
47)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
atcom.dhl.network.wsi.foundation.web.BaseServlet.service(BaseServlet.ja
va:842)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
throwable exception in BaseServletweblogic.rmi.extensions.RemoteRuntimeExcepti
on - with nested exception:
[weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ must
initialize be> fore invoke ]
throwable exception message null

Error redeploying dbxml

I am having an issue when I redeploy a Tomcat app that uses DBXML.
Before the app is shutdown, delete() is called on the XmlManager (which should close() dbxml environment as well). however, when the app is redeployed, I get an exception:
SEVERE: Error reading tld listeners java.lang.NullPointerException
and then later:
java.lang.UnsatisfiedLinkError: Native Library libdb_java45.dll already loaded in another classloader.
The app starts fine, however, if I stop and start tomcat.
Am I destroying dbxml incorrectly? Any ideas?

As far as I know, Tomcat creates a new classloader each time it loads a servlet. Java has a restriction that a native DLL can only be loaded by one classloader. These two factors combine to give DB XML users on Tomcat no end of headaches.
I believe the way to fix this is to load the DB XML native DLLs from outside the servlet's classloader - having Tomcat load them for you. If anyone has a step-by-step practical guide for how to do this, that would be great.
John

Destroy() on Server Shutdown ?

Should the destroy()method of an active servlet be called by the servlet engine
          upon shutting down WebLogic 6.0? I have a servlet that increments a counter, and
          upon destroy(), it writes the state to a properties file. However, upon shutdown
          of the server via the console, it doesn't get written.
          Any thoughts?


As per Servlets spec when a container finds that servlet need to be removed from
          service destroy method of servlet need to be called.
          But WLS6.0 doesn't seem to do this even in case of graceful shut down(When shutdown
          from console too).
          Kumar.
          Buck Turgidson wrote:
          > Should the destroy()method of an active servlet be called by the servlet engine
          > upon shutting down WebLogic 6.0? I have a servlet that increments a counter, and
          > upon destroy(), it writes the state to a properties file. However, upon shutdown
          > of the server via the console, it doesn't get written.
          >
          > Any thoughts?

Destroy() on redeploy (WLS6.1)

Similar Messages

Maybe you are looking for