Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 458602 - NPE in Xvnc.doSetUp
Summary: NPE in Xvnc.doSetUp
Status: RESOLVED FIXED
Alias: None
Product: Hudson
Classification: Technology
Component: Plugins (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Bob Foster CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-27 23:31 EST by Marc-André Laperle CLA
Modified: 2015-02-12 16:19 EST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc-André Laperle CLA 2015-01-27 23:31:12 EST 
After restart of our Hudson instance, we get this exception:

java.lang.NullPointerException
	at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:83)
	at hudson.plugins.xvnc.Xvnc.setUp(Xvnc.java:73)
	at hudson.model.Build$RunnerImpl.doRun(Build.java:129)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:524)
	at hudson.model.Run.run(Run.java:1493)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44)
	at hudson.model.ResourceController.execute(ResourceController.java:82)
	at hudson.model.Executor.run(Executor.java:137)

I am not aware of any recent upgrades to the Hudson instance or plugins.
See for example https://hudson.eclipse.org/tracecompass/job/tracecompass-gerrit/954/console
Comment 1 Bob Foster CLA 2015-01-28 12:48:04 EST 
In Bug 450388 I attached a new version of xvnc that should fix this issue. I would appreciate it if you could verify it works on your side. Thanks.
Comment 2 Marc-André Laperle CLA 2015-01-28 12:48:43 EST 
I have worked around the problem by:
1. Downgrading the Xvnc plugin  1.13-h-1
2. Restart Hudson
3. Start a build
4. Upgrade the plugin again
5. Restart Hudson.

Then my build worked as before and I have the latest plugin.
Comment 3 Marc-André Laperle CLA 2015-01-28 12:50:37 EST 
(In reply to Bob Foster from comment #1)
> In Bug 450388 I attached a new version of xvnc that should fix this issue. I
> would appreciate it if you could verify it works on your side. Thanks.

Sorry I can't reproduce it right now because I've worked around the problem. If I get it again I'll test the fix for sure. That way it will be a long term solution.
Comment 4 Peter Janes CLA 2015-02-03 12:07:56 EST 
The version in bug 450388 fixes it for me.
Comment 5 Bob Foster CLA 2015-02-12 16:01:31 EST 
Fixed by commit 9817090256ca4a51c13da6cdf73cf61821e8130d. Released as xvnc-1.13-h-4.
Comment 6 Marc-André Laperle CLA 2015-02-12 16:05:37 EST 
Great, thank you!
Comment 7 Bob Foster CLA 2015-02-12 16:19:29 EST 
Thank you and everyone who tested this version!