Niklas,
After changing the configuration, the build fails with the following error:
java.io.IOException: Cannot run program
"/home/hudson/tools/java/jdk1.6.0_20-32-unlimited-security/bin/java"
(in directory "/home/hudson/hudson-slave/workspace/wss4j-1.5/wss4j"):
java.io.IOException: error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:475)
at hudson.Proc$LocalProc.<init>(Proc.java:192)
at hudson.Proc$LocalProc.<init>(Proc.java:164)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:638)
at hudson.Launcher$ProcStarter.start(Launcher.java:273)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:793)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:767)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.io.IOException: java.io.IOException: error=2, No such
file or directory
at java.lang.UNIXProcess.<init>(UNIXProcess.java:164)
at java.lang.ProcessImpl.start(ProcessImpl.java:81)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:468)
... 15 more
Looks like there is something wrong with the JDK configuration in Hudson.
Andreas
On Thu, Sep 30, 2010 at 15:34, Niklas Gustavsson <nik...@protocol7.com> wrote:
> On Tue, Sep 28, 2010 at 4:53 PM, Andreas Veithen
> <andreas.veit...@gmail.com> wrote:
>>> Would we like this to be a specific JDK configuration in Hudson? That
>>> is, is there a value in having builds running on "un-touched" JDKs by
>>> default?
>>
>> If the question is whether we have any test suites that validate that
>> a given project runs correctly on a JRE without unlimited strength,
>> then the answer is no, at least for the builds I'm managing (Axis2 and
>> WS). Obviously I cannot speak for other projects...
>
> I've added a specific JDK for this purpose: "JDK 1.6 (Unlimited
> security)". I have also changed back the regular JDK 1.6 to use the
> vanilla policy JARs.
>
> This JDK is available on ubuntu1 and ubuntu2 so you should be able to
> tie your job to "Ubuntu" and use this JDK.
>
> /niklas
>
