cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Revenge" <antonio.mastrol...@cartesio.net>
Subject undeploy and locked logs
Date Tue, 28 Mar 2006 14:12:30 GMT
 

Hi all,

i'm using cocoon 2.1.5.1 (but soon i'll upgrade this version) in a web
application

when I try to undeploy the web application it seems to work, but I see that
my webapp folder still exists.

Insinde the folder there is the cocoon-2.1.5.1.jar and all the cocoon logs
(I use the default logkit logger)

 

logkit.xconf is this (the default configuration file without some categories
as flow, apples, etc):

 

<?xml version="1.0" encoding="UTF-8"?><!--

  Copyright 1999-2004 The Apache Software Foundation

 

  Licensed under the Apache License, Version 2.0 (the "License");

  you may not use this file except in compliance with the License.

  You may obtain a copy of the License at

 

      http://www.apache.org/licenses/LICENSE-2.0

 

  Unless required by applicable law or agreed to in writing, software

  distributed under the License is distributed on an "AS IS" BASIS,

  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

  See the License for the specific language governing permissions and

  limitations under the License.

--><logkit>

  <factories>

    <factory
class="org.apache.avalon.excalibur.logger.factory.PriorityFilterTargetFactor
y" type="priority-filter"/>

    <factory
class="org.apache.avalon.excalibur.logger.factory.ServletTargetFactory"
type="servlet"/>

    <factory class="org.apache.cocoon.util.log.CocoonTargetFactory"
type="cocoon"/>

    <factory
class="org.apache.avalon.excalibur.logger.factory.LF5TargetFactory"
type="lf5"/>

  </factories>

 

  <targets>

 

    <!-- To enable the LogFactor5 graphical logkit browser, replace the
cocoon factory 

         below with the following.

    <lf5 id="core"/>

    -->

 

    <cocoon id="core">

      <filename>${context-root}/WEB-INF/logs/core.log</filename>

      <format type="cocoon">

        %7.7{priority} %{time}   [%{category}] (%{uri})
%{thread}/%{class:short}: %{message}\n%{throwable}

      </format>

      <!--

        append=false: Will override existing log files on Cocoon startup

        append=true: Will append to the existing log files

      -->

      <append>false</append>

      <!--

        rotation: allows you to rotate log files one they meet certain

                  criteria. In example below, files are rotated once they

                  are one hour old or bigger than 100 Mb.

 

      <rotation type="revolving" init="1" max="4">

        <or>

          <size>100m</size>

          <time>01:00:00</time>

        </or>

      </rotation>

      -->

    </cocoon>

 

    <cocoon id="sitemap">

      <filename>${context-root}/WEB-INF/logs/sitemap.log</filename>

      <format type="cocoon">

        %7.7{priority} %{time}   [%{category}] (%{uri})
%{thread}/%{class:short}: %{message}\n%{throwable}

      </format>

      <append>false</append>

    </cocoon>

 

    <cocoon id="handled-errors">

      <filename>${context-root}/WEB-INF/logs/handled-errors.log</filename>

      <format type="cocoon">

        %7.7{priority} %{time}   [%{category}] (%{uri})
%{thread}/%{class:short}: %{message}\n%{throwable}

      </format>

      <append>false</append>

    </cocoon>

 

    <cocoon id="access">

      <filename>${context-root}/WEB-INF/logs/access.log</filename>

      <format type="cocoon">

        %7.7{priority} %{time}   [%{category}] (%{uri})
%{thread}/%{class:short}: %{message}\n%{throwable}

      </format>

      <append>false</append>

    </cocoon>

 

    <!--

      This log file gets only messages with log level ERROR and below.

    -->

    <priority-filter id="error" log-level="ERROR">

      <cocoon>

        <filename>${context-root}/WEB-INF/logs/error.log</filename>

        <format type="cocoon">

          %7.7{priority} %{time}   [%{category}] (%{uri})
%{thread}/%{class:short}: %{message}\n%{throwable}

        </format>

        <append>false</append>

      </cocoon>

    </priority-filter>

     

</targets>

 

  <categories>

    <!--

      log-level: One of DEBUG, INFO, WARN, ERROR, FATAL_ERROR.

      Log level could be different for every category and subcategory.

 

      Not all subcategories are defined in this file. Not defined

      subcategories will be created automatically inheriting settings

      of the parent subcategory.

      When defining subcategory manually, it is required to specify log

      targets, because they are not inherited in this case.

    -->

    <category log-level="INFO" name="core">

      <!-- Startup component manager logger -->

      <category log-level="INFO" name="startup">

        <log-target id-ref="core"/>

        <log-target id-ref="error"/>

      </category>

 

      <category log-level="INFO" name="roles">

        <log-target id-ref="core"/>

        <log-target id-ref="error"/>

      </category>

 

      <category log-level="INFO" name="instrument">

        <category log-level="INFO" name="values">

          <log-target id-ref="core"/>

          <log-target id-ref="error"/>

        </category>

        <log-target id-ref="core"/>

        <log-target id-ref="error"/>

      </category>

 

      <!-- Cocoon component manager logger -->

      <category log-level="INFO" name="manager">

        <log-target id-ref="core"/>

        <log-target id-ref="error"/>

      </category>

 

      <!-- Cocoon cache and stores logger -->

      <category log-level="INFO" name="store">

        <category log-level="INFO" name="janitor">

          <log-target id-ref="core"/>

          <log-target id-ref="error"/>

        </category>

        <log-target id-ref="core"/>

        <log-target id-ref="error"/>

      </category>

 

      <log-target id-ref="core"/>

      <log-target id-ref="error"/>

    </category>

 

    <category log-level="INFO" name="sitemap">

      <log-target id-ref="sitemap"/>

      <log-target id-ref="error"/>

 

      <category log-level="INFO" name="handled-errors">

        <!-- Exceptions that will be handled by a sitemap errorhandler are

             logged to this target. -->

        <log-target id-ref="handled-errors"/>

      </category>

    </category>

 

    <category log-level="INFO" name="access">

      <log-target id-ref="access"/>

      <log-target id-ref="error"/>

    </category>

 

    <category log-level="INFO" name="">

      <log-target id-ref="core"/>

      <log-target id-ref="error"/>

    </category>

  

</categories>

</logkit>

 

 

All these log files (and cocoon-2.1.5.1.jar) are locked and I cannot delete
manually.

I tried to explode the jar lib into classes files (I was searching for the
not disposed class),. and when I try to undeploy the application, all the
classes are deleted, but the logs are still there..

Who locks these files?

 

Could you help me, please?

 

Thanks in advance,

            Antonio.

 


Mime
View raw message