WLS7 Deploy on startup works, redeploy gets ClassNotFoundExceptions

Question

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!!!!!!!

Answer 1

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!!!!!!!