Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-40336

Change C3P0 defaults for idle_test_period

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      We currently ship Confluence with a default idle_test_period of 100 seconds, and a timeout of 30 seconds:

       <property name="hibernate.c3p0.idle_test_period">100</property>
       <property name="hibernate.c3p0.max_size">30</property>
       <property name="hibernate.c3p0.max_statements">0</property>
       <property name="hibernate.c3p0.min_size">0</property>
       <property name="hibernate.c3p0.timeout">30</property>
      

      However, it seems that setting idle_test_period greater than the timeout means that idle connections will never be tested, since idle connections will be removed from the pool after 30 seconds. And we don't set the validate property, which defaults to false, and so idle connections will never be checked with these defaults in place.

      It seems that the timeout should be given a much higher value (i.e., more than 30 seconds), and idle_test_period a value lower than that, so that connections will be checked.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              btom1 Brian
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: