Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major 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

        Kevin Sutter created issue -
        Kevin Sutter made changes -
        Field Original Value New Value
        Parent OPENJPA-2134 [ 12543507 ]
        Issue Type Improvement [ 4 ] Sub-task [ 7 ]
        Rick Curtis made changes -
        Assignee Kevin Sutter [ kwsutter ] Rick Curtis [ curtisr7 ]
        Rick Curtis made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 2.4.0 [ 12325298 ]
        Resolution Fixed [ 1 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development