Deployed application is not picked up during weblogic startup

Question

I'm having this strange problem, my application is deployed with java.Deployer
tool, works fine, then when ever i reboot the weblogic server, the application
is not accessible untill i explicitly redeploy it again.
Please help!

Answer 1

http://e-docs.bea.com/wls/certifications/certs_810/overview.html
Looks 141_03. But you have to understand what "certification" means.
Typically within minor revs of the VM 141_03 and 142 you are ok and there
should be no problems.
As for the proving it to you... There were lots of changes and improvemetns
to the 8.1 code line for deployment. As for knowing what your testing for,
OOM is a general error with no clear indication of where the problem lies,
its not clear if it is WLS version or the VM itself. I am sure you know the
hard answer there, it takes digging in with a profiler to find the culprit.
You have two options:
1) Drill down with a profiler in your env and figure out exactly WHAT is the
cause of the leak in the current environment
2) switch between different app verndors/versions and VMs.
Either way you have alot of varialbes to track, take care of and compare.
There is no silver bullet as always.
Cheers
mbg
"Stephen" <[email protected]> wrote in message
news:[email protected]...
>
BTW, is 8.1 certified with 1.4.2 on Solaris/Sparc yet? Otherwise it is anon-starter
>
"Stephen" <[email protected]> wrote:
SOS, we hear this one all the time, the new and improved version fixes
the problem.
Is this a 1.4.2 fix that helps 8.1 or something in the code that is
different?
be specific, I have this problem as well and am not willing to give it
another
try unless I know what I am testing for.
"Mark Griffith" <[email protected]> wrote:
My suggestion would be to try 8.1, I developed many sample applications
over
the course of the release and never had to restart the server and could
continually redeploy. The worst it got was having to completely
undeploy
and redeploy the application. (undeploy + redeploy is different that
just
redeploy).
Cheers
mbg
"Tom Wilson" <[email protected]> wrote in message
news:[email protected]...
This probably doesn't help but....we were doing our initial
development
using
Weblogic 7.0 using 1.3.1_08 but finally we got tired of dealing withthe
out
of memory issues resulting from continuously deploying new versionsof JSP
pages on our system. We found that running into the "Out of Memory"exceptions
combined with restarting and redeploying the app wasted too much time- an
average of 7 minutes about 7-8 times a day resulting in about 1 hourworth
of downtime for each developer using Weblogic. We finally trieddeveloping
our system with Tomcat and OpenEJB and now we never get "Out of
Memory"
exceptions requiring us to restart Tomcat - provided we are onlyworking
on JSP's.
Also, we used JDK 1.4.2 with Tomcat which helps get around the memoryleak
issue
that results from compiling JSP's using JDK 1.3.1.
My suggestion...try something else
"Stephen Westbom" <[email protected]> wrote:
I have had the same problem with Weblogic 7.0 sp4 using 1.3.1_08.
I
found that
turning off deadspot helps (otherwise known as hotspot).
It makes it unusable after a while in a production environment.
Our
firm is considering
switching to JBoss because it is simpler and more reliable, despiteno
good user
friendly deployment tools.
Weblogic concentrates too much on bells and whistles that sound good
rather than
reliability and usability. I guess existing customers are not asimportant
as
new business.
"Dmitry Amelchenko" <[email protected]> wrote:
Also, I don't know if that helps, but in general we've been
experiencing
some
other problems with the web logic deployment. For instance, aftera
number
of
redeployments, the application throwth OutOfMemoryException (about
10
deployments
MAX).
Internally we've been discussing what's the best way of deployingthe
ear application
into the weblogic -- using java deploy tool, or using hot deployby
just
dropping
the app in a particular bea folder.
Is there a prefered/recommended way of deployment?
If not, what people have found to be the most stable way of
deploying?
>>>>>>
Please help!
P.S. I'm little dissappointed, isn't bea an industry leader? Isn'tit
supposed
to take all these little issues away from the developpers so theycan
concentrate
on solving the business problems? It has not been the case for usso
far. BTW
-- JBOSS just works.
"Dmitry" <[email protected]> wrote:
I'm having this strange problem, my application is deployed with
java.Deployer
tool, works fine, then when ever i reboot the weblogic server,
the
application
is not accessible untill i explicitly redeploy it again.
Please help!