Tabnine Logo
DatasourceAccessor.isValid
Code IndexAdd Tabnine to your IDE (free)

How to use
isValid
method
in
org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor

Best Java code snippets using org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.isValid (Showing top 3 results out of 315)

origin: org.eclipse.persistence/org.eclipse.persistence.core

/**
* This method is called by reestablishConnection.
* Nothing needs to be done in case customize is not active (customization hasn't been applied yet).
* to repair existing customizer after connection became invalid.
* However if connection has been customized then
* if connection is still there and deemed to be valid - clear customization.
* Otherwise (or if clear fails) remove customizer and set its prevCustomizer as a new customizer,
* then re-create customizer using the same session as the original one.
*/
protected void reestablishCustomizer() {
  if(customizer != null && customizer.isActive()) {
    if(isValid()) {
      // the method eats SQLException in case of a failure.
      customizer.clear();
    } else {
      // It's an invalid connection - don't bother trying to clear customization.
      AbstractSession customizerSession = (AbstractSession)customizer.getSession();
      // need this so that the new customizer has the same prevCustomizer as the old one.
      customizer = customizer.getPrevCustomizer();
      // customizer recreated - it's the same as the original one, but not active.
      createCustomizer(customizerSession);
    }
  }
}
origin: com.haulmont.thirdparty/eclipselink

/**
* This method is called by reestablishConnection.
* Nothing needs to be done in case customize is not active (customization hasn't been applied yet). 
* to repair existing customizer after connection became invalid.
* However if connection has been customized then
* if connection is still there and deemed to be valid - clear customization.
* Otherwise (or if clear fails) remove customizer and set its prevCustomizer as a new customizer,
* then re-create customizer using the same session as the original one.
*/
protected void reestablishCustomizer() {
  if(customizer != null && customizer.isActive()) {
    if(isValid()) {
      // the method eats SQLException in case of a failure.   
      customizer.clear();
    } else {
      // It's an invalid connection - don't bother trying to clear customization.
      AbstractSession customizerSession = (AbstractSession)customizer.getSession();
      // need this so that the new customizer has the same prevCustomizer as the old one.
      customizer = customizer.getPrevCustomizer();
      // customizer recreated - it's the same as the original one, but not active.
      createCustomizer(customizerSession);
    }
  }
}
origin: org.eclipse.persistence/com.springsource.org.eclipse.persistence

  /**
  * This method is called by reestablishConnection.
  * Nothing needs to be done in case customize is not active (customization hasn't been applied yet). 
  * to repair existing customizer after connection became invalid.
  * However if connection has been customized then
  * if connection is still there and deemed to be valid - clear customization.
  * Otherwise (or if clear fails) remove customizer and set its prevCustomizer as a new customizer,
  * then re-create customizer using the same session as the original one.
  */
  protected void reestablishCustomizer() {
    if(customizer != null && customizer.isActive()) {
      if(isValid()) {
        // the method eats SQLException in case of a failure.   
        customizer.clear();
      } else {
        // It's an invalid connection - don't bother trying to clear customization.
        AbstractSession customizerSession = (AbstractSession)customizer.getSession();
        // need this so that the new customizer has the same prevCustomizer as the old one.
        customizer = customizer.getPrevCustomizer();
        // customizer recreated - it's the same as the original one, but not active.
        createCustomizer(customizerSession);
      }
    }
  }  
}
org.eclipse.persistence.internal.databaseaccessDatasourceAccessorisValid

Javadoc

This attribute is used to determine if the connection should be returned to the pool or removed from the pool and closed. It will be set to false if an exception occurs during Call execution.

Popular methods of DatasourceAccessor

  • basicBeginTransaction
    Begin the driver level transaction.
  • basicCommitTransaction
    Commit the driver level transaction.
  • basicExecuteCall
    Execute the call to driver level datasource.
  • basicRollbackTransaction
    Rollback the driver level transaction.
  • buildConnectLog
    Build a log string of any driver metadata that can be obtained.
  • clone
    Clone the accessor.
  • closeConnection
    Close the accessor's connection. This is used only for external connection pooling when it is intend
  • closeDatasourceConnection
    Close the connection to the driver level datasource.
  • commitTransaction
    Commit a transaction on the database. If using non-managed transaction commit the local transaction.
  • connectInternal
    Connect to the database. Exceptions are caught and re-thrown as EclipseLink exceptions.
  • createCustomizer
    Attempts to create ConnectionCustomizer. If created the customizer is cached by the accessor. Called
  • decrementCallCount
    Used for load balancing and external pooling.
  • createCustomizer,
  • decrementCallCount,
  • disconnect,
  • getDatasourceConnection,
  • getLogin,
  • getReadStatementsCount,
  • getStoredProcedureStatementsCount,
  • getWriteStatementsCount,
  • incrementCallCount,
  • isConnected

Popular in Java

  • Start an intent from android
  • getResourceAsStream (ClassLoader)
  • compareTo (BigDecimal)
  • scheduleAtFixedRate (ScheduledExecutorService)
  • FlowLayout (java.awt)
    A flow layout arranges components in a left-to-right flow, much like lines of text in a paragraph. F
  • FileNotFoundException (java.io)
    Thrown when a file specified by a program cannot be found.
  • Socket (java.net)
    Provides a client-side TCP socket.
  • Random (java.util)
    This class provides methods that return pseudo-random values.It is dangerous to seed Random with the
  • Handler (java.util.logging)
    A Handler object accepts a logging request and exports the desired messages to a target, for example
  • Base64 (org.apache.commons.codec.binary)
    Provides Base64 encoding and decoding as defined by RFC 2045.This class implements section 6.8. Base
  • Top plugins for WebStorm
Tabnine Logo
  • Products

    Search for Java codeSearch for JavaScript code
  • IDE Plugins

    IntelliJ IDEAWebStormVisual StudioAndroid StudioEclipseVisual Studio CodePyCharmSublime TextPhpStormVimGoLandRubyMineEmacsJupyter NotebookJupyter LabRiderDataGripAppCode
  • Company

    About UsContact UsCareers
  • Resources

    FAQBlogTabnine AcademyTerms of usePrivacy policyJava Code IndexJavascript Code Index
Get Tabnine for your IDE now