Bamboo full reindex thread is initialized with only 1 thread when hibernate.c3p0.max_size is undefined

XMLWordPrintable

    • Severity 2 - Major

      Summary

      When no hibernate.c3p0.max_size is defined in <bamboo-home>/bamboo.cfg.xml (e.g. if a Tomcat JDBC Datasource is being used instead) then the Bamboo full reindex will be initialized with only a single thread. This can cause significant delays in reindex of Bamboo.

      Steps to Reproduce

      1. Configure a Tomcat JDBC Datasource
      2. Remove hibernate.c3p0.max_size from <bamboo-home>/bamboo.cfg.xml
      3. Start Bamboo

      Expected Results

      Full-reindex thread has initialized thread count equal to available processors and/or logic implemented.

      Actual Results

      Full-reindex is initialized with 1 thread

              Assignee:
              Alexey Chystoprudov
              Reporter:
              Rafael Sperafico (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: