Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1, 2.3.0
    • Fix Version/s: 2.4.0
    • Component/s: jdbc, performance
    • Labels:
      None

      Description

      Now that we have determined that closing Connections was overkill during the prepareForPooling processing when ConnectionRetainMode is set to "always" (OPENJPA-2134), maybe it's time to kill the whole idea of prepareForPooling. If application servers are doing their job correctly, all that should be necessary is to call clear() on the EntityManager before pooling an EM. Instead of removing this public API immediately, I'm thinking we should mark it as deprecated (just in case any app servers are still dependent on this processing).

        Activity

        Hide
        curtisr7 Rick Curtis added a comment -

        Committed revision 1564976 to trunk.

        Show
        curtisr7 Rick Curtis added a comment - Committed revision 1564976 to trunk.

          People

          • Assignee:
            curtisr7 Rick Curtis
            Reporter:
            kwsutter Kevin Sutter
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development