Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QuickBuild

System Maintenace running for hours #3727

performance
1 #1
refortin ·

We have System Maintenance scheduled to start at 1:00 am every day. The example below shows the maintenance still running at 9:00am. I believe this issue started when we moved from MySQL to Oracle.

2017-03-01 09:05:19,923 [DefaultQuartzScheduler_Worker-35] INFO com.pmease.quickbuild.plugin.artifact.ArtifactCleanupTask - Cleaning up artifacts for configuration 'root/XXX.../Desktop/Staging'...
2017-03-01 09:05:19,928 [DefaultQuartzScheduler_Worker-35] INFO com.pmease.quickbuild.entitymanager.impl.DefaultBuildManager - Performing task for builds ranging from 197497 to 197497...
2017-03-01 09:05:19,974 [DefaultQuartzScheduler_Worker-35] INFO com.pmease.quickbuild.plugin.artifact.ArtifactCleanupTask - Cleaning up artifacts for configuration 'root/XXX.../Mobile'...
2017-03-01 09:05:19,999 [DefaultQuartzScheduler_Worker-35] INFO com.pmease.quickbuild.plugin.artifact.ArtifactCleanupTask - Cleaning up artifacts for configuration 'root/XXX.../Mobile/Active'...
2017-03-01 09:05:20,003 [DefaultQuartzScheduler_Worker-35] INFO com.pmease.quickbuild.entitymanager.impl.DefaultBuildManager - Performing task for builds ranging from 197502 to 317204...

  • solved #6
  • replies 7
  • views 3693
  • stars 0
#2
robinshen ADMIN ·

While it is running, please get a stack trace:
/path/to/jdk/bin/jstack

2 #3
refortin ·

Hi Robin,

QuickBuild version is 6.1.31 running on Windows server 2012. I've attached 2 traces taken 30 seconds apart.

Thanks

trace1.txt
trace2.txt

1 Reply
#4
steveluo ADMIN ·
refortin

I've attached 2 traces taken 30 seconds apart.

@refortin do you mean run jstack cost 30 seconds, or attached file cost 30 seconds?

1 Reply
#5
refortin ·

Steve,

I mean I ran jstack twice. The output was instantaneous. I just ran it a second time because I was curious about how the output of two runs would differ.

#6
robinshen ADMIN ·

The step is stuck querying builds from Oracle as it tries to load too many builds at once. This situation has been improved in QB 6.1.36 or QB7. Please do an upgrade.

1 Reply
#7
steveluo added the performance label
#8
refortin ·

Upgrading to 6.1.36 solved this issue. Run time went from >15 hours down to 11 minutes.

Thanks.

1 :thumbsup:
Log in to reply