[Issue 150] Slaves with empty names destabilize Hudson operations

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Issue 150] Slaves with empty names destabilize Hudson operations


------- Additional comments from [hidden email] Mon Nov 13 20:05:32 +0000 2006 -------
With Hudson 1.59 and 1.60 the exception is similar to what described in ISSUE #149.

With the current build (from todays workspace, 13 Nov 2006, that contains bugfix
for ISSUE #149), I don't see exception mentioned in #149, but I see the
exceptions mentioned earlier.

For me, reproducing them is very simple:

Configuration -> Add new slave, all fields EMPTY -> Click OK -> Configuration ->
Delete a slave with all empty fields -> Exception:

Exception in thread "Executor #4 for " java.lang.IllegalStateException: Trying
to remove unknown computer: hudson.model.Computer@773d03
        at hudson.model.Hudson.removeComputer(Hudson.java:294)
        at hudson.model.Computer.removeExecutor(Computer.java:166)
        at hudson.model.Executor.run(Executor.java:38)

I use mvn -o jetty:run to start Hudson.

Should probably try with war properly deployed on Tomcat.

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]