myndzi/pool2

Issues

• Return actual error when acquiring fails

  #32 opened 8 years ago
  2

• More connections being open that configured.

  #31 opened 8 years ago
  3

• Pool2 acquisition failure causes resource to hang around

  #30 opened 8 years ago
  20

• TypeError: this._ping is not a function

  #29 opened 8 years ago
  3

• Pool destroyed permanently after temporary network issue

  #28 opened 8 years ago
  8

• When connection acquisition timeout occurs and min is 0, pool2 silently does nothing

  #25 opened 8 years ago
  3

• Will the pool correctly end if unfillable requests error out?

  #24 opened 8 years ago
  1

• r

  #23 opened 8 years ago
  0

• Add "Keep-Alive" or an allocated ping

  #22 opened 8 years ago
  3

• RangeError: Pool2: maxRequests must be a positive integer, Infinity given.

  #21 opened 8 years ago
  2

• Error: Connection lost: The server closed the connection.

  #18 opened 9 years ago
  2

• Convert `destroy` methods to flag resources for destruction after release?

  #17 opened 9 years ago
  0

• Feature request: Auto-reconnect

  #16 opened 9 years ago
  20

• Return a request object?

  #15 opened 9 years ago
  16

• Allocation requests that ping timeout are still served

  #14 opened 9 years ago
  0

• multi-process bug in pool2?

  #13 opened 9 years ago
  1

• Seeing the pool randomly being destroyed after timeout

  #12 opened 9 years ago
  56

• Exception when a supplied 'ping' function takes a long time

  #10 opened 9 years ago
  10

• Document constructor options ?

  #9 opened 9 years ago
  4

• _destroyPool does not reject pending requests

  #8 opened 9 years ago
  1

• Dealing with resource allocation errors

  #7 opened 8 years ago
  2

• 'Pool.release(): Resource not member of pool' error when using setImmediate instead of setTimeout

  #6 opened 9 years ago
  10

• Extend 'capabilities' to be more dynamic?

  #5 opened 9 years ago
  4

• Bumping to 1.1

  #4 opened 9 years ago
  3