WLS 8.1: weblogic.Deployer + concurrent deployment tasks

Question

Hello,
We have a domain with 4 managed servers which supports a team of 4 developers
(one per managed). They have the possibility to launch Deploy taks using weblogic.Deployer
on one of the managed servers.
We have found that deployment tasks are executed one by one in the Administrative
instance. So when a developer creates a deploy task he has to wait until all pending
deployment tasks end.
¿Is it possible to have three deployment tasks running at the same time instead
of one by one? If it is ¿What should I do to activate it?
Thanks in advance,
Oscar

Answer 1

Oscar:
Take thread dumps when your deploying. You can post the thread dumps here.
Lets see what is taking so long to deploy. You'll want to take multiple
dumps, say 20 seconds apart, say 5 in a row. Remember they go to
std-out/err so you need to capture that data. Also it would be nice if you
cut out all the uninteresting idle threads. Are you not precompiling and
running ejbc (appc) before hand?
Cheers
mbg
"Oscar" <[email protected]> wrote in message
news:[email protected]...
>
This domain is more an integration environment rather than a developmentenvironment.
>
>
The idea is that each developer has its own weblogic domain in their localmachine
in which he develops the application (code, debug, deploy, ...).
He has also a user in a UNIX box, in which there is a domain (applicationintegration
domain) with a managed instance per department. With this user he has someAnt
tasks from where they can deploy (using weblogic.Deployer) a stablerelease of
their application to test the dependant functionality.
The problemm is that some applications (using 100 EJBs and 1 War --> 40MBin exploded
ear and 9MB in compressed ear) take more than 5 minutes to deploy in amanaged
instance and so they produce a stuck in the task queue. During this timethe Administrative
is waiting all the time and the managed instance is deploying theapplication
module by module ¿is there any way to decrease this time? ¿is there anyway to
do it asynchronously without blocking the task queue? That time looks abig high
and taking into account that we are going to have bigger applicationshaving only
one deployment task activated each time looks dangerous. ¿What is aboutincreasing
the admin threads? The task has done all the job in administrative side,so ¿why
wait to the managed server?
We have also note that sometimes waiting tasks produce an unavailabilitystate
in the deployment queue. We have found 4 deployment tasks waiting in the queue,
and after an hour the first deployment task was not finished (maybe in adeadlock)
and so the other 3 deployment tasks were waiting. Is this situation theunique
possibility to solve the problemm is restarting the Administrative (usinga kill
command, shutdown command never ends) ¿What could we do?
Thanks in advance for your help,
Oscar
"Mark Griffith" <[email protected]> wrote:
Deployer may initiate tasks on individual MS's it always goes THROUGH
the AS
and it process's requests serially. This ensures the stability of the
system, allowing multiple changes to cascade through the system at the
same
time.
Is there a reason why you don't have every dev using their own WLS box?
cheers
mbg
"Oscar" <[email protected]> wrote in message
news:[email protected]...
Hello,
We have a domain with 4 managed servers which supports a team of4
developers
(one per managed). They have the possibility to launch Deploy taksusing
weblogic.Deployer
on one of the managed servers.
We have found that deployment tasks are executed one by one in theAdministrative
instance. So when a developer creates a deploy task he has to waituntil
all pending
deployment tasks end.
¿Is it possible to have three deployment tasks running at the sametime
instead
of one by one? If it is ¿What should I do to activate it?
Thanks in advance,
Oscar