-
Bug
-
Resolution: Timed out
-
Low
-
None
-
6.3.3
-
2
-
Severity 2 - Major
-
Summary
During Bamboo internal backup function, if the one of the clustered database shutdown for maintenance, Bamboo does not repeat the unpause task when it manage to reconnect to one of the clustered database
Steps to Reproduce
- Connect Bamboo to a clustered of two Oracle databases
- Set a Backup Scheduler in Bamboo
- During backup job running, shutdown one of the clustered Oracle database to cause error to the backup job
Expected Results
The backup job fail and Bamboo will unpause the server
Actual Results
The backup job fail and Bamboo try to unpause the server but fail with the following error:
2018-06-28 01:16:55,804 WARN [scheduler_Worker-4] [SqlExceptionHelper] SQL Error: 1089, SQLState: 08006 2018-06-28 01:16:55,804 ERROR [scheduler_Worker-4] [SqlExceptionHelper] ORA-01089: immediate shutdown or close in progress - no operations are permitted 2018-06-28 01:16:55,812 INFO [scheduler_Worker-4] [XmlMigrator] Ensuring the the file has been unmounted ... 2018-06-28 01:16:55,815 WARN [scheduler_Worker-4] [NewPooledConnection] [c3p0] A PooledConnection that has already signalled a Connection error is still in use! 2018-06-28 01:16:55,815 WARN [scheduler_Worker-4] [NewPooledConnection] [c3p0] Another error has occurred [ java.sql.SQLRecoverableException: ORA-01089: immediate shutdown or close in progress - no operations are permitted ] which will not be reported to listeners! java.sql.SQLRecoverableException: ORA-01089: immediate shutdown or close in progress - no operations are permitted ... 2018-06-28 01:16:55,844 ERROR [scheduler_Worker-4] [ScheduledBackupJob] java.lang.IllegalStateException: Could not transition server from 'PAUSING' to 'RUNNING' java.lang.IllegalStateException: Could not transition server from 'PAUSING' to 'RUNNING' at com.atlassian.bamboo.ServerLifecycleManagerImpl.updateServerLifecycleState(ServerLifecycleManagerImpl.java:284) at com.atlassian.bamboo.ServerLifecycleManagerImpl.serverRunning(ServerLifecycleManagerImpl.java:132) at com.atlassian.bamboo.ServerLifecycleManagerImpl.resumeServer(ServerLifecycleManagerImpl.java:244) at com.atlassian.bamboo.migration.ImportExportManagerImpl.bambooExport(ImportExportManagerImpl.java:96) at com.atlassian.bamboo.configuration.ScheduledBackupJob.execute(ScheduledBackupJob.java:71) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:48) at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:26) at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:17) at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:41) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) Caused by: org.springframework.transaction.TransactionSystemException: Could not commit Hibernate transaction; nested exception is org.hibernate.TransactionException: Unable to commit against JDBC Connection
However, it does not repeat the process to unpause Bamboo after it manage to connect to the second clustered Oracle database
Notes
Bamboo should repeat the task to unpause server when it manage to connect to the database again
Hi,
Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.
We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Bamboo Team