Connection Pool should be upgraded with functionality [moved] #1179

lvca opened this Issue Dec 10, 2012 · 3 comments


None yet

4 participants

OrientDB member

This is Issue 1179 moved from a Google Code project.
Added by 2012-11-22T17:21:31.000Z by
Please review that bug for more context and additional comments, but update this bug.

Original labels: Type-Enhancement, Priority-Low

Original description


The actual connection Pool in Orientdb lacks of some needed functionality in bigger environments: 

Timeout for dbs not used 
Timeout (true / false)

Listeners / Hooks - you can operate with if a connection is established 
(for example -> is the database available or should it be created) 

Listeners - on Close of database - make operations necessary (cleanup - Format C:  or whatever you need) 

Listeners - on Open of Database 

Hope this is enough input -> Luca we send you our implementation - maybe you could reuse something ....

Often you have a DB-layer (with connection pool) between your application and the underlying database - initialized with some passed connection properties (DB-Name/User/Password).

To be able to write unittests against an in-memory database it would be nice to have a connection pool that supports something like"memory:...").


@lvca lvca was assigned May 2, 2013
@lvca lvca modified the milestone: 2.0rc1, 2.1 Aug 28, 2014
@lvca lvca added the enhancement label Oct 4, 2014
@lvca lvca assigned laa and unassigned lvca Feb 1, 2015
@lvca lvca modified the milestone: 2.2, 2.1 Mar 14, 2015
@lvca lvca modified the milestone: 2.2.0-beta, 2.2.0-rc1 Dec 13, 2015
OrientDB member

Are you sure that this issue is valid ?

  1. Listeners - on Close of database - already implemented.
  2. Listeners - on Open of Database - already implemented.
  3. Timeout is not needed any more because single db instance consumes very few of resources.
  4. @markbigler comment. See com.orientechnologies.orient.core.db.OPartitionedDatabasePool#setAutoCreate.
@laa laa added the wontfix label Feb 8, 2016
OrientDB member
laa commented Feb 8, 2016

Well because no one minds, I will close the issue.

@laa laa closed this Feb 8, 2016
@robfrank robfrank modified the milestone: 2.2.0-rc1, 2.2.0-beta2 Mar 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment