Hi,

I'm using Fortress 1.1 to develop a webapp under Tomcat 5.x (WinXP). I've
no problem until I'm trying to undeploy the webapp with Tomcat Manager.
In fact, Tomcat is unable to delete jars which contain  avalon-components
under WEB-INF/lib (source resolver, excalibur datasource ...) and the
generated logkit log file is locked. They seem to be always locked after
the undeploy.
I've downloaded the source code and stepped through the Fortress
implementation and found that the Meta manager opens service.list and other
meta files but don't close them. This bug is produced in two locations:
org.apache.avalon.fortress.impl.role.ServiceMetaManager
org.apache.avalon.fortress.util.Service

After fixing the two "evident" bugs, the logkit log file is unlocked after
the undeploy but the avalon-component-jars are still locked.

At this stage, I've deleted all the meta info from avalon-component-jar and
declared them in a xrole files and the undeploy was completed successfully.
So probably the bug comes always from the avalon-meta manager but I can't
find where.

Please notice that the problem concerns only avalon-component jar using
meta-tag but not components unpacked under WEB-INF/classes (using meta-tag
or not).

Any suggestion is welcome.

Thanks in advance,

Le Minh Triet




**********************************************************************
L'integrite de ce message n'etant pas assuree sur Internet,
nous ne pouvons etre tenu responsable de son contenu.
Si vous n'etes pas destinataire de ce message confidentiel,
Merci de le detruire et d'avertir immediatement l'expediteur.

The integrity of this message cannot be guaranteed on the
Internet. We can not therefore be considered responsible 
for the contents. 
If you are not the intended recipient of this confidential message,
then please delete it and notify immediately the sender.

**********************************************************************


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to