Applet crashes while running against server at localhost

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install and web100srv v3.6.5.1
2. Run the applet by passing localhost (i.e. "java -jar Tcpbw100.jar 127.0.0.1")
3. Click the start button

What is the expected output? What do you see instead?
All tests should complete successfully. However the applet hangs and never 
completes all the tests.

What version of the product are you using? On what operating system?
NDT version 3.6.5.1 obtained from the Downloads section on Ubuntu linux running 
kernel 2.6.35 from kernel.org patched with the web100 patch.

Please provide any additional information below.
The applet completes all the tests successfully if I pass the LAN IP address of 
my system (192.168.x.x). If I pass 127.0.0.1, at one stage of the 
client-to-server throughput test, a wrong message is received (line 1706 of 
Tcpbw100.java) and while parsing this message to Integer to log an error, the 
Applet crashes.

Original issue reported on code.google.com by anant.su...@gmail.com on 17 Jul 2013 at 3:46

[GoogleCodeExporter]

I'm guessing something crashed. Is it possible to get the debug logs for the 
server?

Original comment by AaronMat...@gmail.com on 17 Jul 2013 at 3:57

[GoogleCodeExporter]

Should I post the web100srv.log file ? 
I could give you the screenshots of the error that occurs as well.

Original comment by anant.su...@gmail.com on 17 Jul 2013 at 4:07

[GoogleCodeExporter]

Both would be helpful

Original comment by AaronMat...@gmail.com on 17 Jul 2013 at 4:08

[GoogleCodeExporter]

This is the web100srv.log file :

Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Signal 28 received by process 3108
Unexpected signal (28) received, process (3108) may terminate
Jul 17 09:23:26  localhost port 39890
Signal 17 received by process 3249
Signal 11 received by process 3261
Signal 17 received by process 3249
Signal 15 received by process 3249
Signal 17 received by process 3108
Signal 2 received by process 3108
Signal 2 received by process 3291

Original comment by anant.su...@gmail.com on 17 Jul 2013 at 4:37

[GoogleCodeExporter]

This is a screenshot of the error (server debug level 5) :

Original comment by anant.su...@gmail.com on 17 Jul 2013 at 4:37

Attachments:

• 55.png

[GoogleCodeExporter]

Are you sure web100 is running on teh server? That's a normal error for when 
it's not. What's "uname -a" show?

Original comment by AaronMat...@gmail.com on 17 Jul 2013 at 5:57

[GoogleCodeExporter]

Yes, uname shows kernel version 2.6.35-web100. 
Also, I am able to successfully run the tests from another computer or my own 
computer by passing the LAN IP.

Original comment by anant.su...@gmail.com on 18 Jul 2013 at 11:26

[GoogleCodeExporter]

So this is only a problem if you're running NDT in loopback? If so, that should 
get fixed, though it's probably a lower priority since i'm not sure how useful 
testing how good the loopback 'network' is :)

Original comment by AaronMat...@gmail.com on 18 Jul 2013 at 1:08

[GoogleCodeExporter]

Yes, it is only a problem while running NDT in loopback.
I was trying to run tests against my own server and I found this issue so I 
reported it.

Original comment by anant.su...@gmail.com on 18 Jul 2013 at 1:16

[GoogleCodeExporter]

Original comment by jslawin...@soldevelo.com on 25 Sep 2013 at 1:17

• Added labels: Component-GUI

[GoogleCodeExporter]

Original comment by llewczyn...@soldevelo.com on 25 Sep 2013 at 2:08

• Changed state: Started

[GoogleCodeExporter]

This was not a problem with the applet, but with the ndt server. The issue was 
fixed in v3.6.5.2.

Original comment by llewczyn...@soldevelo.com on 4 Oct 2013 at 9:43

• Changed state: Fixed