I don't know if this relevant or correct but it seems to me that Tomcat
contexts have to be reloadable and crossContext. As in:
<Context path="/xyz" docBase="xyz" debug="0" reloadable="true"
crossContext="true">
This is in the file conf/server.xml.
Hope this helps,
At 16:05 25.06.2002 -0500, you wrote:
>Hello Swami,
>
>Thanks for the info.
>
>I tried adding LogManager.shutdown() to my Log4jInit servlet's
>destroy() method, but it seems as if not all servlets are guaranteed to
>have their
>destroy() method called. What I saw in the Tomcat logs was that only
>servlets that were called via their doGet or doPost methods have their
>destroy methods called. My Log4jInit servlet which gets run at
>context startup (via an entry in the web.xml) never had its destroy method
>called even though it was
>initialized.
>
>Looks like I'll have to write a ServletContextListener or something.
>
>Jake
>
>Tuesday, June 25, 2002, 2:45:55 PM, you wrote:
>
>SI> I think there is a LogManager.shutdown().
>
>SI> Swami
>
> >> -----Original Message-----
> >> From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
> >> Sent: June 25, 2002 3:40 PM
> >> To: Log4J Users List
> >> Subject: Re[2]: stopping logging after removing context in Tomcat
> >> problem...
> >>
> >>
> >> Hello Swami,
> >>
> >> That sounds good. Can you expand on how I would do a
> >> "log4j.shutdown"? I'm not sure where to look. I've never seen
> >> mention of this in the FAQ or the docs and don't know where to look in
> >> the API for this. If you can point me in the right direction, that
> >> would be excellent!
> >>
> >> thanks,
> >>
> >> Jake
> >>
> >> Tuesday, June 25, 2002, 1:53:41 PM, you wrote:
> >>
> >> SI> Try catching the deploy in the destroy of the servlet and do the
> >> SI> log4j.shutdown. This would release the resource held by
> >> this jar file and
> >> SI> you would be able to perform your operation.
> >>
> >> SI> Swami
> >>
> >> >> -----Original Message-----
> >> >> From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
> >> >> Sent: June 25, 2002 2:47 PM
> >> >> To: Log4J Users List
> >> >> Subject: stopping logging after removing context in Tomcat
> >> problem...
> >> >>
> >> >>
> >> >> Hi,
> >> >>
> >> >> I'm not sure if this is an issue I should be bringing up here or on
> >> >> the Tomcat-user list, but here goes...
> >> >>
> >> >> I am using Tomcat-4.1.3 and taking advantage of the new Ant tasks
> >> >> which hook up to Tomcat's manager app to dynamically install and
> >> >> remove applications. This works great and log4j initializes just
> >> >> fine. I am using the FileAppender with
> >> configureAndWatch(). Logging
> >> >> works just fine.
> >> >>
> >> >> However, when I remove the app, Tomcat seems to unload all
> >> resources
> >> >> except for log4j-1.2.4.jar because when I attempt an "ant clean",
> >> >> which deletes my "build" directory, it fails saying that
> >> the resource
> >> >> log4j-1.2.4.jar is still in use.
> >> >>
> >> >> So, is this an issue that someone here can explain or should I take
> >> >> this up with the Tomcat-user list?
> >> >>
> >> >> Thanks,
> >> >>
> >> >> Jake
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Best regards,
> >> >> Jacob mailto:[EMAIL PROTECTED]
> >> >>
> >> >>
> >> >> --
> >> >> To unsubscribe, e-mail:
> >> SI> <mailto:[EMAIL PROTECTED]>
> >> SI> For additional commands, e-mail:
>SI> <mailto:[EMAIL PROTECTED]>
>
>SI>> --
>SI>> To unsubscribe, e-mail:
>SI> <mailto:[EMAIL PROTECTED]>
>SI>> For additional commands, e-mail:
>SI> <mailto:[EMAIL PROTECTED]>
>
>
>
>
>
>
>--
>Best regards,
> Jacob mailto:[EMAIL PROTECTED]
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
Ceki
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
