[#QB-2000] "Job no longer exists" error after placing QB behind a proxy

QuickBuild

"Job no longer exists" error after placing QB behind a proxy

Created: 28/Mar/14 04:42 PM Updated: 02/Apr/14 05:55 AM

Component/s:

None

Affects Version/s:

5.1.16

Fix Version/s:

None

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

After QB has been put behind Nginx proxy, the following error started frequently appearing in log files. Could you please shed some light on its nature?

2014-03-28 17:34:23,269 [pool-1-thread-69098] ERROR com.pmease.quickbuild.DefaultBuildEngine - Error processing build request.
java.lang.RuntimeException: Error executing grid job.
        at com.pmease.quickbuild.grid.GridTaskFuture.get(GridTaskFuture.java:94)
        at com.pmease.quickbuild.grid.GridTaskFuture.get(GridTaskFuture.java:101)
        at com.pmease.quickbuild.DefaultBuildEngine.process(DefaultBuildEngine.java:316)
        at com.pmease.quickbuild.DefaultBuildEngine.access$000(DefaultBuildEngine.java:129)
        at com.pmease.quickbuild.DefaultBuildEngine$2.run(DefaultBuildEngine.java:1057)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: com.pmease.quickbuild.QuickbuildException: Job no longer exists.
        at com.pmease.quickbuild.grid.GridTaskFuture.testJobs(GridTaskFuture.java:40)
        at com.pmease.quickbuild.grid.GridTaskFuture.get(GridTaskFuture.java:75)
        ... 10 more

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robin Shen [29/Mar/14 01:56 AM]

Thanks for reporting this. Can you please do me the favor of describing the detail procedure to reproduce this issue? Such as how agent and server are configured via Nginx, and how your configuration steps are arranged, etc.

[ Permlink | « Hide ]

Lukasz Guminski [31/Mar/14 05:16 PM]

Hi Robin,

The nginx server runs on Redhat on the same machine as QB server.

You will find proxy configuration here
https://gist.github.com/lguminski/9897067#file-proxy1-conf

In fact, the goal was to apply bandwidth throttling to Rest API as a remedy to a problem reported by Maikel in ~~QB-1895~~ .
https://gist.github.com/lguminski/9897067#file-proxy1b-conf

but the first config file already causes configuration, before applying the second.

Please let me know if you still need our QB configuration. If so, I will send it to you by email.

Regards, Lukasz

[ Permlink | « Hide ]

Lukasz Guminski [31/Mar/14 05:33 PM]

correction:
"but the first config file already caused the error, before applying the second. "

[ Permlink | « Hide ]

Robin Shen [02/Apr/14 05:55 AM]

Set up nginx to act as proxy of QB server and set up a couple of build agents running on other machines connecting to QB server, and builds with steps distributed on server and agents are running fine. Is this issue happening at your side consistently? If yes, would it be possible for you to start a WebEx or NetMeeting session so that I can check the issue lively? I am on GMT+8, and is normally online from 9:00AM to 20:00PM.