Package org.conscrypt

Class ServerSessionContext

java.lang.Object
org.conscrypt.ServerSessionContext
All Implemented Interfaces:
SSLSessionContext
public class ServerSessionContext
extends Object
Caches server sessions. Indexes by session ID. Users typically look up sessions using the ID provided by an SSL client.

  • Constructor Details

    • ServerSessionContext

      public ServerSessionContext()

  • Method Details

    • setPersistentCache

      public void setPersistentCache​(SSLServerSessionCache persistentCache)

    • sessionRemoved

      protected void sessionRemoved​(SSLSession session)
      Called when a session is removed. Used by ClientSessionContext to update its host-and-port based cache.

    • getSession

      public SSLSession getSession​(byte[] sessionId)
      Description copied from interface: SSLSessionContext
      Returns the session for the specified session identifier.
      Specified by:
      getSession in interface SSLSessionContext
      Parameters:
      sessionId - the session identifier of the session to look up.
      Returns:
      the session for the specified session identifier, or null if the specified session identifier does not refer to a session in this context.

    • getIds

      public final Enumeration<byte[]> getIds()
      Description copied from interface: SSLSessionContext
      Returns an iterable of all session identifiers in this session context.
      Specified by:
      getIds in interface SSLSessionContext
      Returns:
      an iterable of all session identifiers in this session context.

    • getSessionCacheSize

      public final int getSessionCacheSize()
      Description copied from interface: SSLSessionContext
      Returns the size of the session cache for this session context.
      Specified by:
      getSessionCacheSize in interface SSLSessionContext
      Returns:
      the size of the session cache for this session context, or zero if unlimited.

    • getSessionTimeout

      public final int getSessionTimeout()
      Description copied from interface: SSLSessionContext
      Returns the timeout for sessions in this session context. Sessions exceeding the timeout are invalidated.
      Specified by:
      getSessionTimeout in interface SSLSessionContext
      Returns:
      the timeout in seconds, or zero if unlimited.

    • trimToSize

      protected void trimToSize()
      Makes sure cache size is < maximumSize.

    • setSessionTimeout

      public void setSessionTimeout​(int seconds) throws IllegalArgumentException
      Description copied from interface: SSLSessionContext
      Sets the timeout for sessions in this context. Sessions exceeding the timeout are invalidated.
      Specified by:
      setSessionTimeout in interface SSLSessionContext
      Parameters:
      seconds - the timeout in seconds, or zero if unlimited.
      Throws:
      IllegalArgumentException - if seconds is negative.

    • setSessionCacheSize

      public final void setSessionCacheSize​(int size) throws IllegalArgumentException
      Description copied from interface: SSLSessionContext
      Sets the size of the session cache for this session context.
      Specified by:
      setSessionCacheSize in interface SSLSessionContext
      Parameters:
      size - the size of the session cache, or zero for unlimited cache size.
      Throws:
      IllegalArgumentException - if size is negative.

    • finalize

      protected void finalize() throws Throwable
      Description copied from class: Object
      Invoked when the garbage collector has detected that this instance is no longer reachable. The default implementation does nothing, but this method can be overridden to free resources.

      Note that objects that override finalize are significantly more expensive than objects that don't. Finalizers may be run a long time after the object is no longer reachable, depending on memory pressure, so it's a bad idea to rely on them for cleanup. Note also that finalizers are run on a single VM-wide finalizer thread, so doing blocking work in a finalizer is a bad idea. A finalizer is usually only necessary for a class that has a native peer and needs to call a native method to destroy that peer. Even then, it's better to provide an explicit close method (and implement Closeable), and insist that callers manually dispose of instances. This works well for something like files, but less well for something like a BigInteger where typical calling code would have to deal with lots of temporaries. Unfortunately, code that creates lots of temporaries is the worst kind of code from the point of view of the single finalizer thread.

      If you must use finalizers, consider at least providing your own ReferenceQueue and having your own thread process that queue.

      Unlike constructors, finalizers are not automatically chained. You are responsible for calling super.finalize() yourself.

      Uncaught exceptions thrown by finalizers are ignored and do not terminate the finalizer thread. See Effective Java Item 7, "Avoid finalizers" for more.

      Overrides:
      finalize in class Object
      Throws:
      Throwable