I just downloaded the new FitNesse release 20090709. From this version on FitNesse is released just as a single jar with ~5MB size. In previous versions FitNesse was delivered as zipped distribution. I wondered where the Zip distribution can be downloaded from and read the release notes for version 20090709. There was an interesting entry there:

“Self Install/Update. From now on FitNesse will be released as a jar file. When you first run a new version with java -jar fitnesse.jar it will install itself (or update itself) into the directory in which it is running. No more zip files. No more missing jar files. No more moving pages into new installations. FitNesse takes care of it’s own environment for you.”

java -jar fitnesse.jar
Unpacking new version of FitNesse resources.  Please be patient.
................................................................................................................
................................................................................................................
................................................................................................................
................................................................................
You must now reload FitNesse.  Thank you for your patience........

After this was finished FitNesse created the well known directory structure.

Also the start scripts (run.sh/bat) have gone. The jar is executable, so I started it:

java -jar fitnesse.jar -p 8080
FitNesse (v20090709) Started...
port:              8080
root page:         fitnesse.wiki.FileSystemPage at ./FitNesseRoot
logger:            none
authenticator:     fitnesse.authentication.PromiscuousAuthenticator
html page factory: fitnesse.html.HtmlPageFactory
page version expiration set to 14 days.

Soon I will update fit4oaw to use this version.

Posted via email from Karsten’s Blog

I sometime experience the problem that FitNesse cannot execute tests anymore. After pressing the “Test” button test execution starts, hangs, and after a timeout I get the following error in the log:

Internal Exception:

 java.lang.Exception: FitClient: communication socket was not received on time.
    fitnesse.components.CommandRunningFitClient$TimeoutRunnable.run(CommandRunningFitClient.java:126)
    java.lang.Thread.run(Thread.java:613)

The executed command is:
java -cp /Users/thoms/.m2/repository/org/fitnesse/fitnesse/20090214/fitnesse-20090214.jar:……. :classes:fitnesse.jar:fitlibrary.jar fit.FitServer thoms.local 8080 1

After reading a but through the source I came to the point that this problem arises, when the class FitServer wants to establish a socket for host ‘thoms.local’ and port 8080. Now ‘thoms.local’ is of course my local host, and therefore the same as localhost and 127.0.0.1. I tested now with a small class:

This here works:

public class SocketTest {
    public static void main(String[] args) throws Exception  {
        Socket socket = new Socket(“localhost”, 8080);
        System.out.println(“Socket established”);
        socket.close();
    }
}

When replacing ‘localhost’ by ‘thoms.local’ I get the same problem.

        Socket socket = new Socket(“localhost”, 8080);

Exception in thread “main” java.net.ConnectException: Operation timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:430)
    at java.net.Socket.connect(Socket.java:520)
    at java.net.Socket.connect(Socket.java:470)
    at java.net.Socket.<init>(Socket.java:367)
    at java.net.Socket.<init>(Socket.java:180)
    at playground.SocketTest.main(SocketTest.java:12)

For now I cannot explain why this is happening. Also FitNesse should not call FitServer with ‘thoms.local’, since I call FitNesse with http://localhost:8080.

Tags: fit4oaw, fitnesse