Topic
  • 1 reply
  • Latest Post - ‏2012-12-06T14:49:34Z by SystemAdmin
SystemAdmin
SystemAdmin
5507 Posts

Pinned topic Schedule Hung at Initializing Test Run (63%)

‏2012-12-06T13:56:01Z |
I'm hoping to get some ideas regarding what might cause a schedule to hang at the "Initializing Test Run" Stage.

The workbench log looks like this:

ENTRY com.ibm.rational.test.common.schedule.execution 1 0 2012-12-05 19:31:56.359
!MESSAGE RPTA0000W SmartLoadManager running
Schedule status: UNLAUNCHED
Schedule active users: 0
Current stage: 1
Stage status: Waiting for schedule state RUNNING
Stage target users: 45
Stage duration: 5.00 minutes
Stages after current: 1
Total duration: 24.25 minutes
Percentage completed: 0.00%
Time remaining: 24.25 minutes

!ENTRY com.ibm.rational.test.common.schedule.execution 1 0 2012-12-05 19:32:56.359
!MESSAGE RPTA0000W SmartLoadManager running
Schedule status: LAUNCHED
Schedule active users: 0
Current stage: 1
Stage status: Waiting for schedule state RUNNING
Stage target users: 45
Stage duration: 5.00 minutes
Stages after current: 1
Total duration: 24.25 minutes
Percentage completed: 0.00%
Time remaining: 24.25 minutes

!ENTRY com.ibm.rational.test.common.schedule.execution 1 0 2012-12-05 19:33:56.359
!MESSAGE RPTA0000W SmartLoadManager running
Schedule status: READY
Schedule active users: 0
Current stage: 1
Stage status: Waiting for schedule state RUNNING
Stage target users: 45
Stage duration: 5.00 minutes
Stages after current: 1
Total duration: 24.25 minutes
Percentage completed: 0.00%
Time remaining: 24.25 minutes

The final message is repeated. I left a schedule executing all night, and when I came back in the morning, this "Waiting for schedule state RUNNING" was still being printed to the log.

Both agents have reported that execution of the Schedule was launched, but I don't believe either started generating load.

Does anyone have any idea what might be wrong, or how to figure out what might be wrong?
Updated on 2012-12-06T14:49:34Z at 2012-12-06T14:49:34Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    5507 Posts

    Re: Schedule Hung at Initializing Test Run (63%)

    ‏2012-12-06T14:49:34Z  
    I'm still not sure exactly what was wrong, but I was able to get the schedule to run by increasing the sampling interval to 60s, and running a brief (low-load) schedule prior to the heavier one.