empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gdiao (JIRA)" <empire-db-...@incubator.apache.org>
Subject [jira] [Created] (EMPIREDB-191) The spring example not release connection cause connection pool exhausted.
Date Tue, 27 Aug 2013 01:25:51 GMT
gdiao created EMPIREDB-191:
------------------------------

             Summary: The spring example not release connection cause connection pool exhausted.
                 Key: EMPIREDB-191
                 URL: https://issues.apache.org/jira/browse/EMPIREDB-191
             Project: Empire-DB
          Issue Type: Bug
          Components: Website
    Affects Versions: empire-db-2.4.1
            Reporter: gdiao
            Priority: Minor


    public Integer insertEmployee(String firstName, String lastName, String gender, int departmentId)
{
        SampleDB db = getDB();
        Connection conn = getConnection();

        DBRecord rec = new DBRecord();
        rec.create(db.EMPLOYEES);
        rec.setValue(db.EMPLOYEES.FIRSTNAME, firstName);
        rec.setValue(db.EMPLOYEES.LASTNAME, lastName);
        rec.setValue(db.EMPLOYEES.GENDER, gender);
        rec.setValue(db.EMPLOYEES.DEPARTMENT_ID, departmentId);
        rec.update(conn);
        // Return Employee ID
        return rec.getInt(db.EMPLOYEES.EMPLOYEE_ID);
    }

above code should be coupled with a releaseConnection(conn); otherwise, above code will use
up all the connection in connection pool.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message