I'm seeing something odd in the deploymentList for
org.jboss.deployment.MainDeployer.  You can see the results by invoking
listDeployed() method on MainDeployer from the jmx-console.  The output is
from DeploymentInof.toString() for everything deployed.

My output includes 4 copies of the DeploymentInfo for
(server)/deploy/http-invoker.sar/invoker.war.  They all have the same object
hash: [EMAIL PROTECTED]

Also, if you replace the

            if (deploymentList.lastIndexOf(di) != -1)

line of MainDeployer.destroy() with

            while (deploymentList.lastIndexOf(di) != -1)

and add this line

                log.info("Removing
deploymentList["+deploymentList.lastIndexOf(di)+"] for "+di.url);

to the loop block, you'll see at shutdown that invoker.war gets removed 4
times.

I haven't found the cause yet.  My first guess was that it's related to the
fact that there are 4 attempts to deploy invoker.war before an appropriate
deployer is found.  But a quick look at the code seems to indicate that it
won't get into deploymentList until a deployer is found.

It seems an innocuous, since they are 4 references to the same object.
Replacing deploymentList.add(...) with a conditional add would eliminate the
duplicates, but that really addresses the symptom, not the cause.

Has anyone seen this?  Searched down the cause?


Rod Burgett 
Senior Software Engineer 

webMethods, Inc. 
3930 Pender Drive 
Fairfax, VA  22030  USA 
Ph: 703.460.5819  (tty only) 

"It's all just 0s & 1s - 
 the trick is getting them lined up in the proper order"



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to