Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-18823

Lost stack trace visibility when validation tasks fail due to an exception in Bamboo 6.2

XMLWordPrintable

      Summary

      Since Bamboo 6.2, when validation tasks fail due to an exception the stack trace is no longer printed.

      Steps to Reproduce

      • Remove the dialect property from bamboo.cfg.xml and restart Bamboo.

      Expected Results

      Full stack trace is printed in Bamboo logs

      Actual Results

      Higher level exception message is logged, but no stack trace or underlying cause is logged:

      2017-11-01 17:16:47,829 INFO [localhost-startStop-1] [lifecycle] Real path of servlet context: D:\atlassian\bamboo-6.2.2\Bamboo\atlassian-bamboo\
2017-11-01 17:16:48,297 INFO [localhost-startStop-1] [DefaultBootstrapManager] Running validation tasks
2017-11-01 17:16:48,547 FATAL [localhost-startStop-1] [DefaultBootstrapManager] Validation tests failed: [Cannot create list of validation tests Cannot instantiate upgrade task [com.atlassian.bamboo.upgrade.tasks.validation.BranchKeyStartsWithMastersChainKey]]
2017-11-01 17:16:48,610 FATAL [localhost-startStop-1] [DefaultBootstrapManager] Validation tests failed: Your Bamboo instance could not start because health check failed. Contact Atlassian Support at https://support.atlassian.com
2017-11-01 17:16:48,610 INFO [localhost-startStop-1] [lifecycle] Bamboo home directory: D:\atlassian\bamboo_HOME

            [BAM-18823] Lost stack trace visibility when validation tasks fail due to an exception in Bamboo 6.2

            Krystian Brazulewicz added a comment -

            eene I hope our Support was able to solve your problem. Can you please share the solution?

            Krystian Brazulewicz added a comment - eene I hope our Support was able to solve your problem. Can you please share the solution?

            Elena Veronica ENE added a comment -

            after removing this line from bamboo.cfg.xml :  <property name="hibernate.dialect">org.hibernate.dialect.PostgreSQL82Dialect</property>

            the error is still here and cannot start bamboo server

            Elena Veronica ENE added a comment - after removing this line from bamboo.cfg.xml :  <property name="hibernate.dialect">org.hibernate.dialect.PostgreSQL82Dialect</property> the error is still here and cannot start bamboo server

              mwalerianczyk Marcin Walerianczyk
              jowen@atlassian.com Jeremy Owen
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: