I ran into this issue just recently. I couldn't get swingbench to talk to the coordinator and sadly the large RMI stack traces didn't explain it very well. It turns out that Java RMI expects the hostname and hostname.domain in the /etc/hosts file to be on a separate line to the 127.0.0.1 localhost entry i.e. on the second line.

For example change

127.0.0.1 localhost localhost.localdomain saturn saturn.planets

to

127.0.0.1 localhost localhost.localdomain
10.211.55.4 saturn saturn.planets

Making this simple modification gets everything working as expected. This problem is common in a DHCP environment (not ideal for benchmarking) where you acquire ip address and potentially hostnames dynamincally. Its good practice to keep them on separate lines anyway.

Okay....

So I know I've been quiet recently but that doesn't mean to say I haven't been busy in-fact its been mad at work lately and thats meant that I haven't had a lot of time to work on swingbench or any of my other pet projects. So where am I now? Well there will be a new drop out shortly including some changes to the user interface. Im not sure whether I like them or not. The good news is that all of the options that were once hidden inside of swingbench config file can now be changed from the user interface and its given me the chance to include some that I've meant to put in for some time. The problem with this is that its made the UI a bit busy. I've implemented the change using sub tabs and I swore I'd never to do this as I think it confuses the end user.... I'll let yo decide but the one thing it has confirmed to me is that I'll have to move 2.4 on the a tree based UI similar to the one I use in datagenerator... So what's to come in the next couple of weeks...

• UI changes as I mentioned
• New overview chart replacing the existing one, to feature TPM, TPS, Average response time (?), CPU and Disk I/O.
• Temporal based transactions i.e Run once every 20 minutes or just run once.
• Start recording statistics after x mins, stop recording after x mins.

Now for the bad news. The changes have been quite extensive and have included significant changes to the config file which means any bespoke changes you've made will have to be redone. The changes also mean I could have broken a lot of stuff so expect frequent and regular updates over the next few weeks. I'll also be updating my blog more frequently as well...

Expect the first drop at the start of next week.