com.sun.appserv.connectors.internal.api.PoolingException: Connection could not be allocated because: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

Oracle Community | Olivier Chorier Guest | 4 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    JDBC Pool unavailable induce failed deployment

    Oracle Community | 4 years ago | Olivier Chorier Guest
    com.sun.appserv.connectors.internal.api.PoolingException: Connection could not be allocated because: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
  2. 0

    JPA no suitable driver found for JDBC PostgreSQL in JSF Project

    Stack Overflow | 1 year ago | Niklas Gamsjäger
    com.sun.appserv.connectors.internal.api.PoolingException: Connection could not be allocated because: No suitable driver found for jdbc:postgresql://localhost:5432/project?loginTimeout=0&socketTimeout=0&prepareThreshold=5&unknownLength=2147483647&loglevel=0&tcpkeepalive=false&binaryTransfer=true

    Root Cause Analysis

    1. com.sun.appserv.connectors.internal.api.PoolingException

      Connection could not be allocated because: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

      at com.sun.enterprise.resource.pool.datastructure.RWLockDataStructure.addResource()
    2. Connectors Runtime
      RWLockDataStructure.addResource
      1. com.sun.enterprise.resource.pool.datastructure.RWLockDataStructure.addResource(RWLockDataStructure.java:103)
      1 frame