Examples of Cleaner

com.sleepycat.je.cleaner.Cleaner
The Cleaner is responsible for effectively garbage collecting the JE log. It selects the least utilized log file for cleaning (see FileSelector), reads through the log file (FileProcessor) and determines whether each entry is obsolete (no longer relavent) or active (referenced by the Btree). Entries that are active are migrated (copied) to the end of the log, and finally the cleaned file is deleted. The migration of active entries is a multi-step process that can be configured to operate in different ways. Eviction and checkpointing, as well as the cleaner threads (FileProcessor instances) are participants in this process. Migration may be immediate, lazy, or proactive. Active INs are always migrated lazily, which means that they are marked dirty by the FileProcessor, and then logged later by an eviction or checkpoint. Active LNs are either migrated lazily or immediately depending on the EnvironmentConfig.CLEANER_LAZY_MIGRATION setting. If they are migrated lazily, the migrate flag is set in the LN slot by the FileProcessor, and the LN is logged later by an eviction or checkpoint. When the FileProcessor is finished with a file, all lazy migration for that file is normally completed by the end of the next checkpoint, if not sooner via eviction. The checkpoint/recovery mechanism will ensure that obsolete entries will not be referenced by the Btree. At the end of the checkpoint, it is therefore safe to delete the log file. There is one exception to the above paragraph. When attempting to migrate an LN, if the LN cannot be locked then we must retry the migration at a later time. Also, if a database removal is in progress, we consider all entries in the database obsolete but cannot delete the log file until database removal is complete. Such "pending" LNs and databases are queued and processed periodically during file processing and at the start of a checkpoint; see processPending(). In this case, we may have to wait for more than one checkpoint to occur before the log file can be deleted. See FileSelector and the use of the pendingLNs and pendingDBs collections. The last type of migration, proactive migration, is migration of LNs by the evictor or checkpointer for files that are to-be-cleaned, i.e., part of the cleaner's backlog. The idea is to prevent the backlog from growing too large (and potentially filling the disk) by doing more cleaner work during eviction, which will throttle the application threads. By default, proactive migration is disabled, but it can enabled using EnvironmentConfig.CLEANER_BACKGROUND_PROACTIVE_MIGRATION and CLEANER_FOREGROUND_PROACTIVE_MIGRATION.
com.sun.enterprise.ee.synchronization.cleaner.Cleaner
Repository cache cleaner interface. @author Nazrul Islam @since JDK1.4
jric.cleaner.Cleaner
@author jwb09119 @date 2014/8/15
no.priv.garshol.duke.Cleaner
A function which can turn a value into a normalized value suitable for comparison.
org.jsoup.safety.Cleaner
The whitelist based HTML cleaner. Use to ensure that end-user provided HTML contains only the elements and attributes that you are expecting; no junk, and no cross-site scripting attacks!
The HTML cleaner parses the input as HTML and then runs it through a white-list, so the output HTML can only contain HTML that is allowed by the whitelist.
It is assumed that the input HTML is a body fragment; the clean methods only pull from the source's body, and the canned white-lists only allow body contained tags.
Rather than interacting directly with a Cleaner object, generally see the {@code clean} methods in {@link org.jsoup.Jsoup}.
org.surfnet.oaaas.support.Cleaner
Helper class that contains scheduled tasks for database cleanup
sun.misc.Cleaner
General-purpose phantom-reference-based cleaners.
Cleaners are a lightweight and more robust alternative to finalization. They are lightweight because they are not created by the VM and thus do not require a JNI upcall to be created, and because their cleanup code is invoked directly by the reference-handler thread rather than by the finalizer thread. They are more robust because they use phantom references, the weakest type of reference object, thereby avoiding the nasty ordering problems inherent to finalization.
A cleaner tracks a referent object and encapsulates a thunk of arbitrary cleanup code. Some time after the GC detects that a cleaner's referent has become phantom-reachable, the reference-handler thread will run the cleaner. Cleaners may also be invoked directly; they are thread safe and ensure that they run their thunks at most once.
Cleaners are not a replacement for finalization. They should be used only when the cleanup code is extremely simple and straightforward. Nontrivial cleaners are inadvisable since they risk blocking the reference-handler thread and delaying further cleanup and finalization. @author Mark Reinhold

Examples of org.jsoup.safety.Cleaner

  public boolean isValid(CharSequence value, ConstraintValidatorContext context) {
    if ( value == null ) {
      return true;
    }


    return new Cleaner( whitelist ).isValid( getFragmentAsDocument( value ) );
  }

View Full Code Here

Examples of org.surfnet.oaaas.support.Cleaner

    return new org.springframework.validation.beanvalidation.LocalValidatorFactoryBean();
  }


  @Bean
  public Cleaner cleaner() {
    return new Cleaner();
  }

View Full Code Here

Examples of sun.misc.Cleaner

        b.put(data);
    }


    private void unmapBuffer(MappedByteBuffer b) {
        if(b!=null){
            Cleaner cleaner = ((sun.nio.ch.DirectBuffer) b).cleaner();
            if(cleaner!=null)
                cleaner.clean();
        }
    }

View Full Code Here

Examples of sun.misc.Cleaner

    static void throwException(Throwable t) {
        UNSAFE.throwException(t);
    }


    static void freeDirectBuffer(ByteBuffer buffer) {
        Cleaner cleaner;
        try {
            cleaner = (Cleaner) getObject(buffer, CLEANER_FIELD_OFFSET);
            if (cleaner == null) {
                throw new IllegalArgumentException(
                        "attempted to deallocate the buffer which was allocated via JNIEnv->NewDirectByteBuffer()");
            }
            cleaner.clean();
        } catch (Throwable t) {
            // Nothing we can do here.
        }
    }

View Full Code Here

Examples of sun.misc.Cleaner

    }


    return AccessController.doPrivileged(new PrivilegedAction<Object>() {
      public Object run() {
        try {
          Cleaner cleaner = ((DirectBuffer)buffer).cleaner();
          if (cleaner != null) cleaner.clean(); // Already cleaned otherwise
          return null;
        }
        catch (Exception e) {
          return buffer;
        }

View Full Code Here

Examples of sun.misc.Cleaner

      final boolean toBeWrote) throws FileIOErrorException {
    try {
      if (toBeWrote) {
        if (byteBuffer.isDirect()) {
          ((MappedByteBuffer) byteBuffer).force();
          final Cleaner cleaner = ((sun.nio.ch.DirectBuffer) byteBuffer)
              .cleaner();
          if (cleaner != null) {
            cleaner.clean();
          }
        } else {
          writeByteBuffer(byteBuffer, index);
        }
      } else {
        if (byteBuffer.isDirect()) {
          final Cleaner cleaner = ((sun.nio.ch.DirectBuffer) byteBuffer)
              .cleaner();
          if (cleaner != null) {
            cleaner.clean();
          }
        }
      }
    } catch (Exception exception) {
      String fileSize;

View Full Code Here

Examples of sun.misc.Cleaner

        }


    }


    private static void unmap(MappedByteBuffer bb) {
        Cleaner cl = ((DirectBuffer)bb).cleaner();
        if (cl != null)
            cl.clean();
    }

View Full Code Here

Examples of sun.misc.Cleaner

        }


    }


    private static void unmap(MappedByteBuffer bb) {
        Cleaner cl = ((DirectBuffer)bb).cleaner();
        if (cl != null)
            cl.clean();
    }

View Full Code Here

0 1 2 3 4

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.