NanoContainer Sandbox

Fix org.nanocontainer.pool.PicoPoolTestCase

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Component/s: pool
  • Labels:
    None
  • Number of attachments :
    0

Description

It keeps failing.

I am tempted to delete both pool and pool2, as they are competing with the more mature Jakarta commons-pool project.

Issue Links

depends upon

New Feature - A new feature of the product, which has yet to be developed. PTOYS-4 AutoPool object

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
duplicates

Task - A task that needs to be done. NANOSANDBOX-3 Consolidate pool and pool2

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jörg Schaible added a comment -

JDK? OS? I've tested this with Sun's 1.4.2 on Windows and Linux and also with Blackdown 1.4.1 on Linux and do not have problems ...

Well, before removing it, I'll have a look at commons-pool. We will still have to integrate this somehow into a CA and we will still have the different approaches. Why hurry now?

Show
Jörg Schaible added a comment - JDK? OS? I've tested this with Sun's 1.4.2 on Windows and Linux and also with Blackdown 1.4.1 on Linux and do not have problems ... Well, before removing it, I'll have a look at commons-pool. We will still have to integrate this somehow into a CA and we will still have the different approaches. Why hurry now?
Hide
Permalink
Jörg Schaible added a comment -

I had a look at commons-pool, but I am not convinced, that it solves really our problem. If we want to provide pooling capabilities with a DecoratorCA, we'll always have the problem releasing the components. Commons-pool also always expects the invocation of a release method.

Therefore I would like to implement a solution, that is similar to the AutoReleasingPoolComponentAdapter of pool2, but is based on the AutoPool implementation, that waits in PTOYS-4 for approval.

Show
Jörg Schaible added a comment - I had a look at commons-pool, but I am not convinced, that it solves really our problem. If we want to provide pooling capabilities with a DecoratorCA, we'll always have the problem releasing the components. Commons-pool also always expects the invocation of a release method. Therefore I would like to implement a solution, that is similar to the AutoReleasingPoolComponentAdapter of pool2, but is based on the AutoPool implementation, that waits in PTOYS-4 for approval.
Hide
Permalink
Jörg Schaible added a comment -

Both issues emphasis a consolidation of the pools.

Show
Jörg Schaible added a comment - Both issues emphasis a consolidation of the pools.
Hide
Permalink
Jörg Schaible added a comment -

I think I finally fixed this yesterday synchronizing the concurrent threads with synchronization points.

Show
Jörg Schaible added a comment - I think I finally fixed this yesterday synchronizing the concurrent threads with synchronization points.

People

  • Assignee:
    Jörg Schaible
    Reporter:
    Aslak Hellesøy
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: